From: Wei Xu <xuwei5@hisilicon.com>
To: Huisong Li <lihuisong@huawei.com>, <arnd@arndb.de>,
<krzk@kernel.org>, <sudeep.holla@arm.com>,
<rdunlap@infradead.org>, <zenghui.yu@linux.dev>
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 v7 0/3] soc: hisilicon: Support HCCS driver on Kunpeng SoC
Date: Fri, 11 Aug 2023 17:30:56 +0800 [thread overview]
Message-ID: <64D5FFD0.8060008@hisilicon.com> (raw)
In-Reply-To: <20230808023640.25263-1-lihuisong@huawei.com>
Hi Huisong,
On 2023/8/8 10:36, Huisong Li wrote:
> This series add HCCS driver to query the health status and port information
> of HCCS on Kunpeng SoC as well as document all sysfs entries provided by
> this driver.
>
> ---
> v7:
> - split patch 1/2 to make it easier to review.
> - fix a wrong command code in hccs_get_die_all_link_status().
> - remove unused code and fix a log description in error branch.
>
> v6:
> - fix the new entry in MAINTAINERS file to keep alphabetical order
>
> v5:
> - fix document format to eliminate warning of making htmldocs.
>
> v4:
> - remove useless header and reorder linux header.
> - use __ATTR_RO to replace __ATTR for port attributes.
> - add MODULE_DEVICE_TABLE to autoload the driver.
> - update the date to "November 2023".
> - fix some comments about HCCS description.
>
> v3:
> - replace "using_status" with "enable" attribute.
> - fix some comments in codes.
>
> v2:
> - Document all sysfs entries provided by driver.
> - drop 'pcc_type' and 'intr_mode' in struct hccs_dev.
> - using _CRS with PCC GAS to get channel ID instead of _DSD.
> - replace readw_relaxed_poll_timeout with readw_poll_timeout.
> - use sysfs_emit() instead of sprintf().
> - drop ACPI_PTR in hccs_driver.
> - drop useless log during the probe phase.
>
> Huisong Li (3):
> soc: hisilicon: Support HCCS driver on Kunpeng SoC
> soc: hisilicon: add sysfs entry to query information of HCCS
> doc: soc: hisilicon: Add Kunpeng HCCS driver documentation
>
> .../sysfs-devices-platform-kunpeng_hccs | 81 ++
> MAINTAINERS | 7 +
> drivers/soc/Kconfig | 1 +
> drivers/soc/Makefile | 1 +
> drivers/soc/hisilicon/Kconfig | 20 +
> drivers/soc/hisilicon/Makefile | 2 +
> drivers/soc/hisilicon/kunpeng_hccs.c | 1275 +++++++++++++++++
> drivers/soc/hisilicon/kunpeng_hccs.h | 191 +++
> 8 files changed, 1578 insertions(+)
> create mode 100644 Documentation/ABI/testing/sysfs-devices-platform-kunpeng_hccs
> create mode 100644 drivers/soc/hisilicon/Kconfig
> create mode 100644 drivers/soc/hisilicon/Makefile
> create mode 100644 drivers/soc/hisilicon/kunpeng_hccs.c
> create mode 100644 drivers/soc/hisilicon/kunpeng_hccs.h
>
Thanks!
Series applied to the hisilicon driver tree.
Best Regards,
Wei
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
prev parent reply other threads:[~2023-08-11 9:31 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20230424073020.4039-1-lihuisong@huawei.com>
[not found] ` <20230530112746.2767-1-lihuisong@huawei.com>
[not found] ` <02f74b25-2ade-5b87-b316-ab902f08ead2@huawei.com>
[not found] ` <3e106062-9ceb-eb51-70ba-32734c769bd5@kernel.org>
2023-07-18 8:07 ` [PATCH v3 0/2] soc: hisilicon: Support HCCS driver on Kunpeng SoC lihuisong (C)
2023-07-18 10:59 ` Krzysztof Kozlowski
2023-07-18 14:00 ` lihuisong (C)
2023-07-18 11:01 ` Wei Xu
[not found] ` <20230725075706.48939-1-lihuisong@huawei.com>
[not found] ` <20230725075706.48939-2-lihuisong@huawei.com>
[not found] ` <64BF8E10.70301@hisilicon.com>
[not found] ` <55efb8ed-58ea-0de5-4f7f-f2984e326852@huawei.com>
2023-07-27 3:51 ` [PATCH RESEND v3 1/2] " lihuisong (C)
2023-07-28 3:03 ` [PATCH v4 0/2] " 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 ` Wei Xu [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=64D5FFD0.8060008@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=rdunlap@infradead.org \
--cc=soc@kernel.org \
--cc=sudeep.holla@arm.com \
--cc=tanxiaofei@huawei.com \
--cc=wanghuiqiang@huawei.com \
--cc=zenghui.yu@linux.dev \
/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).