From: Cosmo Chou <chou.cosmo@gmail.com>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
joel@jms.id.au, andrew@codeconstruct.com.au
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-aspeed@lists.ozlabs.org, linux-kernel@vger.kernel.org,
cosmo.chou@quantatw.com, Cosmo Chou <chou.cosmo@gmail.com>
Subject: [PATCH v2 0/4] ARM: dts: aspeed: bletchley: Cleanups and second source devices
Date: Wed, 29 Jul 2026 19:43:08 +0800 [thread overview]
Message-ID: <20260729114312.3947300-1-chou.cosmo@gmail.com> (raw)
This series resolves dt-check-style warnings, sorts I2C nodes,
and adds second-source RTC/LED support for the Bletchley.
Changes in v2:
- Added patch to sort I2C device nodes by address.
- Added patch to fix dt-check-style warnings.
- Carried over second-source RTC and LED controller patches from v1.
Cosmo Chou (4):
ARM: dts: aspeed: bletchley: Sort i2c device nodes by address
ARM: dts: aspeed: bletchley: Fix style warnings
ARM: dts: aspeed: bletchley: Add second source PCA9532 LED controllers
ARM: dts: aspeed: bletchley: Add second source ISL1208 RTC
.../aspeed/aspeed-bmc-facebook-bletchley.dts | 1317 +++++++++++------
1 file changed, 903 insertions(+), 414 deletions(-)
--
2.43.0
next reply other threads:[~2026-07-29 11:43 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-29 11:43 Cosmo Chou [this message]
2026-07-29 11:43 ` [PATCH v2 1/4] ARM: dts: aspeed: bletchley: Sort i2c device nodes by address Cosmo Chou
2026-07-29 11:43 ` [PATCH v2 2/4] ARM: dts: aspeed: bletchley: Fix style warnings Cosmo Chou
2026-07-29 11:43 ` [PATCH v2 3/4] ARM: dts: aspeed: bletchley: Add second source PCA9532 LED controllers Cosmo Chou
2026-07-29 12:08 ` sashiko-bot
2026-07-29 11:43 ` [PATCH v2 4/4] ARM: dts: aspeed: bletchley: Add second source ISL1208 RTC Cosmo Chou
2026-07-29 11:51 ` sashiko-bot
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=20260729114312.3947300-1-chou.cosmo@gmail.com \
--to=chou.cosmo@gmail.com \
--cc=andrew@codeconstruct.com.au \
--cc=conor+dt@kernel.org \
--cc=cosmo.chou@quantatw.com \
--cc=devicetree@vger.kernel.org \
--cc=joel@jms.id.au \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-aspeed@lists.ozlabs.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.