devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Osipenko <digetx@gmail.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
	Rob Herring <robh+dt@kernel.org>,
	linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v2 4/5] dt-bindings: memory: lpddr3-timings: convert to dtschema
Date: Sat, 5 Feb 2022 21:50:33 +0300	[thread overview]
Message-ID: <a204a4eb-6615-26db-facf-ad284c1732d7@gmail.com> (raw)
In-Reply-To: <20220205120043.8337-5-krzysztof.kozlowski@canonical.com>

05.02.2022 15:00, Krzysztof Kozlowski пишет:
> +  reg:
> +    maxItems: 1
> +    description: |
> +      Maximum DDR clock frequency for the speed-bin, in Hz.

Why max-freq is specified as a register? At minimum this is inconsistent
with the lpddr2 binding.

  reply	other threads:[~2022-02-05 18:50 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-05 12:00 [PATCH v2 0/5] dt-bindings: memory: convert to dtschema Krzysztof Kozlowski
2022-02-05 12:00 ` [PATCH v2 1/5] dt-bindings: memory: lpddr3: " Krzysztof Kozlowski
2022-02-05 15:36   ` Rob Herring
2022-02-06 11:12     ` Krzysztof Kozlowski
2022-02-05 12:00 ` [PATCH v2 2/5] dt-bindings: memory: lpddr3: adjust IO width to spec Krzysztof Kozlowski
2022-02-05 12:00 ` [PATCH v2 3/5] dt-bindings: memory: lpddr3: deprecated manufacturer ID Krzysztof Kozlowski
2022-02-05 12:00 ` [PATCH v2 4/5] dt-bindings: memory: lpddr3-timings: convert to dtschema Krzysztof Kozlowski
2022-02-05 18:50   ` Dmitry Osipenko [this message]
2022-02-06 11:20     ` Krzysztof Kozlowski
2022-02-06 11:49       ` Dmitry Osipenko
2022-02-06 11:50   ` Dmitry Osipenko
2022-02-05 12:00 ` [PATCH v2 5/5] dt-bindings: memory: lpddr2-timings: " Krzysztof Kozlowski
2022-02-05 18:49   ` Dmitry Osipenko

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=a204a4eb-6615-26db-facf-ad284c1732d7@gmail.com \
    --to=digetx@gmail.com \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski@canonical.com \
    --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).