From: John Garry <john.garry@huawei.com>
To: Andy Shevchenko <andy.shevchenko@gmail.com>
Cc: "Rafael J. Wysocki" <rafael@kernel.org>,
"Rafael J. Wysocki" <rjw@rjwysocki.net>,
Linux ACPI <linux-acpi@vger.kernel.org>,
LKML <linux-kernel@vger.kernel.org>,
Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Yang Yingliang <yangyingliang@huawei.com>
Subject: Re: [PATCH v3] hisi_lpc: Use acpi_dev_for_each_child()
Date: Tue, 5 Jul 2022 11:16:08 +0100 [thread overview]
Message-ID: <050e5a2f-42b9-f851-ec6e-e2a9d3fdbe1c@huawei.com> (raw)
In-Reply-To: <CAHp75VfpQfBYD-AmVhbxm4tp_1EVv8xqCChYpuuRKOC=P_Y_og@mail.gmail.com>
On 05/07/2022 10:39, Andy Shevchenko wrote:
> On Tue, Jul 5, 2022 at 11:38 AM Andy Shevchenko
> <andy.shevchenko@gmail.com> wrote:
>> On Tue, Jul 5, 2022 at 10:37 AM John Garry<john.garry@huawei.com> wrote:
>>> On 04/07/2022 20:02, Rafael J. Wysocki wrote:
>> ...
>>
>>> I gave these a quick test on my board and they look fine.
>>>
>>> Acked-by: John Garry<john.garry@huawei.com>
>> John, I believe now you may send a formal clean up to convert to platform_device
> Hit Enter too early:-)
>
> ...to platform_device_register_full().
Sure, I can look at that now. But I just found where we previously
mentioned the possibility of factoring out some of the ACPI platform
device creation code:
https://lore.kernel.org/linux-acpi/CAHp75VfOa5pN4MKT-aQmWBwPGWsOaQupyfrN-weWwfR3vMLtuA@mail.gmail.com/
There is actually still a comment in the hisi_lpc driver - I should have
checked there first :)
So my impression is that the hisi_lpc code is almost the same in
acpi_create_platform_device(), apart from we need do the resource fixup
in hisi_lpc_acpi_set_io_res().
So we could factor out by dividing acpi_create_platform_device() into 2x
parts: resource get and then platform dev create. But that does not seem
wise as we have 2x parts which don't make sense on their own. Or else
pass a fixup callback into acpi_create_platform_device(). Any other
ideas if we want to go this way?
Thanks,
John
next prev parent reply other threads:[~2022-07-05 10:16 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-29 12:55 [PATCH] hisi_lpc: Use acpi_dev_for_each_child() Rafael J. Wysocki
2022-06-29 13:33 ` John Garry
2022-06-29 13:38 ` Rafael J. Wysocki
2022-06-29 13:47 ` [PATCH v2] " Rafael J. Wysocki
2022-06-30 12:48 ` Rafael J. Wysocki
2022-06-30 13:37 ` John Garry
2022-06-30 13:40 ` Rafael J. Wysocki
2022-06-30 18:13 ` [PATCH v3] " Rafael J. Wysocki
2022-07-01 8:34 ` Greg Kroah-Hartman
2022-07-01 10:49 ` John Garry
2022-07-01 11:06 ` Andy Shevchenko
2022-07-01 11:07 ` Andy Shevchenko
2022-07-01 11:54 ` John Garry
2022-07-01 12:05 ` Andy Shevchenko
2022-07-01 12:18 ` John Garry
2022-07-04 19:02 ` Rafael J. Wysocki
2022-07-05 8:37 ` John Garry
2022-07-05 9:38 ` Andy Shevchenko
2022-07-05 9:39 ` Andy Shevchenko
2022-07-05 10:16 ` John Garry [this message]
2022-07-05 10:29 ` Andy Shevchenko
2022-07-05 13:54 ` Rafael J. Wysocki
2022-07-05 15:16 ` John Garry
2022-07-05 15:34 ` Rafael J. Wysocki
2022-08-09 10:35 ` John Garry
2022-07-05 15:08 ` Rafael J. Wysocki
2022-07-01 18:16 ` Rafael J. Wysocki
2022-07-01 18:19 ` 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=050e5a2f-42b9-f851-ec6e-e2a9d3fdbe1c@huawei.com \
--to=john.garry@huawei.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=andy.shevchenko@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=rafael@kernel.org \
--cc=rjw@rjwysocki.net \
--cc=yangyingliang@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