Linux SOC development
 help / color / mirror / Atom feed
From: Huisong Li <lihuisong@huawei.com>
To: <rafael@kernel.org>, <rafael.j.wysocki@intel.com>,
	<sudeep.holla@arm.com>, <xuwei5@hisilicon.com>
Cc: <linux-acpi@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
	<soc@kernel.org>, <linux-arm-kernel@lists.infradead.org>,
	<liuyonglong@huawei.com>, <lihuisong@huawei.com>
Subject: [PATCH v2 0/2] mailbox: pcc: export the PCC subspace type
Date: Wed, 20 Sep 2023 14:47:01 +0800	[thread overview]
Message-ID: <20230920064703.23543-1-lihuisong@huawei.com> (raw)
In-Reply-To: <20230914115753.9064-1-lihuisong@huawei.com>

Currently, it seems that the subspace type in all drivers used PCC is fixed
and not obtained from their platform.
And PCCT is a best natural way to export it.

v1->v2:
 - add one patch to use PCC subspace type in kunpeng_hccs

Huisong Li (2):
  mailbox: pcc: export the PCC subspace type
  soc: kunpeng_hccs: add the check for PCC subspace type

 drivers/mailbox/pcc.c                | 10 ++++------
 drivers/soc/hisilicon/kunpeng_hccs.c | 17 +++++++++++++++++
 include/acpi/pcc.h                   |  1 +
 3 files changed, 22 insertions(+), 6 deletions(-)

-- 
2.33.0


       reply	other threads:[~2023-09-20  6:50 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20230914115753.9064-1-lihuisong@huawei.com>
2023-09-20  6:47 ` Huisong Li [this message]
2023-09-20  6:47   ` [PATCH v2 1/2] mailbox: pcc: export the PCC subspace type Huisong Li
2023-09-20  6:47   ` [PATCH v2 2/2] soc: kunpeng_hccs: add the check for " Huisong Li
2023-09-20 14:11     ` Sudeep Holla
2023-09-21  2:27       ` lihuisong (C)
2023-09-28 11:40         ` lihuisong (C)
2023-09-29 11:27         ` Sudeep Holla
2023-10-07  2:45           ` 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=20230920064703.23543-1-lihuisong@huawei.com \
    --to=lihuisong@huawei.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=liuyonglong@huawei.com \
    --cc=rafael.j.wysocki@intel.com \
    --cc=rafael@kernel.org \
    --cc=soc@kernel.org \
    --cc=sudeep.holla@arm.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