linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Jonathan Cameron <Jonathan.Cameron@Huawei.com>
To: Huisong Li <lihuisong@huawei.com>
Cc: <xuwei5@hisilicon.com>, <linux-kernel@vger.kernel.org>,
	<soc@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
	<krzk@kernel.org>, <wanghuiqiang@huawei.com>,
	<liuyonglong@huawei.com>
Subject: Re: [PATCH v2 0/6] Add some features and bugfix for kunpeng_hccs
Date: Fri, 23 Aug 2024 10:02:11 +0100	[thread overview]
Message-ID: <20240823100211.00002b9d@Huawei.com> (raw)
In-Reply-To: <20240823031059.32579-1-lihuisong@huawei.com>

On Fri, 23 Aug 2024 11:10:53 +0800
Huisong Li <lihuisong@huawei.com> wrote:

> This series are intended to support the low power feature for specified
> HCCS and add used HCCS types sysfs. In addition, fix some bugfix and
> enhance some codes.

Quick process thing.  Don't send a v2 like this in reply to v1
(for most kernel subsystems anyway, maybe there are some that request
this?).

Most people still review in email clients and they often start at latest
and work back until they run out of time.  Thus a reply to an earlier
thread is not read!

Jonathan

> 
> ---
>  v2:
>   - remove "this patch" words in commit log suggested by Krzyszto.
>   - use for_each_set_bit to replace the cycle scanning all HCCS IP.
>   - add a patch to rename the 'lane_mode' to 'max_lane_num' to make it
>     easy to see.
>   - add doc description into the code patch.
>   - rename the name of the low power interface.
>   - adjust the increasing and decreasing lane interface description.
>   - do not create available_inc_dec_lane_types when no HCCS type support
>     low power.
> ---
> 
> Huisong Li (6):
>   soc: hisilicon: kunpeng_hccs: Fix a PCC typo
>   soc: hisilicon: kunpeng_hccs: Return failure on having not die or port
>     information
>   soc: hisilicon: kunpeng_hccs: Add the check for base address and size
>     of shared memory
>   soc: hisilicon: kunpeng_hccs: Fix the 'lane_mode' field name in port
>     info structure to 'max_lane_num'
>   soc: hisilicon: kunpeng_hccs: Add used HCCS types sysfs
>   soc: hisilicon: kunpeng_hccs: Support low power feature for the
>     specified HCCS type
> 
>  .../sysfs-devices-platform-kunpeng_hccs       |  45 ++
>  drivers/soc/hisilicon/Kconfig                 |   7 +-
>  drivers/soc/hisilicon/kunpeng_hccs.c          | 516 +++++++++++++++++-
>  drivers/soc/hisilicon/kunpeng_hccs.h          |  33 +-
>  4 files changed, 582 insertions(+), 19 deletions(-)
> 



  parent reply	other threads:[~2024-08-23  9:11 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-18  7:11 [PATCH 0/5] Add some features and bugfix for kunpeng_hccs Huisong Li
2024-07-18  7:11 ` [PATCH 1/5] soc: hisilicon: kunpeng_hccs: fix a PCC typo Huisong Li
2024-07-18  7:11 ` [PATCH 2/5] soc: hisilicon: kunpeng_hccs: return failure on having not die or port information Huisong Li
2024-07-18  7:11 ` [PATCH 3/5] soc: hisilicon: kunpeng_hccs: add used HCCS type sysfs on platform Huisong Li
     [not found]   ` <66AB7194.1060404@hisilicon.com>
2024-08-09  4:07     ` lihuisong (C)
2024-07-18  7:11 ` [PATCH 4/5] soc: hisilicon: kunpeng_hccs: support low power feature for specified HCCS Huisong Li
2024-07-28 11:55   ` Krzysztof Kozlowski
2024-08-09  4:06     ` lihuisong (C)
2024-07-18  7:11 ` [PATCH 5/5] doc: soc: hisilicon: kunpeng_hccs: add low power interface description for HCCS Huisong Li
2024-08-23  3:10 ` [PATCH v2 0/6] Add some features and bugfix for kunpeng_hccs Huisong Li
2024-08-23  3:10   ` [PATCH v2 1/6] soc: hisilicon: kunpeng_hccs: Fix a PCC typo Huisong Li
2024-08-23  8:32     ` Jonathan Cameron
2024-08-23  3:10   ` [PATCH v2 2/6] soc: hisilicon: kunpeng_hccs: Return failure on having not die or port information Huisong Li
2024-08-23  8:33     ` Jonathan Cameron
2024-08-27 11:04       ` lihuisong (C)
2024-08-23  3:10   ` [PATCH v2 3/6] soc: hisilicon: kunpeng_hccs: Add the check for base address and size of shared memory Huisong Li
2024-08-23  8:38     ` Jonathan Cameron
2024-08-27 11:12       ` lihuisong (C)
2024-08-23  3:10   ` [PATCH v2 4/6] soc: hisilicon: kunpeng_hccs: Fix the 'lane_mode' field name in port info structure to 'max_lane_num' Huisong Li
2024-08-23  8:40     ` Jonathan Cameron
2024-08-27 11:15       ` lihuisong (C)
2024-08-23  3:10   ` [PATCH v2 5/6] soc: hisilicon: kunpeng_hccs: Add used HCCS types sysfs Huisong Li
2024-08-23  8:47     ` Jonathan Cameron
2024-08-27 11:32       ` lihuisong (C)
2024-08-23  3:10   ` [PATCH v2 6/6] soc: hisilicon: kunpeng_hccs: Support low power feature for the specified HCCS type Huisong Li
2024-08-23  8:58     ` Jonathan Cameron
2024-08-27 11:48       ` lihuisong (C)
2024-08-27 11:59         ` Jonathan Cameron
2024-08-23  9:02   ` Jonathan Cameron [this message]
2024-08-27 11:49     ` [PATCH v2 0/6] Add some features and bugfix for kunpeng_hccs lihuisong (C)

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=20240823100211.00002b9d@Huawei.com \
    --to=jonathan.cameron@huawei.com \
    --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=wanghuiqiang@huawei.com \
    --cc=xuwei5@hisilicon.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;
as well as URLs for NNTP newsgroup(s).