devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Konstantin Aladyshev <aladyshev22@gmail.com>
To: unlisted-recipients:; (no To-header on input)
Cc: supreeth.venkatesh@amd.com, aladyshev22@gmail.com,
	Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.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
Subject: [PATCH 0/4] DTS changes for the AMD EthanolX CRB BMC
Date: Sat, 11 Jun 2022 12:58:24 +0300	[thread overview]
Message-ID: <20220611095828.1090-1-aladyshev22@gmail.com> (raw)

Several patches for the DTS of the BMC on the AMD EthanolX CRB.

Konstantin Aladyshev (4):
  ARM: dts: aspeed: ethanolx: Add correct label to flash device
  ARM: dts: aspeed: ethanolx: Configure RTS/CTS for UART1
  ARM: dts: aspeed: ethanolx: Use correct driver for the FRU EEPROM
  ARM: dts: aspeed: ethanolx: Enable VUART

 arch/arm/boot/dts/aspeed-bmc-amd-ethanolx.dts | 14 ++++++++++++--
 1 file changed, 12 insertions(+), 2 deletions(-)

-- 
2.25.1


             reply	other threads:[~2022-06-11  9:58 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11  9:58 Konstantin Aladyshev [this message]
2022-06-11  9:58 ` [PATCH 1/4] ARM: dts: aspeed: ethanolx: Add correct label to flash device Konstantin Aladyshev
2022-07-21  2:31   ` Andrew Jeffery
2022-06-11  9:58 ` [PATCH 2/4] ARM: dts: aspeed: ethanolx: Configure RTS/CTS for UART1 Konstantin Aladyshev
2022-07-21  2:32   ` Andrew Jeffery
2022-06-11  9:58 ` [PATCH 3/4] ARM: dts: aspeed: ethanolx: Use correct driver for the FRU EEPROM Konstantin Aladyshev
2022-06-11  9:58 ` [PATCH 4/4] ARM: dts: aspeed: ethanolx: Enable VUART Konstantin Aladyshev
2022-07-21  2:32   ` Andrew Jeffery

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=20220611095828.1090-1-aladyshev22@gmail.com \
    --to=aladyshev22@gmail.com \
    --cc=andrew@aj.id.au \
    --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=supreeth.venkatesh@amd.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).