09 Sep, 2016

1 commit

• fd44aa9a2   [media] v4l: rcar-fcp: Don't force users to check for disabled FCP support ... Browse Code »

  The rcar_fcp_enable() function immediately returns successfully when the
  FCP device pointer is NULL to avoid forcing the users to check the FCP
  device manually before every call. However, the stub version of the
  function used when the FCP driver is disabled returns -ENOSYS
  unconditionally, resulting in a different API contract for the two
  versions of the function.

  As a user that requires FCP support will fail at probe time when calling
  rcar_fcp_get() if the FCP driver is disabled, the stub version of the
  rcar_fcp_enable() function will only be called with a NULL FCP device.
  We can thus return 0 unconditionally to align the behaviour with the
  normal version of the function.

  Reported-by: Sergei Shtylyov
  Signed-off-by: Laurent Pinchart
  Reviewed-by: Geert Uytterhoeven
  Signed-off-by: Mauro Carvalho Chehab

  Laurent Pinchart

  2016-09-09 22:29:57 +0800  

17 Jun, 2016

1 commit

• 7b49235e8   [media] v4l: Add Renesas R-Car FCP driver ... Browse Code »

  The FCP is a companion module of video processing modules in the
  Renesas R-Car Gen3 SoCs. It provides data compression and decompression,
  data caching, and conversion of AXI transactions in order to reduce the
  memory bandwidth.

  The driver is not meant to be used standalone but provides an API to the
  video processing modules to control the FCP.

  Signed-off-by: Laurent Pinchart
  Signed-off-by: Mauro Carvalho Chehab

  Laurent Pinchart

  2016-06-17 18:57:35 +0800