From: Udit Kumar <u-kumar1@ti.com>
To: <linux-arm-kernel@lists.infradead.org>, <afd@ti.com>, <bb@ti.com>,
<vaishnav.a@ti.com>, <j-choudhary@ti.com>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>
Cc: Udit Kumar <u-kumar1@ti.com>
Subject: [PATCH v3 0/2] arm64: dts: ti: k3-j7200-common-proc-board fixes
Date: Wed, 19 Apr 2023 09:30:05 +0530 [thread overview]
Message-ID: <20230419040007.3022780-1-u-kumar1@ti.com> (raw)
This patch series fixes the pin mux configuration and enable
wkup_i2c0 at board level.
Note to self: in u-boot i2c pin mux is set in R5 board file.
which will moved to som file, Fix that too when syncing kernel
and uboot DTS files.
Changes since v2:
https://lore.kernel.org/all/20230418050514.2392717-1-u-kumar1@ti.com/
Pin Mux (Patch 1/1):
- No Change
wkup_i2c:
- Added pin mux
- Added speed
Changes since v1:
https://lore.kernel.org/all/20230414181434.2046049-1-u-kumar1@ti.com/
Pin mux:
- Fixed commit message and author
wkup_i2c:
- Removed Fixes tag in commit message
- Moved wkup_i2c in som instead of common board
- Added eeprom as child device
Keerthy (1):
arm64: dts: ti: k3-j7200: Fix physical address of pin
Udit Kumar (1):
arm64: dts: ti: k3-j7200-som: Enable I2C
.../dts/ti/k3-j7200-common-proc-board.dts | 28 +++++++++----------
arch/arm64/boot/dts/ti/k3-j7200-som-p0.dtsi | 21 ++++++++++++++
2 files changed, 35 insertions(+), 14 deletions(-)
--
2.34.1
next reply other threads:[~2023-04-19 4:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-19 4:00 Udit Kumar [this message]
2023-04-19 4:00 ` [PATCH v3 1/2] arm64: dts: ti: k3-j7200: Fix physical address of pin Udit Kumar
2023-04-19 4:00 ` [PATCH v3 2/2] arm64: dts: ti: k3-j7200-som: Enable I2C Udit Kumar
2023-06-15 13:31 ` [PATCH v3 0/2] arm64: dts: ti: k3-j7200-common-proc-board fixes Vignesh Raghavendra
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=20230419040007.3022780-1-u-kumar1@ti.com \
--to=u-kumar1@ti.com \
--cc=afd@ti.com \
--cc=bb@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=j-choudhary@ti.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=vaishnav.a@ti.com \
--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
all inboxes | Powered by JetHome®