From: Frank Li <Frank.li@nxp.com>
To: Guoniu Zhou <guoniu.zhou@nxp.com>
Cc: Tomi Valkeinen <tomi.valkeinen@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>,
linux-media@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, imx@lists.linux.dev
Subject: Re: [PATCH v3 1/4] dt-bindings: media: ti,ds90ub953: Add new range for remote GPIO data
Date: Tue, 16 Sep 2025 10:23:13 -0400 [thread overview]
Message-ID: <aMly0eRgNRB2VqU9@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <20250916-ds90ub953-v3-1-bb7bc6545da7@nxp.com>
On Tue, Sep 16, 2025 at 05:43:43PM +0800, Guoniu Zhou wrote:
> The DS90UB953 supports four pins, GPIO0 through GPIO3. When enabled as an
> output, it can be programed to output local data or remote data coming
> from the remote compatible deserializer.
>
> Make a different GPIO range for remote ones.
>
> Signed-off-by: Guoniu Zhou <guoniu.zhou@nxp.com>
> ---
> Documentation/devicetree/bindings/media/i2c/ti,ds90ub953.yaml | 8 ++++++--
> 1 file changed, 6 insertions(+), 2 deletions(-)
>
> diff --git a/Documentation/devicetree/bindings/media/i2c/ti,ds90ub953.yaml b/Documentation/devicetree/bindings/media/i2c/ti,ds90ub953.yaml
> index 2e129bf573b79e0ca8f25b4ec5fc6ea76c50abd7..234276a8738a7fbe9fadad62f12366697da97b11 100644
> --- a/Documentation/devicetree/bindings/media/i2c/ti,ds90ub953.yaml
> +++ b/Documentation/devicetree/bindings/media/i2c/ti,ds90ub953.yaml
> @@ -20,9 +20,13 @@ properties:
>
> '#gpio-cells':
> const: 2
> - description:
> + description: |
suppose should be >
The second style is folded which is indicated by ">" character. In addition
to maintaining line breaks on double line breaks, the folded style also
maintains leading whitespace beyond indentation of the first line. The line
breaks on indented lines are also maintained.
Frank
> First cell is the GPIO pin number, second cell is the flags. The GPIO pin
> - number must be in range of [0, 3].
> + number must be in range of [0, 3] when enabled as an input.
> +
> + If enabled as an output, the GPIO pin number must be in range of
> + [0, 7] and [0, 3] for local GPIO data, [4, 7] for GPIO data coming
> + from remote compatible deserializer.
>
> gpio-controller: true
>
>
> --
> 2.34.1
>
next prev parent reply other threads:[~2025-09-16 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 9:43 [PATCH v3 0/4] media: i2c: ds90ub953: Add back channel GPIO support Guoniu Zhou
2025-09-16 9:43 ` [PATCH v3 1/4] dt-bindings: media: ti,ds90ub953: Add new range for remote GPIO data Guoniu Zhou
2025-09-16 14:23 ` Frank Li [this message]
2025-09-16 9:43 ` [PATCH v3 2/4] media: i2c: ds90ub953: Add back channel GPIO support Guoniu Zhou
2025-09-16 9:43 ` [PATCH v3 3/4] media: i2c: ds90ub953: use devm_mutex_init() to simplify code Guoniu Zhou
2025-09-16 14:26 ` Frank Li
2025-09-16 9:43 ` [PATCH v3 4/4] media: i2c: ds90ub953: use guard() " Guoniu Zhou
2025-10-23 8:41 ` [PATCH v3 0/4] media: i2c: ds90ub953: Add back channel GPIO support G.N. 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=aMly0eRgNRB2VqU9@lizhi-Precision-Tower-5810 \
--to=frank.li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=guoniu.zhou@nxp.com \
--cc=imx@lists.linux.dev \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=mchehab@kernel.org \
--cc=robh@kernel.org \
--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: 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
all inboxes | Powered by JetHome®