From: "lihuisong (C)" <lihuisong@huawei.com>
To: Sudeep Holla <sudeep.holla@arm.com>,
<linux-hwmon@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-i2c@vger.kernel.org>, <linux-acpi@vger.kernel.org>
Cc: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
Andi Shyti <andi.shyti@kernel.org>,
Jean Delvare <jdelvare@suse.com>,
Guenter Roeck <linux@roeck-us.net>
Subject: Re: [PATCH v2 4/4] soc: kunpeng_hccs: Migrate to use generic PCC shmem related macros
Date: Thu, 28 Sep 2023 19:30:44 +0800 [thread overview]
Message-ID: <8689e2aa-5fbd-cf9d-d168-a72669aea5ed@huawei.com> (raw)
In-Reply-To: <20230927-pcc_defines-v2-4-0b8ffeaef2e5@arm.com>
lgtm,
Reviewed-by: Huisong Li <lihuisong@huawei.com>
在 2023/9/28 0:26, Sudeep Holla 写道:
> Use the newly defined common and generic PCC shared memory region
> related macros in this driver to replace the locally defined ones.
>
> Cc: Huisong Li <lihuisong@huawei.com>
> Signed-off-by: Sudeep Holla <sudeep.holla@arm.com>
> ---
> drivers/soc/hisilicon/kunpeng_hccs.c | 8 ++------
> 1 file changed, 2 insertions(+), 6 deletions(-)
>
> diff --git a/drivers/soc/hisilicon/kunpeng_hccs.c b/drivers/soc/hisilicon/kunpeng_hccs.c
> index f3810d9d1caa..27a96cafd1ea 100644
> --- a/drivers/soc/hisilicon/kunpeng_hccs.c
> +++ b/drivers/soc/hisilicon/kunpeng_hccs.c
> @@ -31,10 +31,6 @@
>
> #include "kunpeng_hccs.h"
>
> -/* PCC defines */
> -#define HCCS_PCC_SIGNATURE_MASK 0x50434300
> -#define HCCS_PCC_STATUS_CMD_COMPLETE BIT(0)
> -
> /*
> * Arbitrary retries in case the remote processor is slow to respond
> * to PCC commands
> @@ -187,7 +183,7 @@ static int hccs_check_chan_cmd_complete(struct hccs_dev *hdev)
> * deadline_us(timeout_us) until PCC command complete bit is set(cond)
> */
> ret = readw_poll_timeout(&comm_base->status, status,
> - status & HCCS_PCC_STATUS_CMD_COMPLETE,
> + status & PCC_STATUS_CMD_COMPLETE,
> HCCS_POLL_STATUS_TIME_INTERVAL_US,
> cl_info->deadline_us);
> if (unlikely(ret))
> @@ -208,7 +204,7 @@ static int hccs_pcc_cmd_send(struct hccs_dev *hdev, u8 cmd,
> int ret;
>
> /* Write signature for this subspace */
> - tmp.signature = HCCS_PCC_SIGNATURE_MASK | hdev->chan_id;
> + tmp.signature = PCC_SIGNATURE | hdev->chan_id;
> /* Write to the shared command region */
> tmp.command = cmd;
> /* Clear cmd complete bit */
>
next prev parent reply other threads:[~2023-09-28 11:30 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-27 16:26 [PATCH v2 0/4] ACPI: PCC: Define and use the common PCC shared memory regions related macros Sudeep Holla
2023-09-27 16:26 ` [PATCH v2 1/4] ACPI: PCC: Add PCC shared memory region command and status bitfields Sudeep Holla
2023-10-03 13:29 ` Rafael J. Wysocki
2023-10-03 14:29 ` Sudeep Holla
2023-10-03 15:05 ` Rafael J. Wysocki
2023-09-27 16:26 ` [PATCH v2 2/4] i2c: xgene-slimpro: Migrate to use generic PCC shmem related macros Sudeep Holla
2023-09-29 7:33 ` Wolfram Sang
2023-09-27 16:26 ` [PATCH v2 3/4] hwmon: (xgene) " Sudeep Holla
2023-09-27 16:26 ` [PATCH v2 4/4] soc: kunpeng_hccs: " Sudeep Holla
2023-09-28 11:30 ` lihuisong (C) [this message]
2023-09-29 11:45 ` [PATCH v2 0/4] ACPI: PCC: Define and use the common PCC shared memory regions " Sudeep Holla
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=8689e2aa-5fbd-cf9d-d168-a72669aea5ed@huawei.com \
--to=lihuisong@huawei.com \
--cc=andi.shyti@kernel.org \
--cc=jdelvare@suse.com \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=rafael.j.wysocki@intel.com \
--cc=sudeep.holla@arm.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