From: Dmitry Osipenko <digetx@gmail.com>
To: Julius Werner <jwerner@chromium.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@canonical.com>,
Jian-Jia Su <jjsu@google.com>,
Doug Anderson <dianders@chromium.org>,
Rob Herring <robh+dt@kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
Nikola Milosavljevic <mnidza@outlook.com>
Subject: Re: [RFC] Correct memory layout reporting for "jedec,lpddr2" and related bindings
Date: Mon, 4 Jul 2022 11:22:57 +0300 [thread overview]
Message-ID: <7aacd99e-d33e-db6f-e84e-0951b172f5a7@gmail.com> (raw)
In-Reply-To: <CAODwPW9E8wWwxbYKyf4_-JFb4F-JSmLR3qOF_iudjX0f9ndF0A@mail.gmail.com>
15.06.2022 05:25, Julius Werner пишет:
> We need to be able to report the information that's currently encoded
> in the "jedec,lpddr2" binding separately for each channel+rank
> combination, and we need to be able to tell how many LPDDR chips are
> combined under a single memory channel.
Who and why needs that information?
To me it's not a very useful information without knowing how memory
ranges are mapped to the chips and then only kernel drivers should be
able to utilize that info in a meaningful way. What driver are we
talking about?
prev parent reply other threads:[~2022-07-04 8:23 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-15 2:25 [RFC] Correct memory layout reporting for "jedec,lpddr2" and related bindings Julius Werner
2022-06-15 2:28 ` Julius Werner
2022-06-15 19:33 ` Doug Anderson
2022-06-15 21:27 ` Julius Werner
2022-06-15 22:33 ` Doug Anderson
2022-06-15 23:24 ` Julius Werner
2022-06-18 2:17 ` Krzysztof Kozlowski
2022-06-24 9:45 ` Krzysztof Kozlowski
2022-06-30 1:03 ` Julius Werner
2022-06-30 8:05 ` Krzysztof Kozlowski
2022-07-01 0:52 ` Julius Werner
2022-07-01 6:57 ` Krzysztof Kozlowski
2022-07-08 1:20 ` Julius Werner
2022-07-10 15:06 ` Krzysztof Kozlowski
2022-07-20 23:42 ` Julius Werner
2022-07-27 8:47 ` Krzysztof Kozlowski
2022-07-27 14:07 ` Doug Anderson
2022-07-28 7:35 ` Krzysztof Kozlowski
2022-07-28 0:22 ` Julius Werner
2022-07-28 7:38 ` Krzysztof Kozlowski
2022-07-04 8:22 ` Dmitry Osipenko [this message]
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=7aacd99e-d33e-db6f-e84e-0951b172f5a7@gmail.com \
--to=digetx@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=jjsu@google.com \
--cc=jwerner@chromium.org \
--cc=krzysztof.kozlowski@canonical.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mnidza@outlook.com \
--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).