From: Andy Shevchenko <andy@black.fi.intel.com>
To: Charles Keepax <ckeepax@opensource.cirrus.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: Tue, 9 Apr 2024 21:06:56 +0300 [thread overview]
Message-ID: <ZhWDwIZe8b0lqe8o@black.fi.intel.com> (raw)
In-Reply-To: <20240409132126.1117916-3-ckeepax@opensource.cirrus.com>
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.
> 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.
> + return;
> + }
--
With Best Regards,
Andy Shevchenko
next prev parent reply other threads:[~2024-04-09 18:06 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 [this message]
2024-04-10 8:42 ` Charles Keepax
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=ZhWDwIZe8b0lqe8o@black.fi.intel.com \
--to=andy@black.fi.intel.com \
--cc=brgl@bgdev.pl \
--cc=broonie@kernel.org \
--cc=ckeepax@opensource.cirrus.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.