From: rentao.bupt@gmail.com
To: Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>, Joel Stanley <joel@jms.id.au>,
Andrew Jeffery <andrew@aj.id.au>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
taoren@meta.com
Cc: Tao Ren <rentao.bupt@gmail.com>
Subject: [PATCH 0/3] ARM: dts: aspeed: Fixup Wedge400 dts
Date: Thu, 3 Aug 2023 16:03:21 -0700 [thread overview]
Message-ID: <20230803230324.731268-1-rentao.bupt@gmail.com> (raw)
From: Tao Ren <rentao.bupt@gmail.com>
The patch series fixes a few entries in wedge400 device tree.
Patch #1 sets spi alias in ast2500-facebook-netbmc-common.dtsi (included
by wedge400 dts) to make sure spi bus is consistent with flash labels in
flash layout.
Patch #2 enables more ADC channels in wedge400 dts.
Patch #3 sets eMMC max frequency to 25MHz in wedge400 dts.
Tao Ren (3):
ARM: dts: aspeed: Update spi alias in Facebook AST2500 Common dtsi
ARM: dts: aspeed: wedge400: Enable more ADC channels
ARM: dts: aspeed: wedge400: Set eMMC max frequency
arch/arm/boot/dts/aspeed/aspeed-bmc-facebook-wedge400.dts | 4 +++-
arch/arm/boot/dts/aspeed/ast2500-facebook-netbmc-common.dtsi | 4 ++++
2 files changed, 7 insertions(+), 1 deletion(-)
--
2.40.1
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next reply other threads:[~2023-08-03 23:04 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-03 23:03 rentao.bupt [this message]
2023-08-03 23:03 ` [PATCH 1/3] ARM: dts: aspeed: Update spi alias in Facebook AST2500 Common dtsi rentao.bupt
2023-08-03 23:03 ` [PATCH 2/3] ARM: dts: aspeed: wedge400: Enable more ADC channels rentao.bupt
2023-08-03 23:03 ` [PATCH 3/3] ARM: dts: aspeed: wedge400: Set eMMC max frequency rentao.bupt
2023-08-09 8:08 ` [PATCH 0/3] ARM: dts: aspeed: Fixup Wedge400 dts Joel Stanley
2023-08-10 5:34 ` Tao Ren
2023-08-10 5:37 ` Joel Stanley
2023-08-10 5:58 ` Tao Ren
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=20230803230324.731268-1-rentao.bupt@gmail.com \
--to=rentao.bupt@gmail.com \
--cc=andrew@aj.id.au \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=taoren@meta.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