From: Michael Tretter <m.tretter@pengutronix.de>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: linux-media@vger.kernel.org, devicetree@vger.kernel.org,
Philipp Zabel <p.zabel@pengutronix.de>,
Mauro Carvalho Chehab <mchehab@kernel.org>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Fabio Estevam <festevam@gmail.com>,
kernel@pengutronix.de, linux-imx@nxp.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 6/8] media: imx-pxp: make data_path_ctrl0 platform dependent
Date: Fri, 6 Jan 2023 15:11:41 +0100 [thread overview]
Message-ID: <20230106141141.GE24101@pengutronix.de> (raw)
In-Reply-To: <Y7gUfByMdqL3WFJI@pendragon.ideasonboard.com>
On Fri, 06 Jan 2023 14:30:52 +0200, Laurent Pinchart wrote:
> On Thu, Jan 05, 2023 at 02:47:27PM +0100, Michael Tretter wrote:
> > Unfortunately, the PXP_HW_VERSION register reports the PXP on the i.MX7D
> > and on the i.MX6ULL as version 3.0, although the PXP versions on these
> > SoCs have significant differences.
> >
> > Use the compatible to configure the ctrl0 register as required dependent
> > on the platform.
> >
> > Signed-off-by: Michael Tretter <m.tretter@pengutronix.de>
> > ---
> > drivers/media/platform/nxp/imx-pxp.c | 27 +++++++++++++++++++++++++--
> > 1 file changed, 25 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/media/platform/nxp/imx-pxp.c b/drivers/media/platform/nxp/imx-pxp.c
> > index 1d649b9cadad..4e182f80a36b 100644
> > --- a/drivers/media/platform/nxp/imx-pxp.c
> > +++ b/drivers/media/platform/nxp/imx-pxp.c
> > @@ -19,6 +19,7 @@
> > #include <linux/iopoll.h>
> > #include <linux/module.h>
> > #include <linux/of.h>
> > +#include <linux/of_device.h>
> > #include <linux/sched.h>
> > #include <linux/slab.h>
> >
> > @@ -191,6 +192,11 @@ static struct pxp_fmt *find_format(struct v4l2_format *f)
> > return &formats[k];
> > }
> >
> > +struct pxp_ctx;
>
> Please add a blank line here.
>
> > +struct pxp_pdata {
> > + u32 (*data_path_ctrl0)(struct pxp_ctx *ctx);
> > +};
> > +
> > struct pxp_dev {
> > struct v4l2_device v4l2_dev;
> > struct video_device vfd;
> > @@ -199,6 +205,7 @@ struct pxp_dev {
> > void __iomem *mmio;
> >
> > u32 hw_version;
> > + const struct pxp_pdata *pdata;
> >
> > atomic_t num_inst;
> > struct mutex dev_mutex;
> > @@ -726,7 +733,7 @@ static void pxp_setup_csc(struct pxp_ctx *ctx)
> > }
> > }
> >
> > -static u32 pxp_data_path_ctrl0(struct pxp_ctx *ctx)
> > +static u32 pxp_imx6ull_data_path_ctrl0(struct pxp_ctx *ctx)
> > {
> > u32 ctrl0;
> >
> > @@ -756,6 +763,16 @@ static u32 pxp_data_path_ctrl0(struct pxp_ctx *ctx)
> > return ctrl0;
> > }
> >
> > +static u32 pxp_data_path_ctrl0(struct pxp_ctx *ctx)
> > +{
> > + struct pxp_dev *dev = ctx->dev;
> > +
> > + if (dev->pdata && dev->pdata->data_path_ctrl0)
> > + return dev->pdata->data_path_ctrl0(ctx);
> > +
> > + return pxp_imx6ull_data_path_ctrl0(ctx);
>
> Do you need this fallback, given that all compatible strings give you
> valid pdata ? I'd rather be explicit.
>
> This function then becomes so small that I would inline it in the
> caller.
I was a bit paranoid that there may be cases in which pdata is not set. I will
change this to assume that pdata is always valid and just be explicit.
Michael
>
> > +}
> > +
> > static void pxp_set_data_path(struct pxp_ctx *ctx)
> > {
> > struct pxp_dev *dev = ctx->dev;
> > @@ -1711,6 +1728,8 @@ static int pxp_probe(struct platform_device *pdev)
> > if (!dev)
> > return -ENOMEM;
> >
> > + dev->pdata = of_device_get_match_data(&pdev->dev);
> > +
> > dev->clk = devm_clk_get(&pdev->dev, "axi");
> > if (IS_ERR(dev->clk)) {
> > ret = PTR_ERR(dev->clk);
> > @@ -1811,8 +1830,12 @@ static int pxp_remove(struct platform_device *pdev)
> > return 0;
> > }
> >
> > +static const struct pxp_pdata pxp_imx6ull_pdata = {
> > + .data_path_ctrl0 = pxp_imx6ull_data_path_ctrl0,
> > +};
> > +
> > static const struct of_device_id pxp_dt_ids[] = {
> > - { .compatible = "fsl,imx6ull-pxp", .data = NULL },
> > + { .compatible = "fsl,imx6ull-pxp", .data = &pxp_imx6ull_pdata },
> > { },
> > };
> > MODULE_DEVICE_TABLE(of, pxp_dt_ids);
next prev parent reply other threads:[~2023-01-06 14:11 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-05 13:47 [PATCH 0/8] media: imx-pxp: add support for i.MX7D Michael Tretter
2023-01-05 13:47 ` [PATCH 1/8] media: dt-bindings: media: fsl-pxp: convert to yaml Michael Tretter
2023-01-06 3:18 ` Rob Herring
2023-01-06 8:23 ` Michael Tretter
2023-01-06 11:35 ` Laurent Pinchart
2023-01-06 12:34 ` Krzysztof Kozlowski
2023-01-05 13:47 ` [PATCH 2/8] media: imx-pxp: detect PXP version Michael Tretter
2023-01-06 11:47 ` Laurent Pinchart
2023-01-06 12:28 ` Laurent Pinchart
2023-01-06 14:01 ` Michael Tretter
2023-01-06 18:40 ` Laurent Pinchart
2023-01-05 13:47 ` [PATCH 3/8] media: imx-pxp: extract helper function to setup data path Michael Tretter
2023-01-06 11:59 ` Laurent Pinchart
2023-01-05 13:47 ` [PATCH 4/8] media: imx-pxp: explicitly disable unused blocks Michael Tretter
2023-01-06 12:26 ` Laurent Pinchart
2023-01-06 14:08 ` Michael Tretter
2023-01-06 18:39 ` Laurent Pinchart
2023-01-05 13:47 ` [PATCH 5/8] media: imx-pxp: disable LUT block Michael Tretter
2023-01-06 12:27 ` Laurent Pinchart
2023-01-05 13:47 ` [PATCH 6/8] media: imx-pxp: make data_path_ctrl0 platform dependent Michael Tretter
2023-01-06 12:30 ` Laurent Pinchart
2023-01-06 14:11 ` Michael Tretter [this message]
2023-01-06 18:42 ` Laurent Pinchart
2023-01-05 13:47 ` [PATCH 7/8] media: imx-pxp: add support for i.MX7D Michael Tretter
2023-01-06 12:32 ` Laurent Pinchart
2023-01-05 13:47 ` [PATCH 8/8] ARM: dts: imx7d: add node for PXP Michael Tretter
2023-01-06 12:36 ` Laurent Pinchart
2023-01-06 14:36 ` Michael Tretter
2023-01-06 18:43 ` Laurent Pinchart
2023-01-06 12:41 ` [PATCH 0/8] media: imx-pxp: add support for i.MX7D Laurent Pinchart
2023-01-06 14:42 ` Michael Tretter
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20230106141141.GE24101@pengutronix.de \
--to=m.tretter@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).