mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "zhangzekun (A)" <zhangzekun11@huawei.com>
To: "Rafael J. Wysocki" <rafael@kernel.org>
Cc: <lenb@kernel.org>, <patchwork@huawei.com>,
	<wangkefeng.wang@huawei.com>, <linux-acpi@vger.kernel.org>,
	<linux-kernel@vger.kernel.org>, <guohanjun@huawei.com>,
	<wanghuiqiang@huawei.com>, <lihuisong@huawei.com>,
	<wangxiongfeng2@huawei.com>
Subject: Re: [PATCH RFC] ACPI: container: Add power domain control methods
Date: Thu, 10 Nov 2022 22:28:23 +0800	[thread overview]
Message-ID: <21498cd9-e84f-2592-8f7b-16c86c4f05fd@huawei.com> (raw)
In-Reply-To: <CAJZ5v0h1zNSo4E-hk+vBemfV7_gsOe+3Gz-vAcn9AiufTCwX3Q@mail.gmail.com>

Hi, Rafael J

Thanks a lot for your advice! I will look into LPI and find a better way
to do what I want.

Best Regards,
Zekun, Zhang

在 2022/11/10 21:05, Rafael J. Wysocki 写道:
> On Thu, Nov 10, 2022 at 1:13 PM zhangzekun (A) <zhangzekun11@huawei.com> wrote:
>> Kindly ping.
> I'm not going to apply this patch if that's what you're asking about.
>
> Please have a look at LPI which is the ACPI way of doing what you want.
>
> If you need to extend the support for it in the kernel, please do so.
>
> If you need to extend the definition of LPI in the ACPI specification,
> there is also a way to do that.
>
> What you are trying to do would require extending the container device
> definition in the specification anyway.
>
>> 在 2022/10/29 1:07, Rafael J. Wysocki 写道:
>>> On Tue, Oct 25, 2022 at 8:17 AM Zhang Zekun <zhangzekun11@huawei.com> wrote:
>>>> Platform devices which supports power control are often required to be
>>>> power off/on together with the devices in the same power domain. However,
>>>> there isn't a generic driver that support the power control logic of
>>>> these devices.
>>> Not true.
>>>
>>> There is the ACPI power resources interface designed to represent
>>> power domains that is well supported and used in the industry.
>>>
>>> If it doesn't work for you, explain why.
>>>


      reply	other threads:[~2022-11-10 14:28 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-25  6:14 Zhang Zekun
2022-10-28 17:07 ` Rafael J. Wysocki
2022-10-31  7:49   ` zhangzekun (A)
2022-11-10 12:13   ` zhangzekun (A)
2022-11-10 13:05     ` Rafael J. Wysocki
2022-11-10 14:28       ` zhangzekun (A) [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=21498cd9-e84f-2592-8f7b-16c86c4f05fd@huawei.com \
    --to=zhangzekun11@huawei.com \
    --cc=guohanjun@huawei.com \
    --cc=lenb@kernel.org \
    --cc=lihuisong@huawei.com \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=patchwork@huawei.com \
    --cc=rafael@kernel.org \
    --cc=wanghuiqiang@huawei.com \
    --cc=wangkefeng.wang@huawei.com \
    --cc=wangxiongfeng2@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

all inboxes | Powered by JetHome®