From: Dhruva Gole <d-gole@ti.com>
To: Ayush Singh <ayush@beagleboard.org>
Cc: <lorforlinux@beagleboard.org>, <jkridner@beagleboard.org>,
<robertcnelson@beagleboard.org>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Johan Hovold <johan@kernel.org>,
Alex Elder <elder@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
<greybus-dev@lists.linaro.org>, <netdev@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 2/3] arm64: dts: ti: k3-am625-beagleplay: Add bootloader-backdoor-gpios to cc1352p7
Date: Thu, 5 Sep 2024 11:54:38 +0530 [thread overview]
Message-ID: <20240905062438.ae2rajmcoiukjefm@lcpd911> (raw)
In-Reply-To: <20240903-beagleplay_fw_upgrade-v4-2-526fc62204a7@beagleboard.org>
On Sep 03, 2024 at 15:02:19 +0530, Ayush Singh wrote:
> Add bootloader-backdoor-gpios which is required for enabling bootloader
> backdoor for flashing firmware to cc1352p7.
>
> Also fix the incorrect reset-gpio.
A Fixes tag please?
>
> Signed-off-by: Ayush Singh <ayush@beagleboard.org>
> ---
> arch/arm64/boot/dts/ti/k3-am625-beagleplay.dts | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am625-beagleplay.dts b/arch/arm64/boot/dts/ti/k3-am625-beagleplay.dts
> index 70de288d728e..a1cd47d7f5e3 100644
> --- a/arch/arm64/boot/dts/ti/k3-am625-beagleplay.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am625-beagleplay.dts
> @@ -888,7 +888,8 @@ &main_uart6 {
>
> mcu {
> compatible = "ti,cc1352p7";
> - reset-gpios = <&main_gpio0 72 GPIO_ACTIVE_LOW>;
> + bootloader-backdoor-gpios = <&main_gpio0 13 GPIO_ACTIVE_HIGH>;
> + reset-gpios = <&main_gpio0 14 GPIO_ACTIVE_HIGH>;
> vdds-supply = <&vdd_3v3>;
Reviewed-by: Dhruva Gole <d-gole@ti.com>
--
Best regards,
Dhruva Gole
Texas Instruments Incorporated
next prev parent reply other threads:[~2024-09-05 6:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-09-03 9:32 [PATCH v4 0/3] Add Firmware Upload support for beagleplay cc1352 Ayush Singh
2024-09-03 9:32 ` [PATCH v4 1/3] dt-bindings: net: ti,cc1352p7: Add bootloader-backdoor-gpios Ayush Singh
2024-09-05 6:23 ` Dhruva Gole
2024-09-03 9:32 ` [PATCH v4 2/3] arm64: dts: ti: k3-am625-beagleplay: Add bootloader-backdoor-gpios to cc1352p7 Ayush Singh
2024-09-05 6:24 ` Dhruva Gole [this message]
2024-09-03 9:32 ` [PATCH v4 3/3] greybus: gb-beagleplay: Add firmware upload API Ayush Singh
2024-09-10 15:51 ` Simon Horman
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=20240905062438.ae2rajmcoiukjefm@lcpd911 \
--to=d-gole@ti.com \
--cc=ayush@beagleboard.org \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=greybus-dev@lists.linaro.org \
--cc=jkridner@beagleboard.org \
--cc=johan@kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lorforlinux@beagleboard.org \
--cc=netdev@vger.kernel.org \
--cc=nm@ti.com \
--cc=pabeni@redhat.com \
--cc=robertcnelson@beagleboard.org \
--cc=robh@kernel.org \
--cc=vigneshr@ti.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