From: Jerry Huang <jerry.huang@nxp.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
"broonie@kernel.org" <broonie@kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
Leo Li <leoyang.li@nxp.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: RE: [EXT] Re: [PATCH 1/2 v4] dt-bindings: dspi: added for semtech sx1301
Date: Thu, 21 Apr 2022 09:35:28 +0000 [thread overview]
Message-ID: <VE1PR04MB647759CE6388FC6182FA0514FEF49@VE1PR04MB6477.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <f6086989-a4c1-4223-fad0-79bd5719432e@linaro.org>
Best Regards
Jerry Huang
-----Original Message-----
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Sent: 2022年4月21日 17:18
To: Jerry Huang <jerry.huang@nxp.com>; broonie@kernel.org; robh+dt@kernel.org; krzysztof.kozlowski+dt@linaro.org; linux-spi@vger.kernel.org; devicetree@vger.kernel.org; linux-kernel@vger.kernel.org; shawnguo@kernel.org; Leo Li <leoyang.li@nxp.com>; linux-arm-kernel@lists.infradead.org
Subject: Re: [EXT] Re: [PATCH 1/2 v4] dt-bindings: dspi: added for semtech sx1301
Caution: EXT Email
On 21/04/2022 11:11, Jerry Huang wrote:
> Please also answer Michael's comments.
>
> [Jerry Huang] I double checked the MikroBus devices, we used two MikcroBus devices:
> BLE P click:
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> mikroe.com%2Fble-p-click&data=05%7C01%7Cjerry.huang%40nxp.com%7C0a
> 1869e140a74bdfdad108da2377d636%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%
> 7C0%7C637861294862753519%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiL
> CJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdat
> a=%2FwswKJZxub37vxhjuDJ1iigspSPpb1U0kUQDxSaz5Yw%3D&reserved=0
> BEE click:
> https://eur01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fwww.
> mikroe.com%2Fbee-click&data=05%7C01%7Cjerry.huang%40nxp.com%7C0a18
> 69e140a74bdfdad108da2377d636%7C686ea1d3bc2b4c6fa92cd99c5c301635%7C0%7C
> 0%7C637861294862753519%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJ
> QIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=
> bE7kpCsNBxoEumCJDbWif%2FX6Ya9px%2BGzWAqPTJ918QI%3D&reserved=0
> Both of them are SPI interface connect to ls1028ardb through MiKcroBus interface.
> So the name "semtech sx1301" is not correct for this node.
I asked to remove the words "Devicetree bindings" and this was not finished.
Now you mention that entire name of device is wrong... It's confusing. I don't know what device you are describing here. I expect you know. :)
What is this binding about exactly?
[Jerry Huang]
I double checked the SPI device used on MikcroBus, which is not sx1301.
Now we have two MikcroBus click boards, BEE click and BLE P click, both of them have the SPI interface through MikcroBus.
So I can't use the previous name "semtech, sx1301".
> How about "mikroe, spi-dev" or any suggestion about it?
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-04-21 9:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-20 7:31 [PATCH 1/2 v4] dt-bindings: dspi: added for semtech sx1301 Changming Huang
2022-04-20 7:31 ` [PATCH 2/2 v4] arm64: dts: fsl-ls1028a: add dspi2 support Changming Huang
2022-04-20 12:06 ` [PATCH 1/2 v4] dt-bindings: dspi: added for semtech sx1301 Krzysztof Kozlowski
2022-04-21 9:11 ` [EXT] " Jerry Huang
2022-04-21 9:18 ` Krzysztof Kozlowski
2022-04-21 9:35 ` Jerry Huang [this message]
2022-04-21 9:44 ` Michael Walle
2022-04-21 10:06 ` Jerry Huang
2022-04-21 11:08 ` Krzysztof Kozlowski
2022-04-21 11:56 ` Michael Walle
2022-04-21 14:23 ` Rob Herring
2022-04-21 15:16 ` Michael Walle
2022-04-21 19:08 ` Rob Herring
2022-04-22 2:19 ` Jerry Huang
2022-04-21 14:27 ` Rob Herring
2022-04-20 13:29 ` Rob Herring
2022-04-21 9:12 ` [EXT] " Jerry Huang
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=VE1PR04MB647759CE6388FC6182FA0514FEF49@VE1PR04MB6477.eurprd04.prod.outlook.com \
--to=jerry.huang@nxp.com \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=shawnguo@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).