linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Andy Shevchenko <andy@black.fi.intel.com>
Cc: <broonie@kernel.org>, <linus.walleij@linaro.org>, <brgl@bgdev.pl>,
	<linux-gpio@vger.kernel.org>, <linux-spi@vger.kernel.org>,
	<patches@opensource.cirrus.com>
Subject: Re: [PATCH v4 2/3] spi: Add a mechanism to use the fwnode name for the SPI device
Date: Wed, 10 Apr 2024 08:42:44 +0000	[thread overview]
Message-ID: <ZhZRBEAsfSUw1i2g@ediswmail9.ad.cirrus.com> (raw)
In-Reply-To: <ZhWDwIZe8b0lqe8o@black.fi.intel.com>

On Tue, Apr 09, 2024 at 09:06:56PM +0300, Andy Shevchenko wrote:
> On Tue, Apr 09, 2024 at 02:21:25PM +0100, Charles Keepax wrote:
> > Add a mechanism to force the use of the fwnode name for the name of the
> > SPI device itself. This is useful when devices need to be manually added
> > within the kernel.
> 
> Same comment, we don't need two ways to handle fwnode type
> (and effectivelly code duplication to some extent).
> 
> ...
> 
> >  	struct acpi_device *adev = ACPI_COMPANION(&spi->dev);
> 
> >  	if (adev) {
> 
> Replace this to be is_acpi_device_node() check...
> 
> >  		dev_set_name(&spi->dev, "spi-%s", acpi_dev_name(adev));
> 
> ...and derive adev from fwnode.
> 

I had been hoping to not modify the path I wasn't using but fair
enough if you are sure this is a fine substitution.

> >  		return;
> >  	}
> 
> > +	if (is_software_node(fwnode)) {
> > +		dev_set_name(&spi->dev, "spi-%s", fwnode_get_name(fwnode));
> 
> While at this, you can also introduce
> 
> 	struct device *dev = &spi->dev;
> 
> to make these dev_set_name() be shorter.
> 

Sure.

Thanks,
Charles

  reply	other threads:[~2024-04-10  8:43 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-04-09 13:21 [PATCH 0/3] Add bridged amplifiers to cs42l43 Charles Keepax
2024-04-09 13:21 ` [PATCH v4 1/3] gpio: swnode: Add ability to specify native chip selects for SPI Charles Keepax
2024-04-09 13:50   ` Linus Walleij
2024-04-09 18:03   ` Andy Shevchenko
2024-04-10  8:44     ` Charles Keepax
2024-04-09 13:21 ` [PATCH v4 2/3] spi: Add a mechanism to use the fwnode name for the SPI device Charles Keepax
2024-04-09 14:46   ` Charles Keepax
2024-04-09 18:06   ` Andy Shevchenko
2024-04-10  8:42     ` Charles Keepax [this message]
2024-04-09 13:21 ` [PATCH v4 3/3] spi: cs42l43: Add bridged cs35l56 amplifiers Charles Keepax
2024-04-09 18:26   ` Andy Shevchenko
2024-04-10  9:11     ` Charles Keepax
2024-04-10  7:42   ` kernel test robot
2024-04-10  8:01     ` Andy Shevchenko

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=ZhZRBEAsfSUw1i2g@ediswmail9.ad.cirrus.com \
    --to=ckeepax@opensource.cirrus.com \
    --cc=andy@black.fi.intel.com \
    --cc=brgl@bgdev.pl \
    --cc=broonie@kernel.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=patches@opensource.cirrus.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).