From: "Daniel Walker (danielwa)" <danielwa@cisco.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: "xe-linux-external(mailer list)" <xe-linux-external@cisco.com>,
"Marcin Wierzbicki -X (mawierzb - GLOBALLOGIC INC at Cisco)"
<mawierzb@cisco.com>, Rob Herring <robh+dt@kernel.org>,
Daniel Walker <dwalker@fifo99.com>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] dt-bindings: cisco: document the CrayAR compatibles
Date: Fri, 7 Apr 2023 15:15:54 +0000 [thread overview]
Message-ID: <20230407151554.GB1391488@zorba> (raw)
In-Reply-To: <4555d5e8-0403-99bc-9cc2-26b72ea5be3b@kernel.org>
On Fri, Apr 07, 2023 at 08:51:12AM +0200, Krzysztof Kozlowski wrote:
> On 06/04/2023 21:15, Daniel Walker (danielwa) wrote:
> > On Thu, Apr 06, 2023 at 08:56:06PM +0200, Krzysztof Kozlowski wrote:
> >> On 06/04/2023 20:32, Daniel Walker (danielwa) wrote:
> >>>>>>> +++ b/Documentation/devicetree/bindings/arm/cisco/crayar.yaml
> >>>>>>
> >>>>>> How many (or not many) platforms do you expect from Cisco? We mostly
> >>>>>> have one file per SoC manufacturer.
> >>>>>
> >>>>> We have two SoC's one called CrayAR and another called Craw. I've submitted the
> >>>>> Craw dts file before , but I've not resubmitted it. Under Craw I think we have
> >>>>> at least two, but more likely five variations. CrayAR we have one variation with
> >>>>> at least one more planned.
> >>>>>
> >>>>> So we would plan over time to add two dtsi files and three to four dts files to
> >>>>> this directory. Then more over time.
> >>>>
> >>>> So just keep them in one file maybe.
> >>>
> >>> If/when I submit again with anther chip we can discuss it at that time.
> >>
> >> Or you can do it now.
> >
> > What do you want to talk about exactly ? You said keep everything in one file, doesn't this
> > already fit your suggestion ? I'm only submitting one file.
>
> That is supposed to be one file named like: cisco.yaml
> If you ever need to have separate maintainers, then split it.
Ok.
Daniel
next prev parent reply other threads:[~2023-04-07 15:16 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-05 22:30 [PATCH v2 2/2] dt-bindings: cisco: document the CrayAR compatibles Daniel Walker
2023-04-06 7:12 ` Krzysztof Kozlowski
2023-04-06 15:15 ` Daniel Walker (danielwa)
2023-04-06 16:50 ` Krzysztof Kozlowski
2023-04-06 18:32 ` Daniel Walker (danielwa)
2023-04-06 18:56 ` Krzysztof Kozlowski
2023-04-06 19:15 ` Daniel Walker (danielwa)
2023-04-07 6:51 ` Krzysztof Kozlowski
2023-04-07 15:15 ` Daniel Walker (danielwa) [this message]
2023-04-07 16:04 ` Daniel Walker (danielwa)
2023-04-10 15:28 ` Krzysztof Kozlowski
2023-04-10 17:09 ` Daniel Walker (danielwa)
2023-04-10 17:51 ` Daniel Walker (danielwa)
2023-04-12 7:24 ` Krzysztof Kozlowski
2023-04-12 15:04 ` Daniel Walker (danielwa)
2023-04-12 16:13 ` Krzysztof Kozlowski
2023-04-12 17:01 ` Daniel Walker (danielwa)
2023-04-12 17:18 ` Krzysztof Kozlowski
2023-04-12 18:51 ` Daniel Walker (danielwa)
2023-04-12 13:50 ` Rob Herring
2023-04-12 15:05 ` Daniel Walker (danielwa)
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=20230407151554.GB1391488@zorba \
--to=danielwa@cisco.com \
--cc=devicetree@vger.kernel.org \
--cc=dwalker@fifo99.com \
--cc=krzk@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mawierzb@cisco.com \
--cc=robh+dt@kernel.org \
--cc=xe-linux-external@cisco.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