public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Matti Vaittinen <mazziesaccount@gmail.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>, Lee Jones <lee@kernel.org>
Cc: Arnd Bergmann <arnd@arndb.de>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v4 1/2] mfd: rohm-bd71828: Use software nodes for gpio-keys
Date: Wed, 29 Apr 2026 09:08:09 +0300	[thread overview]
Message-ID: <607414e4-f134-4a7d-ad5a-ce48de507bc6@gmail.com> (raw)
In-Reply-To: <391d679c-0d93-456a-977e-2b26b8135db9@gmail.com>

On 29/04/2026 08:53, Matti Vaittinen wrote:
> Hi Dee Ho,
> 
> Thanks a ton Dmitry! This is looking very good to me now. I only have 
> one question below.
> 
> On 28/04/2026 07:13, Dmitry Torokhov wrote:
>> Refactor the rohm-bd71828 MFD driver to use software nodes for
>> instantiating the gpio-keys child device, replacing the old
>> platform_data mechanism.
>>
>> The power key's properties are now defined using software nodes and
>> property entries. The IRQ is passed as a resource attached to the
>> platform device.
>>
>> This will allow dropping support for using platform data for configuring
>> gpio-keys in the future.
>>
>> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
>> ---
>>   drivers/mfd/rohm-bd71828.c | 122 ++++++++++++++++++++++++++++++++ 
>> +------------
>>   1 file changed, 90 insertions(+), 32 deletions(-)
>>
>> diff --git a/drivers/mfd/rohm-bd71828.c b/drivers/mfd/rohm-bd71828.c
>> index a79f354bf5cb..a8bdb9c955a4 100644
>> --- a/drivers/mfd/rohm-bd71828.c
>> +++ b/drivers/mfd/rohm-bd71828.c
>> +    /* Node corresponding to gpio-keys device itself */
>> +    nodes[0].name = devm_kasprintf(dev, GFP_KERNEL, "%s-power-key", 
>> dev_name(dev));
>> +    if (!nodes[0].name)
>> +        return -ENOMEM;
> 
> Do we have any guidance/rules for naming the swnodes similar to 
> devicetree nodes? Do they need to be unique, and are they used for 
> anything?
> 
> I am wondering if the dev_name() is needed or if we should have some 
> 'numbering'? I am not sure if the node names can be used for anything, 
> but in some cases adding IC-type to names will hurt the "generic 
> usability". On the other hand, if names need to be unique, then some 
> numbering might be needed (although, this is not critical for this 
> driver as it is very unlikely there is a system with more than one of 
> these PMICs).

After thinking 2 seconds more... I suppose the dev_name() guarantees the 
name is unique :) So, please forget my babblings about numbering.


-- 
---
Matti Vaittinen
Linux kernel developer at ROHM Semiconductors
Oulu Finland

~~ When things go utterly wrong vim users can always type :help! ~~

  reply	other threads:[~2026-04-29  6:08 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-04-28  4:13 [PATCH v4 0/2] rohm-bdi718x7/71828: Use software nodes for gpio-keys Dmitry Torokhov
2026-04-28  4:13 ` [PATCH v4 1/2] mfd: rohm-bd71828: " Dmitry Torokhov
2026-04-29  5:53   ` Matti Vaittinen
2026-04-29  6:08     ` Matti Vaittinen [this message]
2026-04-28  4:13 ` [PATCH v4 2/2] mfd: rohm-bd718x7: " Dmitry Torokhov
2026-04-29  6:10   ` Matti Vaittinen

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=607414e4-f134-4a7d-ad5a-ce48de507bc6@gmail.com \
    --to=mazziesaccount@gmail.com \
    --cc=arnd@arndb.de \
    --cc=dmitry.torokhov@gmail.com \
    --cc=lee@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    /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