From: John Garry <john.garry@huawei.com>
To: Sudeep Holla <sudeep.holla@arm.com>
Cc: <rjw@rjwysocki.net>, <lenb@kernel.org>, <jeremy.linton@arm.com>,
<arnd@arndb.de>, <olof@lixom.net>, <linux-kernel@vger.kernel.org>,
<linux-acpi@vger.kernel.org>, <guohanjun@huawei.com>,
<gregkh@linuxfoundation.org>,
Jonathan Cameron <Jonathan.Cameron@huawei.com>,
wanghuiqiang <wanghuiqiang@huawei.com>
Subject: Re: [PATCH RFC 1/2] ACPI/PPTT: Add acpi_pptt_get_package_info() API
Date: Wed, 29 Jan 2020 11:03:27 +0000 [thread overview]
Message-ID: <8c9f68ed-2cc8-ae33-2c6a-8c520511d7c4@huawei.com> (raw)
In-Reply-To: <20200128145430.GA47557@bogus>
On 28/01/2020 14:54, Sudeep Holla wrote:
>>>> https://lore.kernel.org/linux-arm-kernel/1579876505-113251-6-git-send-email-john.garry@huawei.com/
>>>>
>>> Ah, there's already quite a lot of dependency built for this feature:(
>> Not really. It's only an RFC ATM, and my requirement is a sysfs file to read
>> the SoC id(s) (under ACPI FW). So I would still expect to be able to support
>> this from the SMCCC extension method.
>>
Hi Sudeep,
> As mentioned above, yes the driver would remain almost same for SMCCC
> SOC_ID support too. The main point was: do we need to add support to
> PPTT Type 2 entry when we know there is proposal to deprecate it. I
> would at-least wait to see progress on that until I would add this to
> the kernel.
Not having support in the kernel for a feature which may be officially
deprecated, i.e public knowledge, in future (maybe 1 year) seems harsh.
Especially when there is no final released alternative.
So do you know if other OSes use it?
Thanks
John
next prev parent reply other threads:[~2020-01-29 11:03 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 11:14 [PATCH RFC 0/2] Add basic generic ACPI soc driver John Garry
2020-01-28 11:14 ` [PATCH RFC 1/2] ACPI/PPTT: Add acpi_pptt_get_package_info() API John Garry
2020-01-28 12:34 ` Sudeep Holla
2020-01-28 14:04 ` John Garry
2020-01-28 14:54 ` Sudeep Holla
2020-01-29 11:03 ` John Garry [this message]
2020-01-30 11:23 ` Sudeep Holla
2020-01-30 16:12 ` John Garry
2020-01-30 17:41 ` Sudeep Holla
2020-01-31 10:58 ` John Garry
2020-01-28 11:14 ` [PATCH RFC 2/2] soc: Add a basic ACPI generic driver John Garry
2020-01-28 11:56 ` Greg KH
2020-01-28 13:33 ` John Garry
2020-01-28 12:50 ` Arnd Bergmann
2020-01-28 14:46 ` John Garry
2020-01-28 15:20 ` Sudeep Holla
2020-01-28 15:59 ` John Garry
2020-01-28 16:17 ` Sudeep Holla
2020-01-28 17:51 ` Olof Johansson
2020-01-28 18:22 ` John Garry
2020-01-28 19:11 ` Rafael J. Wysocki
2020-01-28 19:28 ` John Garry
2020-01-28 22:30 ` Rafael J. Wysocki
2020-01-29 10:27 ` John Garry
2020-01-28 20:06 ` Olof Johansson
2020-01-29 9:58 ` John Garry
2020-01-28 16:56 ` [PATCH RFC 0/2] Add basic generic ACPI soc driver Jeremy Linton
2020-01-28 17:28 ` John Garry
2020-01-28 19:04 ` Jeremy Linton
2020-01-28 20:07 ` John Garry
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=8c9f68ed-2cc8-ae33-2c6a-8c520511d7c4@huawei.com \
--to=john.garry@huawei.com \
--cc=Jonathan.Cameron@huawei.com \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=guohanjun@huawei.com \
--cc=jeremy.linton@arm.com \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=olof@lixom.net \
--cc=rjw@rjwysocki.net \
--cc=sudeep.holla@arm.com \
--cc=wanghuiqiang@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;
as well as URLs for NNTP newsgroup(s).