Devicetree
 help / color / mirror / Atom feed
From: sashiko-bot@kernel.org
To: "Roman Smrž" <roman@amarulasolutions.com>
Cc: devicetree@vger.kernel.org, robh@kernel.org, conor+dt@kernel.org
Subject: Re: [PATCH 3/5] ASoC: pcm179x: Add left-justified formats for pcm1792a
Date: Fri, 02 Oct 2026 09:57:48 +0000	[thread overview]
Message-ID: <20261002095748.796DC1F000FF@smtp.kernel.org> (raw)
In-Reply-To: <20261002-work-v1-3-f0e53bc7331f@amarulasolutions.com>

Thank you for your contribution! Sashiko AI review found 1 potential issue(s) to consider:
- [Medium] ASoC: pcm179x: missing LEFT_J in auto_selectable_formats
--

commit f6579131e2b6aaf5049aa6728620f5e3a4687837
Author: Roman Smrž <roman@amarulasolutions.com>

ASoC: pcm179x: Add left-justified formats for pcm1792a

This commit adds left-justified format support for 24 and 32 bits to
the pcm1792a format table to match the datasheet.

> diff --git a/sound/soc/codecs/pcm179x.c b/sound/soc/codecs/pcm179x.c
> index 61b87dab32667..c059e410cbbe4 100644
> --- a/sound/soc/codecs/pcm179x.c
> +++ b/sound/soc/codecs/pcm179x.c
> @@ -75,6 +75,8 @@ static const struct pcm179x_fmt_table pcm1792a_fmt[] = {
>  	{ SND_SOC_DAIFMT_RIGHT_J, 16, 0 },
>  	{ SND_SOC_DAIFMT_RIGHT_J, 24, 2 },
>  	{ SND_SOC_DAIFMT_RIGHT_J, 32, 2 },
> +	{ SND_SOC_DAIFMT_LEFT_J,  24, 3 },
> +	{ SND_SOC_DAIFMT_LEFT_J,  32, 3 },

[Severity: Medium]
Should the new left-justified format also be added to the auto-negotiation
bitmask in this file?

When the ASoC core attempts to find a matching DAI format between the CPU
and codec components, it intersects their supported auto-selectable formats.
Because SND_SOC_POSSIBLE_DAIFMT_LEFT_J is omitted from the bitmask, it
appears this format will be skipped and remain unavailable to generic
machine drivers unless manually configured in the device tree.

For context, the current bitmask only includes I2S and right-justified
formats:

sound/soc/codecs/pcm179x.c:pcm179x_selectable_formats
static const u64 pcm179x_selectable_formats =
	SND_SOC_POSSIBLE_DAIFMT_I2S	|
	SND_SOC_POSSIBLE_DAIFMT_RIGHT_J;

>  	{ SND_SOC_DAIFMT_I2S,     16, 4 },
>  	{ SND_SOC_DAIFMT_I2S,     24, 5 },
>  	{ SND_SOC_DAIFMT_I2S,     32, 5 },
> };

-- 
Sashiko AI review · https://sashiko.dev/#/patchset/20261002-work-v1-0-f0e53bc7331f@amarulasolutions.com?part=3

  reply	other threads:[~2026-10-02  9:57 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-02  9:49 [PATCH 0/5] ASoC: pcm179x: Add support for pcm1795 and pcm1796 Roman Smrž
2026-10-02  9:49 ` [PATCH 1/5] ASoC: dt-bindings: Add ti,pcm1795 and ti,pcm1796 Roman Smrž
2026-10-03 14:34   ` Krzysztof Kozlowski
2026-10-02  9:49 ` [PATCH 2/5] ASoC: pcm179x: Refactor regmap value lookup Roman Smrž
2026-10-02  9:49 ` [PATCH 3/5] ASoC: pcm179x: Add left-justified formats for pcm1792a Roman Smrž
2026-10-02  9:57   ` sashiko-bot [this message]
2026-10-02  9:49 ` [PATCH 4/5] ASoC: pcm179x: Add pcm1796 as compatible with pcm1792a Roman Smrž
2026-10-02  9:57   ` sashiko-bot
2026-10-03 14:35   ` Krzysztof Kozlowski
2026-10-02  9:49 ` [PATCH 5/5] ASoC: pcm179x: Add support for pcm1975 Roman Smrž

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=20261002095748.796DC1F000FF@smtp.kernel.org \
    --to=sashiko-bot@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=robh@kernel.org \
    --cc=roman@amarulasolutions.com \
    --cc=sashiko-reviews@lists.linux.dev \
    /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