From: Ayush Singh <ayush@beagleboard.org>
To: 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>
Cc: greybus-dev@lists.linaro.org, netdev@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Ayush Singh <ayush@beagleboard.org>
Subject: [PATCH 1/3] dt-bindings: net: ti,cc1352p7: Add boot-gpio
Date: Fri, 19 Jul 2024 15:15:10 +0530 [thread overview]
Message-ID: <20240719-beagleplay_fw_upgrade-v1-1-8664d4513252@beagleboard.org> (raw)
In-Reply-To: <20240719-beagleplay_fw_upgrade-v1-0-8664d4513252@beagleboard.org>
boot-gpio (along with reset-gpio) is used to enable bootloader backdoor
for flashing new firmware.
The pin and pin level to enabel bootloader backdoor is configed using
the following CCFG variables in cc1352p7:
- SET_CCFG_BL_CONFIG_BL_PIN_NO
- SET_CCFG_BL_CONFIG_BL_LEVEL
Signed-off-by: Ayush Singh <ayush@beagleboard.org>
---
Documentation/devicetree/bindings/net/ti,cc1352p7.yaml | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/Documentation/devicetree/bindings/net/ti,cc1352p7.yaml b/Documentation/devicetree/bindings/net/ti,cc1352p7.yaml
index 3dde10de4630..a3511bb59b05 100644
--- a/Documentation/devicetree/bindings/net/ti,cc1352p7.yaml
+++ b/Documentation/devicetree/bindings/net/ti,cc1352p7.yaml
@@ -29,6 +29,9 @@ properties:
reset-gpios:
maxItems: 1
+ boot-gpios:
+ maxItems: 1
+
vdds-supply: true
required:
@@ -46,6 +49,7 @@ examples:
clocks = <&sclk_hf 0>, <&sclk_lf 25>;
clock-names = "sclk_hf", "sclk_lf";
reset-gpios = <&pio 35 GPIO_ACTIVE_LOW>;
+ boot-gpios = <&pio 36 GPIO_ACTIVE_LOW>;
vdds-supply = <&vdds>;
};
};
--
2.45.2
next prev parent reply other threads:[~2024-07-19 9:45 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-19 9:45 [PATCH 0/3] Add Firmware Upload support for beagleplay cc1352 Ayush Singh
2024-07-19 9:45 ` Ayush Singh [this message]
2024-07-19 14:55 ` [PATCH 1/3] dt-bindings: net: ti,cc1352p7: Add boot-gpio Conor Dooley
2024-07-22 10:45 ` Ayush Singh
2024-07-22 11:26 ` Conor Dooley
2024-07-21 9:00 ` Simon Horman
2024-07-21 9:01 ` Simon Horman
2024-07-19 9:45 ` [PATCH 2/3] arm64: dts: ti: k3-am625-beagleplay: Add boot-gpios to cc1352p7 Ayush Singh
2024-07-19 9:45 ` [PATCH 3/3] greybus: gb-beagleplay: Add firmware upload API Ayush Singh
2024-07-19 12:39 ` Hariprasad Kelam
2024-07-19 19:15 ` Andrew Lunn
2024-07-19 21:39 ` Alex Elder
2024-07-22 9:10 ` Hariprasad Kelam
2024-07-20 14:33 ` kernel test robot
2024-07-21 8:59 ` 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=20240719-beagleplay_fw_upgrade-v1-1-8664d4513252@beagleboard.org \
--to=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=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;
as well as URLs for NNTP newsgroup(s).