From: Wei Xu <xuwei5@hisilicon.com>
To: Huisong Li <lihuisong@huawei.com>, <arnd@arndb.de>,
<krzk@kernel.org>, <sudeep.holla@arm.com>
Cc: <linux-kernel@vger.kernel.org>, <soc@kernel.org>,
<linux-arm-kernel@lists.infradead.org>, <wanghuiqiang@huawei.com>,
<tanxiaofei@huawei.com>, <liuyonglong@huawei.com>
Subject: Re: [PATCH RESEND v3 2/2] doc: soc: hisilicon: Add Kunpeng HCCS driver documentation
Date: Tue, 25 Jul 2023 16:59:10 +0800 [thread overview]
Message-ID: <64BF8EDE.7090304@hisilicon.com> (raw)
In-Reply-To: <20230725075706.48939-3-lihuisong@huawei.com>
Hi Huisong,
On 2023/7/25 15:57, Huisong Li wrote:
> Document the sysfs attributes description provided by HCCS driver on
> Kunpeng SoC.
>
> Signed-off-by: Huisong Li <lihuisong@huawei.com>
> ---
> .../sysfs-devices-platform-kunpeng_hccs | 76 +++++++++++++++++++
> MAINTAINERS | 1 +
> 2 files changed, 77 insertions(+)
> create mode 100644 Documentation/ABI/testing/sysfs-devices-platform-kunpeng_hccs
>
> diff --git a/Documentation/ABI/testing/sysfs-devices-platform-kunpeng_hccs b/Documentation/ABI/testing/sysfs-devices-platform-kunpeng_hccs
> new file mode 100644
> index 000000000000..83ebed801249
> --- /dev/null
> +++ b/Documentation/ABI/testing/sysfs-devices-platform-kunpeng_hccs
> @@ -0,0 +1,76 @@
> +What: /sys/devices/platform/HISI04Bx:00/chipX/all_linked
> + /sys/devices/platform/HISI04Bx:00/chipX/linked_full_lane
> + /sys/devices/platform/HISI04Bx:00/chipX/crc_err_cnt
> +Date: May 2023
Please update the date to "November 2023" to match the 6.6 kernel.
> +KernelVersion: 6.6
> +Contact: Huisong Li <lihuisong@huawei.org>
> +Description:
> + The /sys/devices/platform/HISI04Bx:00/chipX/ directory
> + contains read-only attributes exposing some summarization
> + information of all HCCS ports under a specified chip.
> + The X in 'chipX' indicates the Xth chip on platform.
> +
> + There are following attributes in this directory:
> + ================= ==== =========================================
> + all_linked: (RO) if all enabled ports on this chip are
> + linked (bool).
> + linked_full_lane: (RO) if all linked ports on this chip are full
> + lane (bool).
> + crc_err_cnt: (RO) total CRC err count for all ports on this
> + chip.
> + ============= ==== =============================================
> +
> +What: /sys/devices/platform/HISI04Bx:00/chipX/dieY/all_linked
> + /sys/devices/platform/HISI04Bx:00/chipX/dieY/linked_full_lane
> + /sys/devices/platform/HISI04Bx:00/chipX/dieY/crc_err_cnt
> +Date: May 2023
Ditto.
> +KernelVersion: 6.6
> +Contact: Huisong Li <lihuisong@huawei.org>
> +Description:
> + The /sys/devices/platform/HISI04Bx:00/chipX/dieY/ directory
> + contains read-only attributes exposing some summarization
> + information of all HCCS ports under a specified die.
> + The Y in 'dieY' indicates the hardware id of the die on chip who
> + has chip id X.
> +
> + There are following attributes in this directory:
> + ================= ==== =========================================
> + all_linked: (RO) if all enabled ports on this die are
> + linked (bool).
> + linked_full_lane: (RO) if all linked ports on this die are full
> + lane (bool).
> + crc_err_cnt: (RO) total CRC err count for all ports on this
> + die.
> + ============= ==== =============================================
> +
> +What: /sys/devices/platform/HISI04Bx:00/chipX/dieY/hccsN/type
> + /sys/devices/platform/HISI04Bx:00/chipX/dieY/hccsN/lane_mode
> + /sys/devices/platform/HISI04Bx:00/chipX/dieY/hccsN/enable
> + /sys/devices/platform/HISI04Bx:00/chipX/dieY/hccsN/cur_lane_num
> + /sys/devices/platform/HISI04Bx:00/chipX/dieY/hccsN/lane_mask
> + /sys/devices/platform/HISI04Bx:00/chipX/dieY/hccsN/crc_err_cnt
> +Date: May 2023
Ditto.
Best Regards,
Wei
> +KernelVersion: 6.6
> +Contact: Huisong Li <lihuisong@huawei.org>
> +Description:
> + The /sys/devices/platform/HISI04Bx/chipX/dieX/hccsN/ directory
> + contains read-only attributes exposing information about
> + a HCCS port. The N value in 'hccsN' indicates this port id.
> + The X in 'chipX' indicates the ID of the chip to which the
> + HCCS port belongs. For example, X ranges from to 'n - 1' if the
> + chip number on platform is n.
> + The Y in 'dieY' indicates the hardware id of the die to which
> + the hccs port belongs.
> +
> + The HCCS port have the following attributes:
> + ============= ==== =============================================
> + type: (RO) port type (string), e.g. HCCS-v1 -> H32
> + lane_mode: (RO) the lane mode of this port (string), e.g. x8
> + enable: (RO) indicate if this port is enabled (bool).
> + cur_lane_num: (RO) current lane number of this port.
> + lane_mask: (RO) current lane mask of this port, every bit
> + indicates a lane.
> + crc_err_cnt: (RO) CRC err count on this port.
> + ============= ==== =============================================
> + Note: type, lane_mode and enable are fixed attributes on
> + running platform.
> diff --git a/MAINTAINERS b/MAINTAINERS
> index 4e55ff992171..7a34bab232eb 100644
> --- a/MAINTAINERS
> +++ b/MAINTAINERS
> @@ -9474,6 +9474,7 @@ F: drivers/crypto/hisilicon/zip/
> HISILICON KUNPENG SOC HCCS DRIVER
> M: Huisong Li <lihuisong@huawei.com>
> S: Maintained
> +F: Documentation/ABI/testing/sysfs-devices-platform-kunpeng_hccs
> F: drivers/soc/hisilicon/kunpeng_hccs.c
> F: drivers/soc/hisilicon/kunpeng_hccs.h
>
>
next prev parent reply other threads:[~2023-07-25 8:59 UTC|newest]
Thread overview: 76+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-04-24 7:30 [PATCH] soc: hisilicon: Support HCCS driver on Kunpeng SoC Huisong Li
2023-04-24 8:09 ` Arnd Bergmann
2023-04-25 3:04 ` lihuisong (C)
2023-04-25 6:08 ` Arnd Bergmann
2023-04-25 9:42 ` lihuisong (C)
2023-04-25 10:30 ` Sudeep Holla
2023-04-25 13:00 ` lihuisong (C)
2023-04-25 13:19 ` Sudeep Holla
2023-04-26 12:12 ` lihuisong (C)
2023-05-04 13:16 ` lihuisong (C)
2023-05-15 3:37 ` lihuisong (C)
2023-05-15 13:08 ` Sudeep Holla
2023-05-16 7:35 ` lihuisong (C)
2023-05-16 12:29 ` Sudeep Holla
2023-05-16 14:13 ` lihuisong (C)
2023-05-16 14:35 ` Sudeep Holla
2023-05-17 7:16 ` lihuisong (C)
2023-05-17 9:30 ` Sudeep Holla
2023-05-17 11:35 ` lihuisong (C)
2023-05-17 13:16 ` Sudeep Holla
2023-05-18 8:24 ` lihuisong (C)
2023-05-18 8:38 ` Sudeep Holla
2023-05-18 12:29 ` lihuisong (C)
[not found] ` <faa32ce0-00cd-d24c-f505-beb637904af1@kernel.org>
2023-04-25 3:16 ` lihuisong (C)
2023-04-25 11:24 ` Sudeep Holla
2023-05-22 7:22 ` [PATCH v2 0/2] " Huisong Li
2023-05-22 7:22 ` [PATCH v2 1/2] " Huisong Li
2023-05-23 9:39 ` Sudeep Holla
2023-05-23 11:57 ` lihuisong (C)
2023-05-23 13:41 ` Sudeep Holla
2023-05-24 9:36 ` lihuisong (C)
2023-05-25 2:41 ` lihuisong (C)
2023-05-25 7:35 ` Sudeep Holla
2023-05-25 8:12 ` lihuisong (C)
2023-05-30 2:53 ` lihuisong (C)
2023-05-30 8:43 ` Sudeep Holla
2023-05-30 10:57 ` lihuisong (C)
2023-05-22 7:22 ` [PATCH v2 2/2] doc: soc: hisilicon: Add Kunpeng HCCS driver documentation Huisong Li
2023-05-30 11:27 ` [PATCH v3 0/2] soc: hisilicon: Support HCCS driver on Kunpeng SoC Huisong Li
2023-05-30 11:27 ` [PATCH v3 1/2] " Huisong Li
2023-05-30 11:27 ` [PATCH v3 2/2] doc: soc: hisilicon: Add Kunpeng HCCS driver documentation Huisong Li
2023-06-19 6:32 ` [PATCH v3 0/2] soc: hisilicon: Support HCCS driver on Kunpeng SoC lihuisong (C)
2023-07-14 6:17 ` lihuisong (C)
[not found] ` <3e106062-9ceb-eb51-70ba-32734c769bd5@kernel.org>
2023-07-18 8:07 ` lihuisong (C)
2023-07-18 11:01 ` Wei Xu
[not found] ` <c71ae185-d0e8-75df-1d4b-caab4bdc95a7@kernel.org>
2023-07-18 14:00 ` lihuisong (C)
2023-07-20 12:43 ` lihuisong (C)
2023-07-25 7:57 ` [PATCH RESEND " Huisong Li
2023-07-25 7:57 ` [PATCH RESEND v3 1/2] " Huisong Li
2023-07-25 8:55 ` Wei Xu
2023-07-26 9:54 ` lihuisong (C)
2023-07-27 3:51 ` lihuisong (C)
2023-07-25 15:28 ` Randy Dunlap
2023-07-26 9:48 ` lihuisong (C)
2023-07-25 7:57 ` [PATCH RESEND v3 2/2] doc: soc: hisilicon: Add Kunpeng HCCS driver documentation Huisong Li
2023-07-25 8:59 ` Wei Xu [this message]
2023-07-26 9:56 ` lihuisong (C)
2023-07-28 3:03 ` [PATCH v4 0/2] soc: hisilicon: Support HCCS driver on Kunpeng SoC Huisong Li
2023-07-28 3:03 ` [PATCH v4 1/2] " Huisong Li
2023-07-28 3:03 ` [PATCH v4 2/2] doc: soc: hisilicon: Add Kunpeng HCCS driver documentation Huisong Li
2023-07-29 8:26 ` [PATCH v5 0/2] soc: hisilicon: Support HCCS driver on Kunpeng SoC Huisong Li
2023-07-29 8:26 ` [PATCH v5 1/2] " Huisong Li
2023-07-29 22:43 ` Randy Dunlap
2023-08-01 1:30 ` lihuisong (C)
2023-07-29 8:26 ` [PATCH v5 2/2] doc: soc: hisilicon: Add Kunpeng HCCS driver documentation Huisong Li
2023-08-01 2:41 ` [PATCH v6 0/2] soc: hisilicon: Support HCCS driver on Kunpeng SoC Huisong Li
2023-08-01 2:41 ` [PATCH v6 1/2] " Huisong Li
2023-08-06 15:09 ` Zenghui Yu
2023-08-07 1:14 ` lihuisong (C)
2023-08-07 1:41 ` lihuisong (C)
2023-08-01 2:41 ` [PATCH v6 2/2] doc: soc: hisilicon: Add Kunpeng HCCS driver documentation Huisong Li
2023-08-08 2:36 ` [PATCH v7 0/3] soc: hisilicon: Support HCCS driver on Kunpeng SoC Huisong Li
2023-08-08 2:36 ` [PATCH v7 1/3] " Huisong Li
2023-08-08 2:36 ` [PATCH v7 2/3] soc: hisilicon: add sysfs entry to query information of HCCS Huisong Li
2023-08-08 2:36 ` [PATCH v7 3/3] doc: soc: hisilicon: Add Kunpeng HCCS driver documentation Huisong Li
2023-08-11 9:30 ` [PATCH v7 0/3] soc: hisilicon: Support HCCS driver on Kunpeng SoC Wei Xu
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=64BF8EDE.7090304@hisilicon.com \
--to=xuwei5@hisilicon.com \
--cc=arnd@arndb.de \
--cc=krzk@kernel.org \
--cc=lihuisong@huawei.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=liuyonglong@huawei.com \
--cc=soc@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=tanxiaofei@huawei.com \
--cc=wanghuiqiang@huawei.com \
/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