mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Aaron Kling <webgeek1234@gmail.com>
Cc: Liam Girdwood <lgirdwood@gmail.com>,
	Mark Brown <broonie@kernel.org>,  Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	 Conor Dooley <conor+dt@kernel.org>,
	Weidong Wang <wangweidong.a@awinic.com>,
	 Jaroslav Kysela <perex@perex.cz>, Takashi Iwai <tiwai@suse.com>,
	linux-sound@vger.kernel.org,  devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, Teguh Sobirin <teguh@sobir.in>
Subject: Re: [PATCH 2/2] ASoC: codecs: aw88166: Support device specific firmware
Date: Wed, 11 Mar 2026 14:15:37 +0100	[thread overview]
Message-ID: <20260311-glittering-elastic-deer-a2fa58@quoll> (raw)
In-Reply-To: <20260310-aw88166-fw-v1-2-2777563bb673@gmail.com>

On Tue, Mar 10, 2026 at 11:43:05PM -0500, Aaron Kling wrote:
> From: Teguh Sobirin <teguh@sobir.in>
> 
> This driver currently loads firmware from a hardcoded path. Support
> loading device specific firmware when provided by the boot firmware.
> 
> Signed-off-by: Teguh Sobirin <teguh@sobir.in>
> Co-authored-by: Aaron Kling <webgeek1234@gmail.com>

There is no such tag.

Also, incomplete DCO chain.

> ---
>  sound/soc/codecs/aw88166.c | 19 +++++++++++++++----
>  1 file changed, 15 insertions(+), 4 deletions(-)
> 
> diff --git a/sound/soc/codecs/aw88166.c b/sound/soc/codecs/aw88166.c
> index daee4de9e3b01fb335975a65456cc79575533d7e..52d33a2f7cb12877138ea5083ad42e2777f8d323 100644
> --- a/sound/soc/codecs/aw88166.c
> +++ b/sound/soc/codecs/aw88166.c
> @@ -1574,18 +1574,22 @@ static int aw88166_dev_init(struct aw88166 *aw88166, struct aw_container *aw_cfg
>  static int aw88166_request_firmware_file(struct aw88166 *aw88166)
>  {
>  	const struct firmware *cont = NULL;
> +	const char *fw_name;
>  	int ret;
>  
>  	aw88166->aw_pa->fw_status = AW88166_DEV_FW_FAILED;
>  
> -	ret = request_firmware(&cont, AW88166_ACF_FILE, aw88166->aw_pa->dev);
> +	if (device_property_read_string(aw88166->aw_pa->dev, "firmware-name", &fw_name) < 0)
> +		fw_name = AW88166_ACF_FILE;
> +
> +	ret = request_firmware(&cont, fw_name, aw88166->aw_pa->dev);
>  	if (ret) {
> -		dev_err(aw88166->aw_pa->dev, "request [%s] failed!\n", AW88166_ACF_FILE);
> +		dev_err(aw88166->aw_pa->dev, "request [%s] failed!\n", fw_name);
>  		return ret;
>  	}
>  
>  	dev_dbg(aw88166->aw_pa->dev, "loaded %s - size: %zu\n",
> -			AW88166_ACF_FILE, cont ? cont->size : 0);
> +			fw_name, cont ? cont->size : 0);
>  
>  	aw88166->aw_cfg = devm_kzalloc(aw88166->aw_pa->dev,
>  			struct_size(aw88166->aw_cfg, data, cont->size), GFP_KERNEL);
> @@ -1599,7 +1603,7 @@ static int aw88166_request_firmware_file(struct aw88166 *aw88166)
>  
>  	ret = aw88395_dev_load_acf_check(aw88166->aw_pa, aw88166->aw_cfg);
>  	if (ret) {
> -		dev_err(aw88166->aw_pa->dev, "load [%s] failed!\n", AW88166_ACF_FILE);
> +		dev_err(aw88166->aw_pa->dev, "load [%s] failed!\n", fw_name);
>  		return ret;
>  	}
>  
> @@ -1802,9 +1806,16 @@ static const struct i2c_device_id aw88166_i2c_id[] = {
>  };
>  MODULE_DEVICE_TABLE(i2c, aw88166_i2c_id);
>  
> +static const struct of_device_id aw88166_of_match[] = {
> +	{ .compatible = "awinic,aw88166" },
> +	{ /* sentinel */ }
> +};
> +MODULE_DEVICE_TABLE(of, aw88166_of_match);

This looks like an unrelated change.

Best regards,
Krzysztof


  reply	other threads:[~2026-03-11 13:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-11  4:43 [PATCH 0/2] " Aaron Kling via B4 Relay
2026-03-11  4:43 ` [PATCH 1/2] ASoC: dt-bindings: Document firmware-name for awinic,aw88166 Aaron Kling via B4 Relay
2026-03-11 13:16   ` Krzysztof Kozlowski
2026-03-11 16:32     ` Aaron Kling
2026-03-11  4:43 ` [PATCH 2/2] ASoC: codecs: aw88166: Support device specific firmware Aaron Kling via B4 Relay
2026-03-11 13:15   ` Krzysztof Kozlowski [this message]
2026-03-11 16:30     ` Aaron Kling
2026-03-11 16:33       ` Mark Brown
2026-03-11 16:41         ` Aaron Kling
2026-03-11 16:38       ` Krzysztof Kozlowski

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=20260311-glittering-elastic-deer-a2fa58@quoll \
    --to=krzk@kernel.org \
    --cc=broonie@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=lgirdwood@gmail.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=robh@kernel.org \
    --cc=teguh@sobir.in \
    --cc=tiwai@suse.com \
    --cc=wangweidong.a@awinic.com \
    --cc=webgeek1234@gmail.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

all inboxes | Powered by JetHome®