From: Thierry Reding <thierry.reding@gmail.com>
To: Hans Verkuil <hverkuil@xs4all.nl>,
Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Cc: Linux Media Mailing List <linux-media@vger.kernel.org>,
Sowjanya Komatineni <skomatineni@nvidia.com>,
Rob Herring <robh@kernel.org>
Subject: Re: [GIT PULL FOR v5.8] Add Tegra210 Video input driver
Date: Tue, 5 May 2020 22:22:20 +0200 [thread overview]
Message-ID: <20200505202220.GA1972539@ulmo> (raw)
In-Reply-To: <3c9e6a28-fc6e-0e4d-b7a0-57e3f2e1b206@xs4all.nl>
[-- Attachment #1: Type: text/plain, Size: 4060 bytes --]
On Tue, May 05, 2020 at 04:26:04PM +0200, Hans Verkuil wrote:
> On 05/05/2020 16:15, Mauro Carvalho Chehab wrote:
> > Em Tue, 5 May 2020 14:24:22 +0200
> > Hans Verkuil <hverkuil@xs4all.nl> escreveu:
> >
> >> On 05/05/2020 14:17, Mauro Carvalho Chehab wrote:
> >>> Em Tue, 5 May 2020 10:33:00 +0200
> >>> Hans Verkuil <hverkuil@xs4all.nl> escreveu:
> >>>
> >>>> The following changes since commit e51759f56d314d28c25be7606b03791f048e44c7:
> >>>>
> >>>> media: v4l2-ctrls.h: clarify the p_def argument of v4l2_ctrl_new_std_compound (2020-04-29 12:04:58 +0200)
> >>>>
> >>>> are available in the Git repository at:
> >>>>
> >>>> git://linuxtv.org/hverkuil/media_tree.git tags/br-tegra
> >>>>
> >>>> for you to fetch changes up to 0bba0154ded02babccd59e21c6a27c5ad7d50faf:
> >>>>
> >>>> MAINTAINERS: Add Tegra Video driver section (2020-05-05 10:26:05 +0200)
> >>>>
> >>>> ----------------------------------------------------------------
> >>>> Tag branch
> >>>>
> >>>> ----------------------------------------------------------------
> >>>> Sowjanya Komatineni (2):
> >>>> media: tegra: Add Tegra210 Video input driver
> >>>> MAINTAINERS: Add Tegra Video driver section
> >>>
> >>>
> >>> As pointed by checkpatch:
> >>>
> >>> WARNING: DT compatible string "nvidia,tegra210-csi" appears un-documented -- check ./Documentation/devicetree/bindings/
> >>> #628: FILE: drivers/staging/media/tegra-video/csi.c:521:
> >>> + { .compatible = "nvidia,tegra210-csi", .data = &tegra210_csi_soc },
> >>>
> >>> WARNING: DT compatible string "nvidia,tegra210-csi" appears un-documented -- check ./Documentation/devicetree/bindings/
> >>> #3238: FILE: drivers/staging/media/tegra-video/video.c:106:
> >>> + { .compatible = "nvidia,tegra210-csi", },
> >>>
> >>> and double-checked with:
> >>>
> >>> $ git grep "nvidia,tegra210-csi"
> >>> drivers/staging/media/tegra-video/csi.c: { .compatible = "nvidia,tegra210-csi", .data = &tegra210_csi_soc },
> >>> drivers/staging/media/tegra-video/video.c: { .compatible = "nvidia,tegra210-csi", },
> >>>
> >>> The DT specs for this driver are missing. I even checked at linux-next:
> >>> there's no DT bindings for this.
> >>
> >> Sorry, I should have mentioned this in the cover letter: the binding file
> >> is here: https://patchwork.linuxtv.org/patch/63576/
> >>
> >> But it will be merged via the tegra subsystem (Thierry Reding) since it is
> >> part of the display bindings, not media bindings. Also, Thierry was planning
> >> to convert it to yaml, so he offered to merge it instead.
> >
> > Ok. Please re-send the pull request (or just mark it as New on patchwork)
> > once the bindings arrive linux-next.
>
> It's still marked as New in patchwork :-) (https://patchwork.linuxtv.org/patch/63596/)
>
> >
> > Alternatively, I don't mind if those patches would also be merged via
> > Tegra's tree, together with the bindings. On such case, feel free to
> > add, for both patches:
> >
> > Reviewed-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
Mauro, do you mind if I turn that into an Acked-by? I think the ARM SoC
maintainers may prefer that as being more of an explicit statement than
Reviewed-by: that it's fine to take this through ARM SoC.
>
> Thierry, let us know what you want to do. It might not be a bad idea to merge
> the whole series through your tree, as Mauro suggested. It keeps everything
> together.
I can do that. For ARM SoC I typically create a for-X.Y/dt-bindings
branch where I collect device tree bindings patches that don't have
a better place anywhere else, so I'll probably stick the DT binding
update into that branch and then I can base a for-5.8/media branch
on top of that to resolve the checkpatch warnings.
Actually, once I have that I could even just send a PR to Mauro to
take this through the media tree since the dependencies should all
be resolved. But with an Acked-by I'm sure the ARM SoC maintainers
won't mind picking this up.
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-05-05 20:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-05 8:33 [GIT PULL FOR v5.8] Add Tegra210 Video input driver Hans Verkuil
2020-05-05 8:42 ` [GIT PULL FOR v5.8] Add Tegra210 Video input driver (#63596) Jenkins
2020-05-05 12:17 ` [GIT PULL FOR v5.8] Add Tegra210 Video input driver Mauro Carvalho Chehab
2020-05-05 12:24 ` Hans Verkuil
2020-05-05 14:15 ` Mauro Carvalho Chehab
2020-05-05 14:26 ` Hans Verkuil
2020-05-05 20:22 ` Thierry Reding [this message]
2020-05-05 20:39 ` Mauro Carvalho Chehab
-- strict thread matches above, loose matches on Subject: below --
2020-04-24 12:00 Hans Verkuil
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=20200505202220.GA1972539@ulmo \
--to=thierry.reding@gmail.com \
--cc=hverkuil@xs4all.nl \
--cc=linux-media@vger.kernel.org \
--cc=mchehab+huawei@kernel.org \
--cc=robh@kernel.org \
--cc=skomatineni@nvidia.com \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.