public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Guoniu Zhou <guoniu.zhou@nxp.com>
Cc: Tomi Valkeinen <tomi.valkeinen@ideasonboard.com>,
	Mauro Carvalho Chehab <mchehab@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, Frank Li <Frank.Li@nxp.com>,
	Vladimir Zapolskiy <vz@mleia.com>,
	linux-media@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 1/4] dt-bindings: media: ti,ds90ub953: Add third cell for GPIO controller
Date: Sun, 14 Sep 2025 21:10:08 -0500	[thread overview]
Message-ID: <20250915015309.GA2329507-robh@kernel.org> (raw)
In-Reply-To: <20250911-ds90ub953-v2-1-03ee76eb6b59@nxp.com>

On Thu, Sep 11, 2025 at 04:44:22PM +0800, Guoniu Zhou wrote:
> Add third cell for GPIO controller to select GPIO output source. 0 to
> select output source from local GPIO data, 1 to select output source
> from remote compatible deserializer GPIO data.
> 
> Signed-off-by: Guoniu Zhou <guoniu.zhou@nxp.com>
> ---
>  Documentation/devicetree/bindings/media/i2c/ti,ds90ub953.yaml | 8 +++++---
>  Documentation/devicetree/bindings/media/i2c/ti,ds90ub960.yaml | 4 ++--
>  2 files changed, 7 insertions(+), 5 deletions(-)
> 
> diff --git a/Documentation/devicetree/bindings/media/i2c/ti,ds90ub953.yaml b/Documentation/devicetree/bindings/media/i2c/ti,ds90ub953.yaml
> index 2e129bf573b79e0ca8f25b4ec5fc6ea76c50abd7..de759413a36060d3be6f2c3b67de48ee6e4d29f2 100644
> --- a/Documentation/devicetree/bindings/media/i2c/ti,ds90ub953.yaml
> +++ b/Documentation/devicetree/bindings/media/i2c/ti,ds90ub953.yaml
> @@ -19,10 +19,12 @@ properties:
>        - ti,ds90ub971-q1
>  
>    '#gpio-cells':
> -    const: 2
> +    const: 3
>      description:
>        First cell is the GPIO pin number, second cell is the flags. The GPIO pin
>        number must be in range of [0, 3].
> +      Third cell is GPIO output source(0 for local gpio data, 1 for remote
> +      gpio data from remote compatible deserializer).

Changing the cell size is an ABI break unless 3 cells was supported in 
OS before which I don't think it would be given GPIO cell meaning is 
pretty standardized. You could just all a flag to the 2nd cell I think. 
Or if 0-3 are local GPIOs, then make remote ones a different range.

Rob

  reply	other threads:[~2025-09-15  2:10 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-11  8:44 [PATCH v2 0/4] media: i2c: ds90ub953: Add back channel GPIO support Guoniu Zhou
2025-09-11  8:44 ` [PATCH v2 1/4] dt-bindings: media: ti,ds90ub953: Add third cell for GPIO controller Guoniu Zhou
2025-09-15  2:10   ` Rob Herring [this message]
2025-09-11  8:44 ` [PATCH v2 2/4] media: i2c: ds90ub953: Add back channel GPIO support Guoniu Zhou
2025-09-11  8:44 ` [PATCH v2 3/4] media: i2c: ds90ub953: use devm_mutex_init() to simplify code Guoniu Zhou
2025-09-11  8:44 ` [PATCH v2 4/4] media: i2c: ds90ub953: use guard() " Guoniu Zhou

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=20250915015309.GA2329507-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=Frank.Li@nxp.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=guoniu.zhou@nxp.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-media@vger.kernel.org \
    --cc=mchehab@kernel.org \
    --cc=tomi.valkeinen@ideasonboard.com \
    --cc=vz@mleia.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