Linux Tegra architecture development
 help / color / mirror / Atom feed
From: David Heidelberg <david@ixit.cz>
To: Kieran Bingham <kieran.bingham@ideasonboard.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jacopo Mondi <jacopo@jmondi.org>,
	Sakari Ailus <sakari.ailus@linux.intel.com>,
	Jimmy Su <jimmy.su@intel.com>,
	Matthias Fend <matthias.fend@emfend.at>,
	Mikhail Rudenko <mike.rudenko@gmail.com>,
	Daniel Scally <dan.scally@ideasonboard.com>,
	Jacopo Mondi <jacopo.mondi@ideasonboard.com>,
	Michael Riesch <michael.riesch@collabora.com>,
	Benjamin Mugnier <benjamin.mugnier@foss.st.com>,
	Sylvain Petinot <sylvain.petinot@foss.st.com>,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Paul Elder <paul.elder@ideasonboard.com>,
	Martin Kepplinger <martin.kepplinger@puri.sm>,
	Quentin Schulz <quentin.schulz@theobroma-systems.com>,
	Tommaso Merciai <tomm.merciai@gmail.com>,
	Svyatoslav Ryhel <clamor95@gmail.com>,
	Richard Acayan <mailingradian@gmail.com>,
	Thierry Reding <thierry.reding@kernel.org>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Frank Li <Frank.Li@nxp.com>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <festevam@gmail.com>,
	Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Geert Uytterhoeven <geert+renesas@glider.be>,
	Magnus Damm <magnus.damm@gmail.com>,
	Heiko Stuebner <heiko@sntech.de>
Cc: linux-kernel@vger.kernel.org, linux-media@vger.kernel.org,
	devicetree@vger.kernel.org, linux-tegra@vger.kernel.org,
	linux@ew.tq-group.com, imx@lists.linux.dev,
	linux-arm-kernel@lists.infradead.org,
	linux-arm-msm@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
	linux-rockchip@lists.infradead.org,
	Conor Dooley <conor.dooley@microchip.com>,
	Vladimir Zapolskiy <vladimir.zapolskiy@linaro.org>,
	Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Kieran Bingham <kieran.bingham+renesas@ideasonboard.com>,
	Laurent Pinchart <laurent.pinchart+renesas@ideasonboard.com>
Subject: Re: [PATCH v3 0/7] dt-bindings: Orientation defines
Date: Wed, 29 Jul 2026 19:07:53 +0200	[thread overview]
Message-ID: <cadefce1-076b-4349-9d96-80d524652017@ixit.cz> (raw)
In-Reply-To: <20260628-kbingham-orientation-v3-0-4ed92968aff8@ideasonboard.com>

On 28/06/2026 12:22, Kieran Bingham wrote:
> Add a new dt-bindings/media/video-interface-devices.h header that
> initially supports the Orientation types and convert existing users
> throughout the code base.
> 
> v3 collects tags, and fixes the typo, but drops all hunks that do not
> apply on the media-next tree so that these changes can be merged. Once
> the core feature is accepted a second sweep will convert remaining (new)
> additions of the orientation field.
> 
> v2:
>   - Now expands from the original v1 "dt-bindings: media: Add macros for
>     video interface devices" to update
>     Documentation/devicetree/bindings/media/video-interface-devices.yaml
>     and extend to actually change all users to the new types.
>   - Link to v2: https://lore.kernel.org/r/20260626-kbingham-orientation-v2-0-47178be927b4@ideasonboard.com
> 
> v3:
>   - Fix the arch/arm/boot/dts/nvidia/tegra30-lg-x3.dtsi
>     MEDIA_ORIENTATION_REAR to MEDIA_ORIENTATION_BACK
>     - Though this patch is dropped from this series to post the main
>       integration through the media tree.
>   - Drop (temporarily) changes to:
>      - arch/arm/boot/dts/nvidia/tegra30-lg-x3.dtsi
>      - arch/arm64/boot/dts/qcom/sdm670-google-common.dtsi
>      - arch/arm64/boot/dts/rockchip/rk3588-rock-5b-plus-radxa-cam4k-cam0.dtso
>      - arch/arm64/boot/dts/rockchip/rk3588-rock-5b-plus-radxa-cam4k-cam1.dtso
>   - Non applying changes will be re-posted after the core feature
>     lands in linux-next, or after those changes appear in media-next.
> 
> ---
> Kieran Bingham (7):
>        dt-bindings: media: Add macros for video interface devices
>        media: dt-bindings: video-interface-devices: add video-interface-devices.h references
>        dt-bindings: media: i2c: Utilise video-interface-devices enums
>        arm64: dts: freescale: Convert to new media orientation definitions
>        arm64: dts: qcom: Convert to new media orientation definitions
>        arm64: dts: renesas: Convert to new media orientation definitions
>        arm64: dts: rockchip: Convert to new media orientation definitions
> 
series,
Reviewed-by: David Heidelberg <david@ixit.cz>

