[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <155062a9-8d1a-e771-1bee-35580b1b2b73@gmx.de>
Date: Mon, 12 Sep 2022 19:29:45 +0200
From: Armin Wolf <W_Armin@....de>
To: Barnabás Pőcze <pobrn@...tonmail.com>
Cc: hdegoede@...hat.com, markgross@...nel.org, rafael@...nel.org,
lenb@...nel.org, hmh@....eng.br, matan@...alib.org,
corentin.chary@...il.com, jeremy@...tem76.com,
productdev@...tem76.com, platform-driver-x86@...r.kernel.org,
linux-acpi@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 3/5] ACPI: battery: Allow battery hooks to be registered
multiple times.
Am 12.09.22 um 18:42 schrieb Barnabás Pőcze:
> Hi
>
> 2022. szeptember 12., hétfő 14:53 keltezéssel, Armin Wolf írta:
>
>> Registering multiple instances of a battery hook is beneficial
>> for drivers which can be instantiated multiple times. Until now,
>> this would mean that such a driver would have to implement some
>> logic to manage battery hooks.
>>
>> Extend the battery hook handling instead.
> I think this is already possible by embedding the acpi_battery_hook
> object inside the driver's device specific data object, no?
>
> Regards,
> Barnabás Pőcze
>
>
Yes, it indeed is. However afaik it is not possible to pass instance-specific
data to such an embedded battery hook. It could be possible by passing the
battery hook as an argument to add_battery()/remove_battery() and using container_of(),
but in my opinion this would be too much of a quick hack.
>> [...]
Powered by blists - more mailing lists