Commit ccb3dd25 authored by Laurent Pinchart's avatar Laurent Pinchart Committed by Greg Kroah-Hartman

v4l: rcar-fcp: Don't force users to check for disabled FCP support

commit fd44aa9a254b18176ec3792a18e7de6977030ca8 upstream.

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: default avatarSergei Shtylyov <>
Signed-off-by: default avatarLaurent Pinchart <>
Reviewed-by: default avatarGeert Uytterhoeven <>
Signed-off-by: default avatarMauro Carvalho Chehab <>
Signed-off-by: default avatarGreg Kroah-Hartman <>
parent cb5d016a
......@@ -29,7 +29,7 @@ static inline struct rcar_fcp_device *rcar_fcp_get(const struct device_node *np)
static inline void rcar_fcp_put(struct rcar_fcp_device *fcp) { }
static inline int rcar_fcp_enable(struct rcar_fcp_device *fcp)
return -ENOSYS;
return 0;
static inline void rcar_fcp_disable(struct rcar_fcp_device *fcp) { }
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment