From: Laurent Pinchart <laurent.pinchart@ideasonboard.com> To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com> Cc: linux-renesas-soc@vger.kernel.org, linux-media@vger.kernel.org, dri-devel@lists.freedesktop.org, Kieran Bingham <kieran.bingham@ideasonboard.com>, Nicolas Dufresne <nicolas@ndufresne.ca>, Geert Uytterhoeven <geert@linux-m68k.org>, Dave Airlie <airlied@gmail.com>, Daniel Vetter <daniel@ffwll.ch>, Mauro Carvalho Chehab <mchehab@kernel.org>, Hans Verkuil <hverkuil-cisco@xs4all.nl> Subject: Re: [PATCH v3 0/7] media/drm: renesas: Add new pixel formats Date: Tue, 17 Jan 2023 15:38:25 +0200 [thread overview] Message-ID: <Y8ak0SD1YLUZt0Pz@pendragon.ideasonboard.com> (raw) In-Reply-To: <479e1dca-8d9c-cc75-75d9-3148ccc54f68@ideasonboard.com> Hi Tomi, (CC'ing Mauro and Hans) On Tue, Jan 10, 2023 at 04:25:37PM +0200, Tomi Valkeinen wrote: > On 26/12/2022 16:56, Laurent Pinchart wrote: > > Hi Tomi, > > > > (CC'ing Daniel and Dave) > > > > On Wed, Dec 21, 2022 at 11:24:41AM +0200, Tomi Valkeinen wrote: > >> From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com> > >> > >> Hi, > >> > >> These add new pixel formats for Renesas V3U and V4H SoCs. > >> > >> As the display pipeline is split between DRM and V4L2 components, this > >> series touches both subsystems. I'm sending all these together to > >> simplify review. If needed, I can later split this to V4L2 and DRM > >> parts, of which the V4L2 part needs to be merged first. > > > > As the changes on the DRM side are small and shouldn't conflict with > > anything else queued for v6.3, it would be easier to merge the whole > > series through the media tree. Daniel, Dave, would you be OK with that ? > > If so, could you please ack patches 6/7 and 7/7 ? > > Note that these patches depend on the two DRM driver patches in "[PATCH > v5 0/7] Renesas V4H DSI & DP output support", which are not very small > (but still not big). Good point. I'm thus leaning more towards merging this through the DRM tree then. Mauro, can we get your ack on the V4L2 part of this series ? We'll create a stable branch based on v6.2-rc1 in case it also need to be merged in the media tree due to last minute conflicts (I'm mainly thinking about the new formats). Hans, as there won't be a pull request through the media tree, if you want to review the new formats, now would be a good time. > I don't think there's a compile-time dependency between the DRM and V4L2 > parts, but there's a functional side dependency, so it would be nice to > merge these via a single tree. I can't say if DRM or V4L2 tree is > easier, but I don't expect conflicts either way. -- Regards, Laurent Pinchart
WARNING: multiple messages have this Message-ID (diff)
From: Laurent Pinchart <laurent.pinchart@ideasonboard.com> To: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com> Cc: Kieran Bingham <kieran.bingham@ideasonboard.com>, dri-devel@lists.freedesktop.org, Nicolas Dufresne <nicolas@ndufresne.ca>, linux-renesas-soc@vger.kernel.org, Geert Uytterhoeven <geert@linux-m68k.org>, Hans Verkuil <hverkuil-cisco@xs4all.nl>, Mauro Carvalho Chehab <mchehab@kernel.org>, linux-media@vger.kernel.org Subject: Re: [PATCH v3 0/7] media/drm: renesas: Add new pixel formats Date: Tue, 17 Jan 2023 15:38:25 +0200 [thread overview] Message-ID: <Y8ak0SD1YLUZt0Pz@pendragon.ideasonboard.com> (raw) In-Reply-To: <479e1dca-8d9c-cc75-75d9-3148ccc54f68@ideasonboard.com> Hi Tomi, (CC'ing Mauro and Hans) On Tue, Jan 10, 2023 at 04:25:37PM +0200, Tomi Valkeinen wrote: > On 26/12/2022 16:56, Laurent Pinchart wrote: > > Hi Tomi, > > > > (CC'ing Daniel and Dave) > > > > On Wed, Dec 21, 2022 at 11:24:41AM +0200, Tomi Valkeinen wrote: > >> From: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com> > >> > >> Hi, > >> > >> These add new pixel formats for Renesas V3U and V4H SoCs. > >> > >> As the display pipeline is split between DRM and V4L2 components, this > >> series touches both subsystems. I'm sending all these together to > >> simplify review. If needed, I can later split this to V4L2 and DRM > >> parts, of which the V4L2 part needs to be merged first. > > > > As the changes on the DRM side are small and shouldn't conflict with > > anything else queued for v6.3, it would be easier to merge the whole > > series through the media tree. Daniel, Dave, would you be OK with that ? > > If so, could you please ack patches 6/7 and 7/7 ? > > Note that these patches depend on the two DRM driver patches in "[PATCH > v5 0/7] Renesas V4H DSI & DP output support", which are not very small > (but still not big). Good point. I'm thus leaning more towards merging this through the DRM tree then. Mauro, can we get your ack on the V4L2 part of this series ? We'll create a stable branch based on v6.2-rc1 in case it also need to be merged in the media tree due to last minute conflicts (I'm mainly thinking about the new formats). Hans, as there won't be a pull request through the media tree, if you want to review the new formats, now would be a good time. > I don't think there's a compile-time dependency between the DRM and V4L2 > parts, but there's a functional side dependency, so it would be nice to > merge these via a single tree. I can't say if DRM or V4L2 tree is > easier, but I don't expect conflicts either way. -- Regards, Laurent Pinchart
next prev parent reply other threads:[~2023-01-17 13:38 UTC|newest] Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top 2022-12-21 9:24 [PATCH v3 0/7] media/drm: renesas: Add new pixel formats Tomi Valkeinen 2022-12-21 9:24 ` [PATCH v3 1/7] media: Add 2-10-10-10 RGB formats Tomi Valkeinen 2022-12-26 14:48 ` Laurent Pinchart 2022-12-26 14:48 ` Laurent Pinchart 2023-02-08 1:53 ` Akira Yokosawa 2023-02-08 1:53 ` Akira Yokosawa 2023-02-08 7:56 ` Tomi Valkeinen 2023-02-08 7:56 ` Tomi Valkeinen 2023-02-08 8:36 ` Akira Yokosawa 2023-02-08 8:36 ` Akira Yokosawa 2022-12-21 9:24 ` [PATCH v3 2/7] media: Add Y210, Y212 and Y216 formats Tomi Valkeinen 2022-12-26 14:49 ` Laurent Pinchart 2022-12-26 14:49 ` Laurent Pinchart 2023-02-22 15:28 ` Nicolas Dufresne 2023-02-23 13:10 ` Tomi Valkeinen 2023-02-24 18:04 ` Nicolas Dufresne 2022-12-21 9:24 ` [PATCH v3 3/7] media: renesas: vsp1: Change V3U to be gen4 Tomi Valkeinen 2022-12-26 14:51 ` Laurent Pinchart 2022-12-26 14:51 ` Laurent Pinchart 2022-12-21 9:24 ` [PATCH v3 4/7] media: renesas: vsp1: Add V4H SoC version Tomi Valkeinen 2022-12-21 9:24 ` Tomi Valkeinen 2022-12-21 9:24 ` [PATCH v3 5/7] media: renesas: vsp1: Add new formats (2-10-10-10 ARGB, Y210, Y212) Tomi Valkeinen 2022-12-26 14:52 ` Laurent Pinchart 2022-12-26 14:52 ` Laurent Pinchart 2022-12-21 9:24 ` [PATCH v3 6/7] drm: rcar-du: Bump V3U to gen 4 Tomi Valkeinen 2022-12-21 9:24 ` Tomi Valkeinen 2022-12-21 9:24 ` [PATCH v3 7/7] drm: rcar-du: Add new formats (2-10-10-10 ARGB, Y210) Tomi Valkeinen 2022-12-26 14:44 ` Laurent Pinchart 2022-12-26 14:44 ` Laurent Pinchart 2022-12-26 14:56 ` [PATCH v3 0/7] media/drm: renesas: Add new pixel formats Laurent Pinchart 2022-12-26 14:56 ` Laurent Pinchart 2023-01-10 14:25 ` Tomi Valkeinen 2023-01-10 14:25 ` Tomi Valkeinen 2023-01-17 13:38 ` Laurent Pinchart [this message] 2023-01-17 13:38 ` Laurent Pinchart 2023-01-17 16:41 ` Mauro Carvalho Chehab 2023-01-17 16:41 ` Mauro Carvalho Chehab 2023-01-20 8:04 ` 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=Y8ak0SD1YLUZt0Pz@pendragon.ideasonboard.com \ --to=laurent.pinchart@ideasonboard.com \ --cc=airlied@gmail.com \ --cc=daniel@ffwll.ch \ --cc=dri-devel@lists.freedesktop.org \ --cc=geert@linux-m68k.org \ --cc=hverkuil-cisco@xs4all.nl \ --cc=kieran.bingham@ideasonboard.com \ --cc=linux-media@vger.kernel.org \ --cc=linux-renesas-soc@vger.kernel.org \ --cc=mchehab@kernel.org \ --cc=nicolas@ndufresne.ca \ --cc=tomi.valkeinen@ideasonboard.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: linkBe 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.