Thank you!
David

      parent reply	other threads:[~2026-07-29 17:08 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-28 10:22 [PATCH v3 0/7] dt-bindings: Orientation defines Kieran Bingham
2026-06-28 10:22 ` [PATCH v3 1/7] dt-bindings: media: Add macros for video interface devices Kieran Bingham
2026-07-10  8:16   ` Michael Riesch
2026-06-28 10:22 ` [PATCH v3 2/7] media: dt-bindings: video-interface-devices: add video-interface-devices.h references Kieran Bingham
2026-06-28 15:09   ` Krzysztof Kozlowski
2026-07-10  8:18   ` Michael Riesch
2026-06-28 10:22 ` [PATCH v3 3/7] dt-bindings: media: i2c: Utilise video-interface-devices enums Kieran Bingham
2026-06-29 11:09   ` Benjamin Mugnier
2026-06-28 10:22 ` [PATCH v3 4/7] arm64: dts: freescale: Convert to new media orientation definitions Kieran Bingham
2026-06-29  6:52   ` Alexander Stein
2026-06-28 10:22 ` [PATCH v3 5/7] arm64: dts: qcom: " Kieran Bingham
2026-06-28 10:22 ` [PATCH v3 6/7] arm64: dts: renesas: " Kieran Bingham
2026-06-28 10:22 ` [PATCH v3 7/7] arm64: dts: rockchip: " Kieran Bingham
2026-06-29  9:56   ` Quentin Schulz
2026-07-29 17:07 ` David Heidelberg [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=cadefce1-076b-4349-9d96-80d524652017@ixit.cz \
    --to=david@ixit.cz \
    --cc=Frank.Li@nxp.com \
    --cc=andersson@kernel.org \
    --cc=benjamin.mugnier@foss.st.com \
    --cc=clamor95@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=conor.dooley@microchip.com \
    --cc=dan.scally@ideasonboard.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=heiko@sntech.de \
    --cc=imx@lists.linux.dev \
    --cc=jacopo.mondi@ideasonboard.com \
    --cc=jacopo@jmondi.org \
    --cc=jimmy.su@intel.com \
    --cc=jonathanh@nvidia.com \
    --cc=kernel@pengutronix.de \
    --cc=kieran.bingham+renesas@ideasonboard.com \
    --cc=kieran.bingham@ideasonboard.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=laurent.pinchart+renesas@ideasonboard.com \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=linux-renesas-soc@vger.kernel.org \
    --cc=linux-rockchip@lists.infradead.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=linux@ew.tq-group.com \
    --cc=magnus.damm@gmail.com \
    --cc=mailingradian@gmail.com \
    --cc=martin.kepplinger@puri.sm \
    --cc=matthias.fend@emfend.at \
    --cc=mchehab@kernel.org \
    --cc=michael.riesch@collabora.com \
    --cc=mike.rudenko@gmail.com \
    --cc=paul.elder@ideasonboard.com \
    --cc=quentin.schulz@theobroma-systems.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=sakari.ailus@linux.intel.com \
    --cc=sylvain.petinot@foss.st.com \
    --cc=thierry.reding@kernel.org \
    --cc=tomm.merciai@gmail.com \
    --cc=vladimir.zapolskiy@linaro.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