Hi Geert,
Thank you for the review.
On Monday 15 February 2016 10:32:35 Geert Uytterhoeven wrote:
> On Fri, Feb 12, 2016 at 3:00 AM, Laurent Pinchart wrote:
> > 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 converting of AXI transaction in order to reduce the
>
> "conversion"?
Of course. Can you submit a similar patch to the Gen3 datasheet ? ;-)
> > 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
> > <laurent.pinchart+rene...@ideasonboard.com>
>
> Thanks for your patch!
>
> > --- /dev/null
> > +++ b/Documentation/devicetree/bindings/media/renesas,fcp.txt
> > @@ -0,0 +1,24 @@
> > +Renesas R-Car Frame Compression Processor (FCP)
> > +-----------------------------------------------
> > +
> > +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
> > +converting of AXI transaction in order to reduce the memory bandwidth.
>
> "conversion"?
>
> > +
> > +There are three types of FCP whose configuration and behaviour highly
> > depend +on the module they are paired with.
> > +
> > + - compatible: Must be one of the following
> > + - "renesas,fcpv" for the 'FCP for VSP' device
>
> Any chance this module can turn up in another SoC later? I guess yes.
It's not just that it can, it will.
> What about future-proofing using "renesas,r8a7795-fcpv" and "renesas,rcar-
> gen3-fcpv"?
Given that the device currently has registers and clock only, I wanted to keep
the DT bindings simple. My plan is to introduce new compat strings later as
needed, if needed, when incompatible FCP instances will be introduced. Feel
free to challenge that :-)
> > diff --git a/drivers/media/platform/Kconfig
> > b/drivers/media/platform/Kconfig index fd4fcd5a7184..cbb4e5735bf8 100644
> > --- a/drivers/media/platform/Kconfig
> > +++ b/drivers/media/platform/Kconfig
> > @@ -255,6 +255,19 @@ config VIDEO_RENESAS_JPU
> > To compile this driver as a module, choose M here: the module
> > will be called rcar_jpu.
> >
> > +config VIDEO_RENESAS_FCP
> > + tristate "Renesas Frame Compression Processor"
> > + depends on ARCH_SHMOBILE || COMPILE_TEST
>
> ARCH_RENESAS
Ah, that's finally merged, great.
> > diff --git a/drivers/media/platform/rcar-fcp.c
> > b/drivers/media/platform/rcar-fcp.c new file mode 100644
> > index 000000000000..cf8cb629ae4f
> > --- /dev/null
> > +++ b/drivers/media/platform/rcar-fcp.c
> >
> > +struct rcar_fcp_device *rcar_fcp_get(const struct device_node *np)
> > +{
> > + struct rcar_fcp_device *fcp;
> > +
> > + mutex_lock(&fcp_lock);
> > +
> > + list_for_each_entry(fcp, &fcp_devices, list) {
> > + if (fcp->dev->of_node != np)
> > + continue;
> > +
> > + /*
> > + * Make sure the module won't be unloaded behind our back.
> > This
> > + * is a poor's man safety net, the module should really
> > not be
>
> poor man's
>
> > diff --git a/include/media/rcar-fcp.h b/include/media/rcar-fcp.h
> > new file mode 100644
> > index 000000000000..4260cf48d3b1
> > --- /dev/null
> > +++ b/include/media/rcar-fcp.h
> > @@ -0,0 +1,34 @@
> > +/*
> > + * rcar-fcp.h -- R-Car Frame Compression Processor Driver
> > + *
> > + * Copyright (C) 2016 Renesas Electronics Corporation
> > + *
> > + * Contact: Laurent Pinchart (laurent.pinch...@ideasonboard.com)
> > + *
> > + * This program is free software; you can redistribute it and/or modify
> > + * it under the terms of the GNU General Public License as published by
> > + * the Free Software Foundation; either version 2 of the License, or
> > + * (at your option) any later version.
> > + */
> > +#ifndef __MEDIA_RCAR_FCP_H__
> > +#define __MEDIA_RCAR_FCP_H__
> > +
> > +struct device_node;
> > +struct rcar_fcp_device;
> > +
> > +#if IS_ENABLED(CONFIG_VIDEO_RENESAS_FCP)
> > +struct rcar_fcp_device *rcar_fcp_get(const struct device_node *np);
> > +void rcar_fcp_put(struct rcar_fcp_device *fcp);
> > +void rcar_fcp_enable(struct rcar_fcp_device *fcp);
> > +void rcar_fcp_disable(struct rcar_fcp_device *fcp);
> > +#else
> > +static inline struct rcar_fcp_device *rcar_fcp_get(const struct
> > device_node *np)
> > +{
> > + return ERR_PTR(-ENOENT);
> > +}
> > +static inline void rcar_fcp_put(struct rcar_fcp_device *fcp) { }
> > +static inline void rcar_fcp_enable(struct rcar_fcp_device *fcp) { }
> > +static inline void rcar_fcp_disable(struct rcar_fcp_device *fcp) { }
>
> Given the dummies, the vsp driver can also work when FCP support is not
> enabled?
> Or is this meant purely to avoid #ifdefs in the vsp driver when compiling
> for R-Car Gen2?
>
> In case of the latter, you may want to enforce this in Kconfig.
It's the latter, I'll enforce it in Kconfig in the patch that adds FCP support
in the VSP driver (and keep the stubs here for Gen2).
--
Regards,
Laurent Pinchart
