linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Nishanth Menon <nm@ti.com>
To: Sebastian Fricke <sebastian.fricke@collabora.com>
Cc: Geert Uytterhoeven <geert+renesas@glider.be>,
	Nas Chung <nas.chung@chipsnmedia.com>,
	Jackson Lee <jackson.lee@chipsnmedia.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Robert Beckett <bob.beckett@collabora.com>,
	Hans Verkuil <hverkuil-cisco@xs4all.nl>,
	Nicolas Dufresne <nicolas.dufresne@collabora.com>,
	Vignesh Raghavendra <vigneshr@ti.com>,
	Tero Kristo <kristo@kernel.org>, <linux-media@vger.kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH -next] media: chips-media: VIDEO_WAVE_VPU should depend on ARCH_K3
Date: Fri, 1 Dec 2023 00:11:12 -0600	[thread overview]
Message-ID: <20231201061112.jvera4kirvoqseqz@reseal> (raw)
In-Reply-To: <20231130100647.pbgk7oqgynx3pzrw@basti-XPS-13-9310>

On 11:07-20231130, Sebastian Fricke wrote:
> Hey Geert,
> 
> Thanks for the patch!
> 
> Could you please adjust the subject line to:
> media: chips-media: wave5: VIDEO_WAVE_VPU should depend on ARCH_K3
>                     ^^^^^^
> 
> On 28.11.2023 19:26, Geert Uytterhoeven wrote:
> > The Chips&Media Wave 5 Series multi-standard codec IP is currently only
> > supported on Texas Instruments K3 J721S2 SoC.  Hence add a dependency on
> 
> While it is true that is currently only tested on the K3 architecture ,
> it is not only supported by that exact SoC, as you can see here:
> https://lore.kernel.org/all/20231127223718.2651185-4-b-brnich@ti.com/T/
> 
> So, maybe this commit is worded better with:
> 
> is currently only supported on the Texas Instruments K3 architecture.
> 
> The change however is obviously correct.
> 
> Greetings,
> Sebastian
> 
> > ARCH_K3, to prevent asking the user about this driver when configuring a
> > kernel without Texas Instruments K3 Multicore SoC support.
> > 
> > Fixes: 9707a6254a8a6b97 ("media: chips-media: wave5: Add the v4l2 layer")

Thank you Sebastian, in addition, a nitpick: checkpatch.pl complains:
Please use correct Fixes: style 'Fixes: <12 chars of sha1> ("<title line>")'
https://docs.kernel.org/process/submitting-patches.html
Quote:

If your patch fixes a bug in a specific commit, e.g. you found an
issue using git bisect, please use the 'Fixes:' tag with the first 12
characters of the SHA-1 ID, and the one line summary. Do not split
the tag across multiple lines, tags are exempt from the "wrap at 75
columns" rule in order to simplify parsing scripts


with the above fixed, please feel free to add:
Reviewed-by: Nishanth Menon <nm@ti.com>

> > Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
> > ---
> > drivers/media/platform/chips-media/wave5/Kconfig | 1 +
> > 1 file changed, 1 insertion(+)
> > 
> > diff --git a/drivers/media/platform/chips-media/wave5/Kconfig b/drivers/media/platform/chips-media/wave5/Kconfig
> > index 77e7ae5c8f35f454..9ccc1f7e32f3874f 100644
> > --- a/drivers/media/platform/chips-media/wave5/Kconfig
> > +++ b/drivers/media/platform/chips-media/wave5/Kconfig
> > @@ -3,6 +3,7 @@ config VIDEO_WAVE_VPU
> > 	tristate "Chips&Media Wave Codec Driver"
> > 	depends on V4L_MEM2MEM_DRIVERS
> > 	depends on VIDEO_DEV && OF
> > +	depends on ARCH_K3 || COMPILE_TEST
> > 	select VIDEOBUF2_DMA_CONTIG
> > 	select VIDEOBUF2_VMALLOC
> > 	select V4L2_MEM2MEM_DEV

-- 
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3  1A34 DDB5 849D 1736 249D

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

      reply	other threads:[~2023-12-01  6:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-28 18:26 [PATCH -next] media: chips-media: VIDEO_WAVE_VPU should depend on ARCH_K3 Geert Uytterhoeven
2023-11-30 10:07 ` Sebastian Fricke
2023-12-01  6:11   ` Nishanth Menon [this message]

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=20231201061112.jvera4kirvoqseqz@reseal \
    --to=nm@ti.com \
    --cc=bob.beckett@collabora.com \
    --cc=geert+renesas@glider.be \
    --cc=hverkuil-cisco@xs4all.nl \
    --cc=jackson.lee@chipsnmedia.com \
    --cc=kristo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=nas.chung@chipsnmedia.com \
    --cc=nicolas.dufresne@collabora.com \
    --cc=sebastian.fricke@collabora.com \
    --cc=vigneshr@ti.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 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).