From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Florian Fainelli <f.fainelli@gmail.com>, linux-kernel@vger.kernel.org
Cc: Broadcom internal kernel review list
<bcm-kernel-feedback-list@broadcom.com>,
"moderated list:BROADCOM BCM7XXX ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 2/3] Documentation: sysfs: brcmstb-memc: Document new attributes
Date: Mon, 27 Mar 2023 18:01:48 +0200 [thread overview]
Message-ID: <676afe98-c39d-47e9-8d06-3ac88bc7404f@linaro.org> (raw)
In-Reply-To: <20230324165231.3468069-3-f.fainelli@gmail.com>
On 24/03/2023 17:52, Florian Fainelli wrote:
> Document the DDR rank, size, total size, width and type attributes.
>
> Signed-off-by: Florian Fainelli <f.fainelli@gmail.com>
> ---
> .../ABI/testing/sysfs-platform-brcmstb-memc | 39 +++++++++++++++++++
> 1 file changed, 39 insertions(+)
>
> diff --git a/Documentation/ABI/testing/sysfs-platform-brcmstb-memc b/Documentation/ABI/testing/sysfs-platform-brcmstb-memc
> index 2f2b750ac2fd..bc969c02b85f 100644
> --- a/Documentation/ABI/testing/sysfs-platform-brcmstb-memc
> +++ b/Documentation/ABI/testing/sysfs-platform-brcmstb-memc
> @@ -1,3 +1,42 @@
> +What: /sys/bus/platform/devices/*/ddr_rank
> +Date: March 2023
> +KernelVersion: 6.3
We are now at v6.3, so this cannot go into current cycle. Date is also
not realistic. Target v6.4 and it's date from the crystal ball.
> +Contact: Florian Fainelli <f.fainelli@gmail.com>
> +Description:
> + Displays whether the device is single or dual rank.
> +
> +What: /sys/bus/platform/devices/*/ddr_size
> +Date: March 2023
> +KernelVersion: 6.3
> +Contact: Florian Fainelli <f.fainelli@gmail.com>
> +Description:
> + This field specifies the size of each DRAM device in the first
> + (or only) rank
Why only first rank? Have in mind that one physical chip can have
multiple ranks and the interface should be ready for it. Otherwise soon
you will have to break it to support different sizes in different ranks.
> +
> +What: /sys/bus/platform/devices/*/ddr_total_width
> +Date: March 2023
> +KernelVersion: 6.3
> +Contact: Florian Fainelli <f.fainelli@gmail.com>
> +Description:
> + This field specifies the total data width of all DRAM devices
> + (in each rank)
Sorry, I do not understand. "Total" and "in each" are a bit
contradictory. Also misses units description. Is this
> +
> +What: /sys/bus/platform/devices/*/ddr_type
> +Date: March 2023
> +KernelVersion: 6.3
> +Contact: Florian Fainelli <f.fainelli@gmail.com>
> +Description:
> + This field specifies DRAM technology type. Possible values:
> + DDR2, DDR3, DDR4, GDDR5, GDDR5M, LPDDR4.
> +
> +What: /sys/bus/platform/devices/*/ddr_width
> +Date: March 2023
> +KernelVersion: 6.3
> +Contact: Florian Fainelli <f.fainelli@gmail.com>
> +Description:
> + This field specifies the data width of each DRAM device.
Width in which units? And width of what exactly? data-bus? Then bits and
make it maybe "ddr_width_bits" and print 8/16/32. Is it IO width (number
of DQ pins)? Then it could be also up to 128 in general.
Best regards,
Krzysztof
next prev parent reply other threads:[~2023-03-27 16:02 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-24 16:52 [PATCH 0/3] memory: brcmstb_memc: Report more DDR information Florian Fainelli
2023-03-24 16:52 ` [PATCH 1/3] memory: brcmstb_memc: Cache configuration register value Florian Fainelli
2023-03-24 16:52 ` [PATCH 2/3] Documentation: sysfs: brcmstb-memc: Document new attributes Florian Fainelli
2023-03-27 16:01 ` Krzysztof Kozlowski [this message]
2023-03-24 16:52 ` [PATCH 3/3] memory: brcmstb_memc: Add new DDR attributes Florian Fainelli
2023-03-27 16:04 ` 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=676afe98-c39d-47e9-8d06-3ac88bc7404f@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=bcm-kernel-feedback-list@broadcom.com \
--cc=f.fainelli@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.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®