From: Nishanth Menon <nm@ti.com>
To: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>,
<jan.kiszka@siemens.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
<jan.kiszka@siemens.com>, <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/2] arm64: dts: ti: k3-am65: disable optional peripherals by default
Date: Wed, 2 Feb 2022 14:32:17 -0600 [thread overview]
Message-ID: <20220202203217.sf2cr4orwl4usvyf@starry> (raw)
In-Reply-To: <5beef188724ef42b0c2147ca9bf6e6ca25c75dec.1641900122.git.matthias.schiffer@ew.tq-group.com>
On 12:25-20220111, Matthias Schiffer wrote:
> All peripharals that require pinmuxing or other configuration to work
> should be disabled by default. Dependent DTS are adjusted accordingly.
>
> The following nodes are now "disabled" according to dtx_diff and were not
> overridden to "okay", as they define no pinctrl:
>
> k3-am654-base-board:
> - mcu_i2c0
> - mcu_spi0..2
> - cal
> - main_i2c3
> - ehrpwm0..5
> - main_uart1..2
> - main_spi1..4
>
> k3-am65-iot2050*:
> - mci_spi1..2
> - cal
> - ehrpwm0..5
> - main_spi0..4
>
> Signed-off-by: Matthias Schiffer <matthias.schiffer@ew.tq-group.com>
Jan: you ok with this series? Please ack.
--
Regards,
Nishanth Menon
Key (0xDDB5849D1736249D) / Fingerprint: F8A2 8693 54EB 8232 17A3 1A34 DDB5 849D 1736 249D
next prev parent reply other threads:[~2022-02-02 20:32 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-11 11:25 [PATCH 1/2] arm64: dts: ti: k3-am65: disable optional peripherals by default Matthias Schiffer
2022-01-11 11:25 ` [PATCH 2/2] arm64: dts: ti: k3-am65*: remove #address-cells/#size-cells from flash nodes Matthias Schiffer
2022-02-03 12:52 ` Jan Kiszka
2022-01-20 12:32 ` [PATCH 1/2] arm64: dts: ti: k3-am65: disable optional peripherals by default Matthias Schiffer
2022-01-20 12:41 ` Matthias Schiffer
2022-02-02 20:32 ` Nishanth Menon [this message]
2022-02-03 11:39 ` Jan Kiszka
2022-02-03 13:06 ` Matthias Schiffer
2022-02-03 17:28 ` Jan Kiszka
2022-02-04 16:14 ` Kishon Vijay Abraham I
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=20220202203217.sf2cr4orwl4usvyf@starry \
--to=nm@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=jan.kiszka@siemens.com \
--cc=kristo@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=matthias.schiffer@ew.tq-group.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).