From: Shawn Guo <shawnguo@kernel.org>
To: Changming Huang <jerry.huang@nxp.com>
Cc: leoyang.li@nxp.com, robh+dt@kernel.org, krzk+dt@kernel.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Jianchao Wang <jianchao.wang@nxp.com>
Subject: Re: [PATCH v2] arm64: dts: fsl-ls1028a: add dspi2 support
Date: Mon, 18 Apr 2022 16:16:46 +0800 [thread overview]
Message-ID: <20220418081646.GE391514@dragon> (raw)
In-Reply-To: <20220411091157.1965623-1-jerry.huang@nxp.com>
On Mon, Apr 11, 2022 at 05:11:57PM +0800, Changming Huang wrote:
> Enable MikroBUS SPI port.
>
> Signed-off-by: Jianchao Wang <jianchao.wang@nxp.com>
> Signed-off-by: Changming Huang <jerry.huang@nxp.com>
> ---
> arch/arm64/boot/dts/freescale/fsl-ls1028a-rdb.dts | 13 +++++++++++++
"arm64: dts: fsl-ls1028a-rdb: ..." to make it clear this is a board
rather than SoC change.
> 1 file changed, 13 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/freescale/fsl-ls1028a-rdb.dts b/arch/arm64/boot/dts/freescale/fsl-ls1028a-rdb.dts
> index 68c31cb8eead..6d0508d5abd0 100644
> --- a/arch/arm64/boot/dts/freescale/fsl-ls1028a-rdb.dts
> +++ b/arch/arm64/boot/dts/freescale/fsl-ls1028a-rdb.dts
> @@ -117,6 +117,19 @@ &duart1 {
> status = "okay";
> };
>
> +&dspi2 {
> + bus-num = <2>;
> + status = "okay";
> +
> + mikrobus@0 {
> + compatible = "semtech,sx1301";
Where is the bindings for this?
Shawn
> + reg = <0>;
> + spi-max-frequency = <2000000>;
> + fsl,spi-cs-sck-delay = <1000000>;
> + fsl,spi-sck-cs-delay = <50>;
> + };
> +};
> +
> &enetc_mdio_pf3 {
> sgmii_phy0: ethernet-phy@2 {
> reg = <0x2>;
> --
> 2.25.1
>
prev parent reply other threads:[~2022-04-18 8:17 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-11 9:11 [PATCH v2] arm64: dts: fsl-ls1028a: add dspi2 support Changming Huang
2022-04-18 8:16 ` Shawn Guo [this message]
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=20220418081646.GE391514@dragon \
--to=shawnguo@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=jerry.huang@nxp.com \
--cc=jianchao.wang@nxp.com \
--cc=krzk+dt@kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@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).