mirror of https://lore.kernel.org/lkml/
 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: Sun, 6 Feb 2022 14:49:28 +0300	[thread overview]
Message-ID: <57486a1b-8667-6f51-977f-16343572925e@gmail.com> (raw)
In-Reply-To: <a5bbf115-21a2-7d63-6744-72487b9e756a@canonical.com>

06.02.2022 14:20, Krzysztof Kozlowski пишет:
> On 05/02/2022 19:50, Dmitry Osipenko wrote:
>> 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.
> 
> First of all, this is a conversion, so the bindings already specified
> max-freq that way.

The conversion part looks okay to me.

> Second, I don't know. I think this was some Lukasz's workaround for
> device node without unit address, but I don't see the reason now why it
> was needed.

I see now that actually there is one exynos5422-odroid-core.dtsi that
uses the 'reg' property.

> We could unify it with DDR2 by deprecating 'reg' and introducing
> 'max-freq', in separate commit. But you know, existing bindings are
> already there...

Will be great if you could add another patch to deprecate the 'reg'.
This will prevent returning to this topic in the future if somebody will
be adding lpddr3 timings, it also will make bindings to look consistent.

Thank you!

  reply	other threads:[~2022-02-06 11:53 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: " 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
2022-02-06 11:20     ` Krzysztof Kozlowski
2022-02-06 11:49       ` Dmitry Osipenko [this message]
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=57486a1b-8667-6f51-977f-16343572925e@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

all inboxes | Powered by JetHome®