From: Mauro Carvalho Chehab <mchehab@kernel.org>
To: Laurent Pinchart <laurent.pinchart@ideasonboard.com>
Cc: Jenkins <jenkins@linuxtv.org>,
linux-media@vger.kernel.org, builder@linuxtv.org,
Christian Hemp <c.hemp@phytec.de>,
Dong Aisheng <aisheng.dong@nxp.com>,
Guoniu Zhou <guoniu.zhou@nxp.com>,
Jacopo Mondi <jacopo@jmondi.org>,
Stefan Riedmueller <s.riedmueller@phytec.de>
Subject: Re: [GIT PULL FOR v6.3] NXP i.MX8 ISI driver (#89568)
Date: Sat, 15 Apr 2023 11:05:56 +0100 [thread overview]
Message-ID: <20230415110556.25290b53@sal.lan> (raw)
In-Reply-To: <20230323172255.7d67d7ac@coco.lan>
Em Thu, 23 Mar 2023 17:24:30 +0100
Mauro Carvalho Chehab <mchehab@kernel.org> escreveu:
> Em Thu, 23 Mar 2023 01:33:52 +0200
> Laurent Pinchart <laurent.pinchart@ideasonboard.com> escreveu:
>
> > Hi Mauro,
> >
> > On Sun, Mar 19, 2023 at 10:08:21PM +0100, Mauro Carvalho Chehab wrote:
> > > Em Sun, 19 Mar 2023 02:34:23 +0000 Jenkins escreveu:
> > >
> > > > checkpatch.pl:
> > > > $ cat patches/0002-media-nxp-Add-i.MX8-ISI-driver.patch | formail -c | ./scripts/checkpatch.pl --terse --mailback --no-summary --strict
> > > > -:98: WARNING: please write a help paragraph that fully describes the config symbol
> > > > -:112: WARNING: please write a help paragraph that fully describes the config symbol
> > > > -:761: WARNING: DT compatible string "fsl,imx8-isi" appears un-documented -- check ./Documentation/devicetree/bindings/
> > > > -:1128: CHECK: Please use a blank line after function/struct/union/enum declarations
> > > > -:1178: CHECK: Please use a blank line after function/struct/union/enum declarations
> > > > -:1928: CHECK: usleep_range is preferred over udelay; see Documentation/timers/timers-howto.rst
> > >
> > > There are still a couple of checkpatch issues there. Please check.
> > > In special:
> > >
> > > - either DT file is wrong or patch 2. Patch 1 declares:
> > >
> > > properties:
> > > compatible:
> > > enum:
> > > - fsl,imx8mn-isi
> > > - fsl,imx8mp-isi
> > >
> > > But patch 2 has an additional one:
> > >
> > > static const struct of_device_id mxc_isi_of_match[] = {
> > > { .compatible = "fsl,imx8-isi", .data = &mxc_imx8_data_v1 },
> > > { .compatible = "fsl,imx8mn-isi", .data = &mxc_imx8mn_data },
> > > { .compatible = "fsl,imx8mp-isi", .data = &mxc_imx8mp_data },
> > > { /* sentinel */ },
> >
> > Indeed, that should be fixed. Would you mind if I addressed this on top
> > ? I will be travelling next week, which would delay a new pull request
> > to v6.3-rc5. That's still within the allowed time frame, but if I get
> > delayed a bit more, I'm worried about missing the v6.4 merge window.
> >
> > I will actively maintain the ISI driver and will fix this for v6.5 at
> > the latest if I can't make it for v6.4. It shouldn't cause any
> > regression for supported DT bindings, and the "fsl,imx8-isi" compatible
> > string isn't listed in the bindings and won't be used in device tree
> > sources.
> >
> > > - Instead of udelay(300, could it use, instead usleep_range()?
> >
> > This could be fixed on top too.
>
> Sure. Feel free to add patches on the top.
Jus re-checked the PR. DT is still broken there:
WARNING: DT compatible string "fsl,imx8-isi" appears un-documented -- check ./Documentation/devicetree/bindings/
#894: FILE: drivers/media/platform/nxp/imx8-isi/imx8-isi-core.c:624:
+ { .compatible = "fsl,imx8-isi", .data = &mxc_imx8_data_v1 },
total: 0 errors, 5 warnings, 6215 lines checked
Please fix.
Regards,
Mauro
next prev parent reply other threads:[~2023-04-15 10:06 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 9:51 [GIT PULL FOR v6.3] NXP i.MX8 ISI driver Laurent Pinchart
2023-02-27 13:44 ` Adam Ford
2023-02-27 14:33 ` Laurent Pinchart
2023-03-19 2:34 ` [GIT PULL FOR v6.3] NXP i.MX8 ISI driver (#89568) Jenkins
2023-03-19 21:08 ` Mauro Carvalho Chehab
2023-03-22 23:33 ` Laurent Pinchart
2023-03-23 16:24 ` Mauro Carvalho Chehab
2023-03-25 23:18 ` Laurent Pinchart
2023-04-15 10:05 ` Mauro Carvalho Chehab [this message]
2023-04-15 10:20 ` Laurent Pinchart
2023-04-15 12:07 ` Mauro Carvalho Chehab
2023-03-19 10:44 ` Jenkins
2023-04-15 10:20 ` Jenkins
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=20230415110556.25290b53@sal.lan \
--to=mchehab@kernel.org \
--cc=aisheng.dong@nxp.com \
--cc=builder@linuxtv.org \
--cc=c.hemp@phytec.de \
--cc=guoniu.zhou@nxp.com \
--cc=jacopo@jmondi.org \
--cc=jenkins@linuxtv.org \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-media@vger.kernel.org \
--cc=s.riedmueller@phytec.de \
/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