devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Julius Werner <jwerner@chromium.org>
Cc: Rob Herring <robh+dt@kernel.org>,
	Dmitry Osipenko <digetx@gmail.com>,
	Doug Anderson <dianders@chromium.org>,
	Jian-Jia Su <jjsu@google.com>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 0/4] dt-bindings: memory: Describing LPDDR topology
Date: Wed, 31 Aug 2022 09:34:06 +0300	[thread overview]
Message-ID: <44af0610-63b1-20d2-2c8c-23e84edb519c@linaro.org> (raw)
In-Reply-To: <20220831013359.1807905-1-jwerner@chromium.org>

On 31/08/2022 04:33, Julius Werner wrote:
> This patch series implements a proposal previously discussed on the
> mailing list under the topic `[RFC] Correct memory layout reporting for
> "jedec,lpddr2" and related bindings`. It adds a new jedec,lpddr-channel
> binding which should be used to group nodes of the existing jedec,lpddr
> bindings to describe their relative topology on the system and the
> amount of chips wired in parallel on each channel, as well as their
> different ranks. This also adds bindings for LPDDR4 and LPDDR5 memory
> types and deduplicates some common schema elements between different
> LPDDR types.
> 
> Julius Werner (4):
>   dt-bindings: memory: Factor out common properties of LPDDR bindings
>   dt-bindings: memory: Add numeric LPDDR compatible string variant
>   dt-bindings: memory: Add jedec,lpddr4 and jedec,lpddr5 bindings
>   dt-bindings: memory: Add jedec,lpddrX-channel binding

Thanks for the patches. Where are the users of these bindings? Although
bindings do not have requirement of providing user (as kernel API has),
but this is quite a rework so I want to see that it is applicable. That
it matches real use case and need. I can do it only with real DTS in the
kernel.

Best regards,
Krzysztof

  parent reply	other threads:[~2022-08-31  6:34 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-31  1:33 [PATCH 0/4] dt-bindings: memory: Describing LPDDR topology Julius Werner
2022-08-31  1:33 ` [PATCH 1/4] dt-bindings: memory: Factor out common properties of LPDDR bindings Julius Werner
2022-08-31  6:18   ` Krzysztof Kozlowski
2022-09-01  1:09     ` Julius Werner
2022-09-05 12:32       ` Krzysztof Kozlowski
2022-08-31  6:30   ` Krzysztof Kozlowski
2022-08-31  1:33 ` [PATCH 2/4] dt-bindings: memory: Add numeric LPDDR compatible string variant Julius Werner
2022-08-31  6:23   ` Krzysztof Kozlowski
2022-08-31  1:33 ` [PATCH 3/4] dt-bindings: memory: Add jedec,lpddr4 and jedec,lpddr5 bindings Julius Werner
2022-08-31  6:28   ` Krzysztof Kozlowski
2022-09-01  1:10     ` Julius Werner
2022-09-02 20:24       ` Rob Herring
2022-08-31  1:33 ` [PATCH 4/4] dt-bindings: memory: Add jedec,lpddrX-channel binding Julius Werner
2022-08-31  6:55   ` Krzysztof Kozlowski
2022-09-01  1:11     ` Julius Werner
2022-09-08 13:56       ` Krzysztof Kozlowski
2022-09-09 23:36         ` Julius Werner
2022-08-31  6:34 ` Krzysztof Kozlowski [this message]
2022-09-01  1:05   ` [PATCH 0/4] dt-bindings: memory: Describing LPDDR topology Julius Werner

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=44af0610-63b1-20d2-2c8c-23e84edb519c@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=digetx@gmail.com \
    --cc=jjsu@google.com \
    --cc=jwerner@chromium.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).