From: <Tudor.Ambarus@microchip.com>
To: <Eugen.Hristev@microchip.com>, <robh+dt@kernel.org>,
<Nicolas.Ferre@microchip.com>
Cc: <alexandre.belloni@bootlin.com>,
<Ludovic.Desroches@microchip.com>, <soc@kernel.org>,
<devicetree@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <Claudiu.Beznea@microchip.com>,
<Codrin.Ciubotariu@microchip.com>
Subject: Re: [PATCH v3 2/4] ARM: dts: at91: add sama7g5 SoC DT and sama7g5-ek
Date: Thu, 13 May 2021 13:42:13 +0000 [thread overview]
Message-ID: <e68afc06-4ad9-9feb-8082-94f4ed7245da@microchip.com> (raw)
In-Reply-To: <20210513061354.138158-2-eugen.hristev@microchip.com>
cut
> diff --git a/arch/arm/boot/dts/at91-sama7g5ek.dts b/arch/arm/boot/dts/at91-sama7g5ek.dts
> new file mode 100644
> index 000000000000..d71c3224a0f9
> --- /dev/null
> +++ b/arch/arm/boot/dts/at91-sama7g5ek.dts
> @@ -0,0 +1,705 @@
cut
> +&flx11 {
> + atmel,flexcom-mode = <ATMEL_FLEXCOM_MODE_SPI>;
> + status = "okay";
> +
> + spi0: spi@400 {
> + compatible = "atmel,at91rm9200-spi";
The spi function for flx11 should be described in the SoC dt. You may check
what I did at:
https://www.mail-archive.com/linux-kernel@vger.kernel.org/msg2159037.html
Cheers,
ta
next prev parent reply other threads:[~2021-05-13 13:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-13 6:13 [PATCH v3 1/4] dt-bindings: ARM: at91: document sama7g5ek board Eugen Hristev
2021-05-13 6:13 ` [PATCH v3 2/4] ARM: dts: at91: add sama7g5 SoC DT and sama7g5-ek Eugen Hristev
2021-05-13 13:42 ` Tudor.Ambarus [this message]
2021-05-13 6:13 ` [PATCH v3 3/4] ARM: configs: at91: add defconfig for sama7 family of SoCs Eugen Hristev
2021-05-13 6:13 ` [PATCH v3 4/4] ARM: multi_v7_defconfig: add sama7g5 SoC Eugen Hristev
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=e68afc06-4ad9-9feb-8082-94f4ed7245da@microchip.com \
--to=tudor.ambarus@microchip.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=Codrin.Ciubotariu@microchip.com \
--cc=Eugen.Hristev@microchip.com \
--cc=Ludovic.Desroches@microchip.com \
--cc=Nicolas.Ferre@microchip.com \
--cc=alexandre.belloni@bootlin.com \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--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).