All of lore.kernel.org
 help / color / mirror / Atom feed
From: Jiaxun Yang <jiaxun.yang@flygoat.com>
To: Mark Pearson <markpearson@lenovo.com>,
	Hans de Goede <hdegoede@redhat.com>,
	"Rafael J. Wysocki" <rafael@kernel.org>
Cc: Platform Driver <platform-driver-x86@vger.kernel.org>,
	"Rafael J. Wysocki" <rjw@rjwysocki.net>,
	Len Brown <lenb@kernel.org>, Mark Gross <mgross@linux.intel.com>,
	Ike Panhc <ike.pan@canonical.com>,
	ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [External] Re: [PATCH 0/2] IdeaPad platform profile support
Date: Tue, 5 Jan 2021 14:24:48 +0800	[thread overview]
Message-ID: <75952842-3ee3-82a2-7809-66e2d5263c73@flygoat.com> (raw)
In-Reply-To: <2eefa5ec-4f09-eabd-2c20-f217fa084dfc@lenovo.com>

在 2021/1/5 上午5:58, Mark Pearson 写道:
> On 04/01/2021 15:58, Hans de Goede wrote:
>> Hi,
>>
>> On 1/4/21 9:33 PM, Rafael J. Wysocki wrote:
>>> On Mon, Jan 4, 2021 at 3:36 PM Hans de Goede <hdegoede@redhat.com>
>>>   wrote:
>>>> Hi,
>>>>
>>>> On 1/1/21 1:56 PM, Jiaxun Yang wrote:
>>>>> Tested on Lenovo Yoga-14SARE Chinese Edition.
>>>>>
[...]
> Just for my understanding of what happens next....please correct me if I
> have anything wrong:
>
>   - platform_profile gets pulled from ACPI for 5.11
>
>   - platform_profile gets updated to add this data/pointer implementation
> and goes into 5.12.
Hi all,

Another approach could be just let all the patch go through pdx86 tree 
and with
pointer part acked by Rafael as it's unlikely to have merge conflicts.

> Jiaxun, let me know if you're happy with following
> up on that based on Hans suggestions, If you are pushed for time let me
> know and I'll happily help out/implement/test as required. I sadly don't
> have any ideapads but very happy to support your efforts any way I can.


I'm happy with Hans suggestion, will send v2 for it later.

I've been ask Lenovo engineers about DYTC and other ideapad ACPI
stuff on Lenovo China forum[1], but moderator here told me Lenovo won't
invest any Linux effort on their consumer product line :-(

Is it possible to publish a DYTC specification or documents to help us 
further
understand these mechanisms?

I'm tired of reading disassembly AML and code to figure out these internals.

>
>   - Can we get the x86 portion done at the same time or does that end up
> going to 5.13? I had been looking at the ideapad_laptop.c patch and have
> some concerns there as Jiaxun's patch is essentially a duplicate of what
> I implemented in thinkpad_acpi.c which doesn't seem to be ideal
> (especially as there is a V6 version of DYTC coming out this year). I
> haven't had time to look at code to consider better alternatives though...

It may be worthy to share these code but I'm comfort to have this 
duplication as I'm
unsure about the future of DYTC. Will DYTC for thinkpads always coherent 
with DYTC
for ideapads?

Thanks.

[1]: https://club.lenovo.com.cn/thread-5980431-1-1.html

- Jiaxun

>
> Mark


  reply	other threads:[~2021-01-05  6:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-01-01 12:56 [PATCH 0/2] IdeaPad platform profile support Jiaxun Yang
2021-01-01 12:56 ` [PATCH 1/2] ACPI: platform-profile: Introduce data parameter to handler Jiaxun Yang
2021-01-04 14:34   ` Hans de Goede
2021-01-01 12:56 ` [PATCH 2/2] platform/x86: ideapad-laptop: DYTC Platform profile support Jiaxun Yang
2021-01-04 14:34 ` [PATCH 0/2] IdeaPad platform " Hans de Goede
2021-01-04 20:33   ` Rafael J. Wysocki
2021-01-04 20:58     ` Hans de Goede
2021-01-04 21:58       ` [External] " Mark Pearson
2021-01-05  6:24         ` Jiaxun Yang [this message]
2021-01-05 16:53           ` Mark Pearson
2021-01-05 10:28         ` Hans de Goede
2021-01-05 17:18       ` Rafael J. Wysocki
2021-01-06  9:17         ` Hans de Goede
2021-01-07 13:50           ` Rafael J. Wysocki

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=75952842-3ee3-82a2-7809-66e2d5263c73@flygoat.com \
    --to=jiaxun.yang@flygoat.com \
    --cc=hdegoede@redhat.com \
    --cc=ike.pan@canonical.com \
    --cc=lenb@kernel.org \
    --cc=linux-acpi@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=markpearson@lenovo.com \
    --cc=mgross@linux.intel.com \
    --cc=platform-driver-x86@vger.kernel.org \
    --cc=rafael@kernel.org \
    --cc=rjw@rjwysocki.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.