All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rob Herring <robh@kernel.org>
To: Oder Chiou <oder_chiou@realtek.com>
Cc: cezary.rojewski@intel.com, broonie@kernel.org,
	lgirdwood@gmail.com, krzk+dt@kernel.org, conor+dt@kernel.org,
	linux-spi@vger.kernel.org, perex@perex.cz,
	linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
	alsa-devel@alsa-project.org, flove@realtek.com,
	shumingf@realtek.com, jack.yu@realtek.com,
	derek.fang@realtek.com
Subject: Re: [PATCH v10 1/3] spi: export of_find_spi_controller_by_node()
Date: Fri, 19 Dec 2025 14:28:03 -0600	[thread overview]
Message-ID: <20251219202803.GA3877108-robh@kernel.org> (raw)
In-Reply-To: <20251216071853.3929135-2-oder_chiou@realtek.com>

On Tue, Dec 16, 2025 at 03:18:51PM +0800, Oder Chiou wrote:
> Some devices are primarily described on another bus (e.g. I2C) but also
> have an additional SPI connection that serves as a transport for
> firmware loading. Export of_find_spi_controller_by_node() so drivers can
> obtain the SPI controller referenced by a DT phandle.
> 
> Signed-off-by: Oder Chiou <oder_chiou@realtek.com>
> ---
>  drivers/spi/spi.c       |  3 ++-
>  include/linux/spi/spi.h | 11 +++++++++++
>  2 files changed, 13 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/spi/spi.c b/drivers/spi/spi.c
> index e25df9990f82..ecb5281b04a2 100644
> --- a/drivers/spi/spi.c
> +++ b/drivers/spi/spi.c
> @@ -4771,7 +4771,7 @@ static struct spi_device *of_find_spi_device_by_node(struct device_node *node)
>  }
>  
>  /* The spi controllers are not using spi_bus, so we find it with another way */
> -static struct spi_controller *of_find_spi_controller_by_node(struct device_node *node)
> +struct spi_controller *of_find_spi_controller_by_node(struct device_node *node)
>  {
>  	struct device *dev;
>  
> @@ -4784,6 +4784,7 @@ static struct spi_controller *of_find_spi_controller_by_node(struct device_node
>  	/* Reference got in class_find_device */
>  	return container_of(dev, struct spi_controller, dev);
>  }
> +EXPORT_SYMBOL_GPL(of_find_spi_controller_by_node);
>  
>  static int of_spi_notify(struct notifier_block *nb, unsigned long action,
>  			 void *arg)
> diff --git a/include/linux/spi/spi.h b/include/linux/spi/spi.h
> index cb2c2df31089..1eb04a96cc1c 100644
> --- a/include/linux/spi/spi.h
> +++ b/include/linux/spi/spi.h
> @@ -882,6 +882,17 @@ extern int devm_spi_register_controller(struct device *dev,
>  					struct spi_controller *ctlr);
>  extern void spi_unregister_controller(struct spi_controller *ctlr);
>  
> +#if IS_ENABLED(CONFIG_OF_DYNAMIC)

This has nothing to do with CONFIG_OF_DYNAMIC. CONFIG_OF is what you 
want, and there's probably a section for that already.

> +extern struct spi_controller *of_find_spi_controller_by_node(
> +	struct device_node *node);
> +#else
> +static inline struct spi_controller *of_find_spi_controller_by_node(
> +	struct device_node *node)
> +{
> +	return NULL;
> +}
> +#endif
> +
>  #if IS_ENABLED(CONFIG_ACPI) && IS_ENABLED(CONFIG_SPI_MASTER)
>  extern struct spi_controller *acpi_spi_find_controller_by_adev(struct acpi_device *adev);
>  extern struct spi_device *acpi_spi_device_alloc(struct spi_controller *ctlr,
> -- 
> 2.52.0
> 

  parent reply	other threads:[~2025-12-19 20:29 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-16  7:18 [PATCH v10 0/3] ASoC: rt5575: Add the codec driver for the ALC5575 Oder Chiou
2025-12-16  7:18 ` [PATCH v10 1/3] spi: export of_find_spi_controller_by_node() Oder Chiou
2025-12-17 10:51   ` Cezary Rojewski
2025-12-19 20:28   ` Rob Herring [this message]
2025-12-16  7:18 ` [PATCH v10 2/3] ASoC: dt-bindings: realtek,rt5575: add support for ALC5575 Oder Chiou
2025-12-19 20:28   ` Rob Herring (Arm)
2025-12-16  7:18 ` [PATCH v10 3/3] ASoC: rt5575: Add the codec driver for the ALC5575 Oder Chiou
2025-12-17 10:45   ` Cezary Rojewski
2025-12-17 10:54     ` Mark Brown
2025-12-18  7:48     ` Oder Chiou

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=20251219202803.GA3877108-robh@kernel.org \
    --to=robh@kernel.org \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=cezary.rojewski@intel.com \
    --cc=conor+dt@kernel.org \
    --cc=derek.fang@realtek.com \
    --cc=devicetree@vger.kernel.org \
    --cc=flove@realtek.com \
    --cc=jack.yu@realtek.com \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-sound@vger.kernel.org \
    --cc=linux-spi@vger.kernel.org \
    --cc=oder_chiou@realtek.com \
    --cc=perex@perex.cz \
    --cc=shumingf@realtek.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.