From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: "Larson, Bradley" <Bradley.Larson@amd.com>,
Rob Herring <robh@kernel.org>, Brad Larson <brad@pensando.io>
Cc: "adrian.hunter@intel.com" <adrian.hunter@intel.com>,
"alcooperx@gmail.com" <alcooperx@gmail.com>,
"andy.shevchenko@gmail.com" <andy.shevchenko@gmail.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"brijeshkumar.singh@amd.com" <brijeshkumar.singh@amd.com>,
"broonie@kernel.org" <broonie@kernel.org>,
"catalin.marinas@arm.com" <catalin.marinas@arm.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"fancer.lancer@gmail.com" <fancer.lancer@gmail.com>,
"gerg@linux-m68k.org" <gerg@linux-m68k.org>,
"gsomlo@gmail.com" <gsomlo@gmail.com>,
"krzk@kernel.org" <krzk@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"lee.jones@linaro.org" <lee.jones@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
"p.yadav@ti.com" <p.yadav@ti.com>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"piotrs@cadence.com" <piotrs@cadence.com>,
"rdunlap@infradead.org" <rdunlap@infradead.org>,
"samuel@sholland.org" <samuel@sholland.org>,
"Suthikulpanit, Suravee" <Suravee.Suthikulpanit@amd.com>,
"Lendacky, Thomas" <Thomas.Lendacky@amd.com>,
"ulf.hansson@linaro.org" <ulf.hansson@linaro.org>,
"will@kernel.org" <will@kernel.org>,
"yamada.masahiro@socionext.com" <yamada.masahiro@socionext.com>
Subject: Re: [PATCH v8 06/17] dt-bindings: mfd: amd,pensando-elbasr: Add AMD Pensando Elba System Resource chip
Date: Thu, 17 Nov 2022 13:33:30 +0100 [thread overview]
Message-ID: <56e640fe-d3b7-31f1-2171-5040a7e043d2@linaro.org> (raw)
In-Reply-To: <BL0PR12MB2401ECC21B2EA83A5D806E369B069@BL0PR12MB2401.namprd12.prod.outlook.com>
On 17/11/2022 01:41, Larson, Bradley wrote:
> [AMD Official Use Only - General]
>
> From: Rob Herring <robh@kernel.org>
> Sent: Wednesday, November 16, 2022 2:30 PM
>
>>> v8:
>>> - Apply review request changes and picked the two unique examples
>>> for the 4 chip-selects as one has the reset control support and
>>> the other an interrupt. Missed the --in-reply-to in git
>>> send-email for v7, included in this update.
>>
>> No, you haven't. By default in git, you don't have to do anything. See
>> --thread and --no-chain-reply-to options. If you are messing with
>> --in-reply-to, you are doing it wrong.
>>
>> Please resend the whole series properly threaded.
>
> Will resend the series
>
>>> diff --git a/Documentation/devicetree/bindings/mfd/amd,pensando-elbasr.yaml b/Documentation/devicetree/bindings/mfd/amd,pensando-elbasr.yaml
>>> new file mode 100644
>>> index 000000000000..622c93402a86
>>> --- /dev/null
>> +++ b/Documentation/devicetree/bindings/mfd/amd,pensando-elbasr.yaml
>>> @@ -0,0 +1,60 @@
> ...
>>> +
>>> +title: AMD Pensando Elba SoC Resource Controller
>>> +
>>> +description: |
>>> + AMD Pensando Elba SoC Resource Controller functions are
>>> + accessed with four chip-selects. Reset control is on CS0.
>>
>> One device with 4 chip-selects? Then I'd expect 'reg = <0 1 2 3>;'
>>
>> Hard to say more because I don't have the whole thread nor remember what
>> exactly we discussed before. That was 100s of bindings ago...
>
> I agree and the example for v7 had all 4 chip-selects shown. This is not a pick and
> choose device on what functions to use for a usable system. Krzysztof requested
> only showing two chip-selects in the example.
The problem is that you describe here SPI controller (and its chip
selects) but binding is for the SPI device. The example is not the
problem...
> ...
>>> +examples:
>>> + - |
>>> + #include <dt-bindings/interrupt-controller/arm-gic.h>
>>> +
>>> + spi {
>>> + #address-cells = <1>;
>>> + #size-cells = <0>;
>>> + num-cs = <4>;
Drop this property as well, unless it is necessary to explain
"amd,pensando-elbasr" device.
>>> +
>>> + system-controller@0 {
>>> + compatible = "amd,pensando-elbasr";
>>> + reg = <0>;
>>> + spi-max-frequency = <12000000>;
>>> + #reset-cells = <1>;
>>> + };
Best regards,
Krzysztof
next prev parent reply other threads:[~2022-11-17 12:34 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 1:04 [PATCH v7 06/17] dt-bindings: mfd: amd,pensando-elbasr: Add AMD Pensando Elba System Resource chip Brad Larson
2022-11-16 8:45 ` Krzysztof Kozlowski
2022-11-16 8:46 ` Krzysztof Kozlowski
2022-11-16 19:39 ` [PATCH v8 " Brad Larson
2022-11-16 22:30 ` Rob Herring
2022-11-17 0:41 ` Larson, Bradley
2022-11-17 12:33 ` Krzysztof Kozlowski [this message]
2022-11-17 13:14 ` Rob Herring
2022-11-17 18:37 ` Larson, Bradley
2022-11-18 8:42 ` Geert Uytterhoeven
2022-11-18 18:29 ` Larson, Bradley
2023-01-30 19:12 ` Brad Larson
2023-02-01 9:57 ` Krzysztof Kozlowski
2023-02-06 23:43 ` Brad Larson
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=56e640fe-d3b7-31f1-2171-5040a7e043d2@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=Bradley.Larson@amd.com \
--cc=Suravee.Suthikulpanit@amd.com \
--cc=Thomas.Lendacky@amd.com \
--cc=adrian.hunter@intel.com \
--cc=alcooperx@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=arnd@arndb.de \
--cc=brad@pensando.io \
--cc=brijeshkumar.singh@amd.com \
--cc=broonie@kernel.org \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=fancer.lancer@gmail.com \
--cc=gerg@linux-m68k.org \
--cc=gsomlo@gmail.com \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@vger.kernel.org \
--cc=p.yadav@ti.com \
--cc=p.zabel@pengutronix.de \
--cc=piotrs@cadence.com \
--cc=rdunlap@infradead.org \
--cc=robh@kernel.org \
--cc=samuel@sholland.org \
--cc=ulf.hansson@linaro.org \
--cc=will@kernel.org \
--cc=yamada.masahiro@socionext.com \
/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).