[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <3c372ca4-373d-9c03-8636-a9f065eed577@electromag.com.au>
Date: Fri, 26 Jul 2019 10:40:28 +0800
From: Richard Tresidder <rtresidd@...ctromag.com.au>
To: David Lechner <david@...hnology.com>, sre@...nel.org,
enric.balletbo@...labora.com, ncrews@...omium.org,
andrew.smirnov@...il.com, groeck@...omium.org, tglx@...utronix.de,
linux-pm@...r.kernel.org, linux-kernel@...r.kernel.org
Subject: Re: [PATCH 1/1] power/supply/powersupply_sysfs: Add of_node name to
uevent message if available
Hi David
That it would be. I wasn't aware of that call.
I'll give it a crack and send in a new version of the patch.
Cheers
Richard Tresidder
Richard Tresidder
On 25/07/2019 10:08 pm, David Lechner wrote:
> On 7/25/19 2:47 AM, Richard Tresidder wrote:
>> If the of_node name of the supply is available from the devicetree
>> binding
>> then include it under the var POWER_SUPPLY_OF_NODE_NAME.
>> This helps where a consistent name is known via the device tree binding
>> but it is hard to identify based on the usual enumeration process.
>>
>
> Would it be possible to use of_device_uevent() instead of introducing
> a new
> property?
>
>
>
Powered by blists - more mailing lists