Linux Serial subsystem development
 help / color / mirror / Atom feed
From: Hui Wang <hui.wang@canonical.com>
To: Rob Herring <robh@kernel.org>
Cc: linux-serial@vger.kernel.org, devicetree@vger.kernel.org,
	gregkh@linuxfoundation.org, jirislaby@kernel.org,
	hvilleneuve@dimonoff.com
Subject: Re: [PATCH 1/2] dt-bindings: serial: sc16is7xx: add reset-gpios
Date: Tue, 4 Jun 2024 18:35:01 +0800	[thread overview]
Message-ID: <bf7ed22b-e75a-470b-ad69-0ea0be958024@canonical.com> (raw)
In-Reply-To: <20240603131850.GA148307-robh@kernel.org>


On 6/3/24 21:18, Rob Herring wrote:
> On Mon, Jun 03, 2024 at 08:37:09PM +0800, Hui Wang wrote:
>> In some designs, the chip reset pin is connected to a gpio, this
>> gpio needs to be set correctly before probing the driver, so adding
>> a reset-gpios in the device tree.
>>
>> Signed-off-by: Hui Wang <hui.wang@canonical.com>
>> ---
>>   Documentation/devicetree/bindings/serial/nxp,sc16is7xx.yaml | 4 ++++
>>   1 file changed, 4 insertions(+)
>>
>> diff --git a/Documentation/devicetree/bindings/serial/nxp,sc16is7xx.yaml b/Documentation/devicetree/bindings/serial/nxp,sc16is7xx.yaml
>> index 5dec15b7e7c3..62aff6e034cb 100644
>> --- a/Documentation/devicetree/bindings/serial/nxp,sc16is7xx.yaml
>> +++ b/Documentation/devicetree/bindings/serial/nxp,sc16is7xx.yaml
>> @@ -28,6 +28,9 @@ properties:
>>     clocks:
>>       maxItems: 1
>>   
>> +  reset-gpios:
>> +    maxItems: 1
>> +
>>     clock-frequency:
>>       description:
>>         When there is no clock provider visible to the platform, this
>> @@ -120,6 +123,7 @@ examples:
>>               compatible = "nxp,sc16is752";
>>               reg = <0x54>;
>>               clocks = <&clk20m>;
>> +            reset-gpios = <&gpio5 13 GPIO_ACTIVE_LOW>;
> Missing the header for the define.
>
> Test your bindings before sending.

OK, got it.

Thanks.

>
>>               interrupt-parent = <&gpio3>;
>>               interrupts = <7 IRQ_TYPE_EDGE_FALLING>;
>>               nxp,modem-control-line-ports = <0 1>; /* Ports 0 and 1 as modem control lines */
>> -- 
>> 2.34.1
>>

  reply	other threads:[~2024-06-04 10:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-03 12:37 [PATCH 1/2] dt-bindings: serial: sc16is7xx: add reset-gpios Hui Wang
2024-06-03 12:37 ` [PATCH 2/2] serial: sc16is7xx: setup reset pin if it is defined in device tree Hui Wang
2024-06-03 13:11   ` Hugo Villeneuve
2024-06-04 10:34     ` Hui Wang
2024-06-03 13:18 ` [PATCH 1/2] dt-bindings: serial: sc16is7xx: add reset-gpios Rob Herring
2024-06-04 10:35   ` Hui Wang [this message]
2024-06-04  6:54 ` Krzysztof Kozlowski
2024-06-04 10:35   ` Hui Wang

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=bf7ed22b-e75a-470b-ad69-0ea0be958024@canonical.com \
    --to=hui.wang@canonical.com \
    --cc=devicetree@vger.kernel.org \
    --cc=gregkh@linuxfoundation.org \
    --cc=hvilleneuve@dimonoff.com \
    --cc=jirislaby@kernel.org \
    --cc=linux-serial@vger.kernel.org \
    --cc=robh@kernel.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