From: <Claudiu.Beznea@microchip.com>
To: <Horatiu.Vultur@microchip.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Cc: <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<Nicolas.Ferre@microchip.com>, <UNGLinuxDriver@microchip.com>,
<maxime.chevallier@bootlin.com>
Subject: Re: [PATCH 1/3] ARM: dts: lan966x: Add gpio-restart
Date: Tue, 19 Jul 2022 07:52:29 +0000 [thread overview]
Message-ID: <3e0b7137-08d1-fef2-86b5-a48419dd2101@microchip.com> (raw)
In-Reply-To: <20220718212921.1506984-2-horatiu.vultur@microchip.com>
On 19.07.2022 00:29, Horatiu Vultur wrote:
> The pcb8291 can be rebooted by toggling the GPIO 56. Therefore enable
> this in DT.
>
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>
> ---
> arch/arm/boot/dts/lan966x-pcb8291.dts | 6 ++++++
> 1 file changed, 6 insertions(+)
>
> diff --git a/arch/arm/boot/dts/lan966x-pcb8291.dts b/arch/arm/boot/dts/lan966x-pcb8291.dts
> index d56d2054c38d..02fbf7371a8d 100644
> --- a/arch/arm/boot/dts/lan966x-pcb8291.dts
> +++ b/arch/arm/boot/dts/lan966x-pcb8291.dts
> @@ -16,6 +16,12 @@ chosen {
> aliases {
> serial0 = &usart3;
> };
> +
> + gpio-restart {
> + compatible = "gpio-restart";
> + gpios = <&gpio 56 GPIO_ACTIVE_LOW>;
Could you, please, add also pinctrl-names, pinctrl-0 for this gpio?
> + priority = <200>;
> + };
> };
>
> &gpio {
next prev parent reply other threads:[~2022-07-19 7:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-18 21:29 [PATCH 0/3] ARM: dts: lan966x: Extend pcb8291 Horatiu Vultur
2022-07-18 21:29 ` [PATCH 1/3] ARM: dts: lan966x: Add gpio-restart Horatiu Vultur
2022-07-19 7:52 ` Claudiu.Beznea [this message]
2022-07-19 20:02 ` Horatiu Vultur - M31836
2022-07-18 21:29 ` [PATCH 2/3] ARM: dts: lan966x: Disable can0 on pcb8291 Horatiu Vultur
2022-07-19 7:55 ` Claudiu.Beznea
2022-07-19 20:03 ` Horatiu Vultur - M31836
2022-07-18 21:29 ` [PATCH 3/3] ARM: dts: lan966x: Enable network driver " Horatiu Vultur
2022-07-19 7:58 ` Claudiu.Beznea
2022-07-19 20:03 ` Horatiu Vultur - M31836
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=3e0b7137-08d1-fef2-86b5-a48419dd2101@microchip.com \
--to=claudiu.beznea@microchip.com \
--cc=Horatiu.Vultur@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=robh+dt@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
all inboxes | Powered by JetHome®