From: Rahul T R <r-ravikumar@ti.com>
To: <nm@ti.com>
Cc: <vigneshr@ti.com>, <kristo@kernel.org>, <robh+dt@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<r-ravikumar@ti.com>, <jkridner@gmail.com>
Subject: [PATCH v7 0/2] Enable RPi header on j721e sk
Date: Thu, 3 Nov 2022 23:17:41 +0530 [thread overview]
Message-ID: <20221103174743.16827-1-r-ravikumar@ti.com> (raw)
The following series of patches enables RPi header
on j721e sk. It is a 40 pin io expasion header which
brings out i2c5, ehrpwm 2,3 and some pins of gpio 0,1
v7:
- Rebased to next-20221103
- Move setting status diable to main dtsi
v6:
- Rebased to 6.1-rc1
v5:
- Enable only gpio's and i2c on the RPi Header
as per the discussion in the v4
v4:
- Correct the node name in dt binding example
v3:
- Change node name from clock to clock-controller
- Add correct description for clock-controller node
v2:
- Add full path for clock property $ref
- Remove the discription for clock pattern property,
since $ref is added
- Remove the label in the example
- Fix the indentation in the example
Rahul T R (1):
arm64: dts: ti: k3-j721e-sk: Add pinmux for RPi Header
Vijay Pothukuchi (1):
arm64: dts: ti: k3-j721e-main: Add dts nodes for EHRPWMs
arch/arm64/boot/dts/ti/k3-j721e-main.dtsi | 68 ++++++++++++++++++++++-
arch/arm64/boot/dts/ti/k3-j721e-sk.dts | 59 ++++++++++++++++++++
2 files changed, 126 insertions(+), 1 deletion(-)
--
2.38.0
next reply other threads:[~2022-11-03 17:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-03 17:47 Rahul T R [this message]
2022-11-03 17:47 ` [PATCH v7 1/2] arm64: dts: ti: k3-j721e-main: Add dts nodes for EHRPWMs Rahul T R
2022-11-03 21:53 ` Nishanth Menon
2022-11-04 5:08 ` Rahul T R
2022-11-03 17:47 ` [PATCH v7 2/2] arm64: dts: ti: k3-j721e-sk: Add pinmux for RPi Header Rahul T R
2022-11-03 21:54 ` Nishanth Menon
2022-11-04 5:15 ` Rahul T R
2022-11-04 23:56 ` Nishanth Menon
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=20221103174743.16827-1-r-ravikumar@ti.com \
--to=r-ravikumar@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jkridner@gmail.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@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).