devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Julius Werner <jwerner@chromium.org>
Cc: linux-kernel@vger.kernel.org, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Doug Anderson <dianders@chromium.org>,
	devicetree@vger.kernel.org, Jian-Jia Su <jjsu@google.com>,
	Dmitry Osipenko <digetx@gmail.com>
Subject: Re: [PATCH 1/4 v4] dt-bindings: memory: Factor out common properties of LPDDR bindings
Date: Thu, 15 Sep 2022 08:44:07 -0500	[thread overview]
Message-ID: <20220915134407.GA1168889-robh@kernel.org> (raw)
In-Reply-To: <20220915003222.1296421-1-jwerner@chromium.org>

On Wed, 14 Sep 2022 17:32:19 -0700, Julius Werner wrote:
> The bindings for different LPDDR versions mostly use the same kinds of
> properties, so in order to reduce duplication when we're adding support
> for more versions, this patch creates a new lpddr-props subschema that
> can be referenced by the others to define these common parts. (This will
> consider a few smaller I/O width and density numbers "legal" for LPDDR3
> that are usually not used there, but this should be harmless.)
> 
> Signed-off-by: Julius Werner <jwerner@chromium.org>
> ---
>  .../ddr/jedec,lpddr-props.yaml                | 52 +++++++++++++++++++
>  .../memory-controllers/ddr/jedec,lpddr2.yaml  | 40 ++------------
>  .../memory-controllers/ddr/jedec,lpddr3.yaml  | 32 ++----------
>  3 files changed, 60 insertions(+), 64 deletions(-)
>  create mode 100644 Documentation/devicetree/bindings/memory-controllers/ddr/jedec,lpddr-props.yaml
> 
> Changelog:
> 
> - v2:
>   - removed minItems
>   - reordered io-width enum from lowest to highest
>   - moved `$ref` below `mainainers`
>   - removed part about undeprecating manufacturer-id
> - v3:
>   - no changes
> - v4:
>   - removed quotes from schema $ref strings
> 


Please add Acked-by/Reviewed-by tags when posting new versions. However,
there's no need to repost patches *only* to add the tags. The upstream
maintainer will do that for acks received on the version they apply.

If a tag was not added on purpose, please state why and what changed.


  parent reply	other threads:[~2022-09-15 13:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-15  0:32 [PATCH 1/4 v4] dt-bindings: memory: Factor out common properties of LPDDR bindings Julius Werner
2022-09-15  0:32 ` [PATCH 2/4 v4] dt-bindings: memory: Add numeric LPDDR compatible string variant Julius Werner
2022-09-15 13:44   ` Rob Herring
2022-09-15  0:32 ` [PATCH 3/4 v4] dt-bindings: memory: Add jedec,lpddr4 and jedec,lpddr5 bindings Julius Werner
2022-09-16 19:31   ` Rob Herring
2022-09-15  0:32 ` [PATCH 4/4 v4] dt-bindings: memory: Add jedec,lpddrX-channel binding Julius Werner
2022-09-15 13:44 ` Rob Herring [this message]
2022-09-30  1:00   ` [PATCH 1/4 v4] dt-bindings: memory: Factor out common properties of LPDDR bindings Julius Werner
2022-09-30  6:51     ` Krzysztof Kozlowski

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=20220915134407.GA1168889-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=digetx@gmail.com \
    --cc=jjsu@google.com \
    --cc=jwerner@chromium.org \
    --cc=krzysztof.kozlowski@linaro.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).