From: Horatiu Vultur <horatiu.vultur@microchip.com>
To: <devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Cc: <robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<nicolas.ferre@microchip.com>, <alexandre.belloni@bootlin.com>,
<claudiu.beznea@microchip.com>, <arnd@arndb.de>, <olof@lixom.net>,
<soc@kernel.org>, <UNGLinuxDriver@microchip.com>,
<maxime.chevallier@bootlin.com>,
Horatiu Vultur <horatiu.vultur@microchip.com>
Subject: [PATCH 0/2] ARM: add support for pcb8309
Date: Wed, 20 Jul 2022 21:49:02 +0200 [thread overview]
Message-ID: <20220720194904.2025384-1-horatiu.vultur@microchip.com> (raw)
Add documentation and add the pcb8309.
It features a LAN9662 SoC with 2 internal copport ports and two SFP cages.
Horatiu Vultur (2):
dt-bindings: arm: at91: add lan966 pcb8309 board
ARM: dts: lan966x: add support for pcb8309
.../devicetree/bindings/arm/atmel-at91.yaml | 6 +
arch/arm/boot/dts/Makefile | 3 +-
arch/arm/boot/dts/lan966x-pcb8309.dts | 189 ++++++++++++++++++
3 files changed, 197 insertions(+), 1 deletion(-)
create mode 100644 arch/arm/boot/dts/lan966x-pcb8309.dts
--
2.33.0
next reply other threads:[~2022-07-20 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-20 19:49 Horatiu Vultur [this message]
2022-07-20 19:49 ` [PATCH 1/2] dt-bindings: arm: at91: add lan966 pcb8309 board Horatiu Vultur
2022-07-21 6:46 ` Krzysztof Kozlowski
2022-07-22 12:52 ` Horatiu Vultur
2022-07-20 19:49 ` [PATCH 2/2] ARM: dts: lan966x: add support for pcb8309 Horatiu Vultur
2022-07-21 6:08 ` Kavyasree.Kotagiri
2022-07-22 12:46 ` Horatiu Vultur - M31836
2022-07-21 7:39 ` Claudiu.Beznea
2022-07-22 12:48 ` Horatiu Vultur - M31836
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=20220720194904.2025384-1-horatiu.vultur@microchip.com \
--to=horatiu.vultur@microchip.com \
--cc=UNGLinuxDriver@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=arnd@arndb.de \
--cc=claudiu.beznea@microchip.com \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=maxime.chevallier@bootlin.com \
--cc=nicolas.ferre@microchip.com \
--cc=olof@lixom.net \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).