From: Hari Prasath <Hari.PrasathGE@microchip.com>
To: <nicolas.ferre@microchip.com>, <claudiu.beznea@microchip.com>,
<davem@davemloft.net>, <krzysztof.kozlowski+dt@linaro.org>,
<alexandre.belloni@bootlin.com>, <arnd@arndb.de>,
<olof@lixom.net>, <soc@kernel.org>, <manikandan.m@microchip.com>,
<michael@walle.cc>, <horatiu.vultur@microchip.com>,
<kavyasree.kotagiri@microchip.com>, <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <durai.manickamkr@microchip.com>
Cc: <Hari.PrasathGE@microchip.com>
Subject: [linux][PATCH 0/6] Add support for sam9x60 curiosity board
Date: Wed, 7 Sep 2022 14:50:48 +0530 [thread overview]
Message-ID: <20220907092054.29915-1-Hari.PrasathGE@microchip.com> (raw)
This patch series addresses the following:
- Moving of flexcom definitions from board file to SoC file plus
some minor changes to its properties.
- Add support for the new sam9x60 curiosity board based on the
existing sam9x60 SoC.
Durai Manickam KR (1):
ARM: dts: at91: sam9x60: Add missing flexcom definitions
Hari Prasath (2):
ARM: dts: at91: sam9x60: Move flexcom definitions to the SoC dtsi
ARM: dts: at91: sam9x60: Add DMA bindigs for the flexcom nodes
Manikandan M (3):
ARM: dts: at91: sam9x60: Fix the label numbering for the flexcom
functions
ARM: dts: at91: sam9x60: Specify the FIFO size for the Flexcom UART
ARM: dts: at91: sam9x60_curiosity: Add device tree for
sam9x60_curiosity board
.../devicetree/bindings/arm/atmel-at91.yaml | 6 +
arch/arm/boot/dts/Makefile | 1 +
arch/arm/boot/dts/at91-sam9x60_curiosity.dts | 532 +++++++++++++++
arch/arm/boot/dts/at91-sam9x60ek.dts | 49 +-
arch/arm/boot/dts/sam9x60.dtsi | 623 ++++++++++++++++++
5 files changed, 1172 insertions(+), 39 deletions(-)
create mode 100644 arch/arm/boot/dts/at91-sam9x60_curiosity.dts
--
2.17.1
next reply other threads:[~2022-09-07 9:21 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-07 9:20 Hari Prasath [this message]
2022-09-07 9:20 ` [linux][PATCH 1/6] ARM: dts: at91: sam9x60: Fix the label numbering for the flexcom functions Hari Prasath
2022-09-07 9:20 ` [linux][PATCH 2/6] ARM: dts: at91: sam9x60: Move flexcom definitions to the SoC dtsi Hari Prasath
2022-09-08 7:59 ` Claudiu.Beznea
2022-09-07 9:20 ` [linux][PATCH 3/6] ARM: dts: at91: sam9x60: Specify the FIFO size for the Flexcom UART Hari Prasath
2022-09-07 9:20 ` [linux][PATCH 4/6] ARM: dts: at91: sam9x60: Add DMA bindigs for the flexcom nodes Hari Prasath
2022-09-08 7:58 ` Claudiu.Beznea
2022-09-07 9:20 ` [linux][PATCH 5/6] ARM: dts: at91: sam9x60: Add missing flexcom definitions Hari Prasath
2022-09-08 7:58 ` Claudiu.Beznea
2022-09-07 9:20 ` [linux][PATCH 6/6] ARM: dts: at91: sam9x60_curiosity: Add device tree for sam9x60_curiosity board Hari Prasath
2022-09-08 7:58 ` Claudiu.Beznea
2022-09-08 11:04 ` Krzysztof Kozlowski
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=20220907092054.29915-1-Hari.PrasathGE@microchip.com \
--to=hari.prasathge@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=claudiu.beznea@microchip.com \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=durai.manickamkr@microchip.com \
--cc=horatiu.vultur@microchip.com \
--cc=kavyasree.kotagiri@microchip.com \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manikandan.m@microchip.com \
--cc=michael@walle.cc \
--cc=nicolas.ferre@microchip.com \
--cc=olof@lixom.net \
--cc=soc@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 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®