[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <7aacd99e-d33e-db6f-e84e-0951b172f5a7@gmail.com>
Date: Mon, 4 Jul 2022 11:22:57 +0300
From: Dmitry Osipenko <digetx@...il.com>
To: Julius Werner <jwerner@...omium.org>,
Krzysztof Kozlowski <krzysztof.kozlowski@...onical.com>,
Jian-Jia Su <jjsu@...gle.com>,
Doug Anderson <dianders@...omium.org>,
Rob Herring <robh+dt@...nel.org>,
LKML <linux-kernel@...r.kernel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
Nikola Milosavljevic <mnidza@...look.com>
Subject: Re: [RFC] Correct memory layout reporting for "jedec,lpddr2" and
related bindings
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?
Powered by blists - more mailing lists