linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Alexandre Belloni <alexandre.belloni@bootlin.com>
To: Andrei Simion <andrei.simion@microchip.com>
Cc: alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
	claudiu.beznea@tuxon.dev, linux-sound@vger.kernel.org,
	lgirdwood@gmail.com, broonie@kernel.org, tiwai@suse.com,
	codrin.ciubotariu@microchip.com, perex@perex.cz,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 2/2] ASoC: atmel: atmel_ssc_dai: Drop S24_LE support due to single channel limitation
Date: Mon, 16 Sep 2024 14:30:45 +0200	[thread overview]
Message-ID: <2024091612304529f5ebe1@mail.local> (raw)
In-Reply-To: <20240916113203.17871-1-andrei.simion@microchip.com>

On 16/09/2024 14:32:05+0300, Andrei Simion wrote:
> On 16.09.2024 12:59, Alexandre Belloni wrote:
> > EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> > 
> > On 16/09/2024 11:52:15+0300, Andrei Simion wrote:
> >> From: Codrin Ciubotariu <codrin.ciubotariu@microchip.com>
> >>
> >> Drop S24_LE format because it is not supported if more than 2 channels
> >> (of TDM slots) are used. This limitation makes it impractical for use cases
> >> requiring more than 2 TDM slots, leading to potential issues in
> >> multi-channel configurations.
> >>
> >> [andrei.simion@microchip.com: Reword the commit title and the commit
> >> message.]
> >>
> >> Signed-off-by: Codrin Ciubotariu <codrin.ciubotariu@microchip.com>
> >> Signed-off-by: Andrei Simion <andrei.simion@microchip.com>
> >> ---
> >>  sound/soc/atmel/atmel_ssc_dai.c | 2 +-
> >>  1 file changed, 1 insertion(+), 1 deletion(-)
> >>
> >> diff --git a/sound/soc/atmel/atmel_ssc_dai.c b/sound/soc/atmel/atmel_ssc_dai.c
> >> index 7047f17fe7a8..475e7579c64c 100644
> >> --- a/sound/soc/atmel/atmel_ssc_dai.c
> >> +++ b/sound/soc/atmel/atmel_ssc_dai.c
> >> @@ -822,7 +822,7 @@ static int atmel_ssc_resume(struct snd_soc_component *component)
> >>  }
> >>
> >>  #define ATMEL_SSC_FORMATS (SNDRV_PCM_FMTBIT_S8     | SNDRV_PCM_FMTBIT_S16_LE |\
> >> -                       SNDRV_PCM_FMTBIT_S24_LE | SNDRV_PCM_FMTBIT_S32_LE)
> >> +                        SNDRV_PCM_FMTBIT_S32_LE)
> >
> > I believe this requires a comment. Else someone may add it back later
> > on.
> >
> 
> It is unclear to me. Would it be good to send v2 with this update?
> 

Yes, please send a new version. My point is that it is explained in the
commit log. This is fine when you are adding something because then
people will easily use git blame and find the commit and log. However,
because you are removing code, it is not obvious there is a reason why
it isn't there;

> >>
> >>  static const struct snd_soc_dai_ops atmel_ssc_dai_ops = {
> >>       .startup        = atmel_ssc_startup,
> >> --
> >> 2.34.1
> >>
> >
> > --
> > Alexandre Belloni, co-owner and COO, Bootlin
> > Embedded Linux and Kernel engineering
> > https://bootlin.com
> 
> Best regards,
> Andrei Simion

-- 
Alexandre Belloni, co-owner and COO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com


  reply	other threads:[~2024-09-16 12:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-16  8:52 [PATCH 0/2] Updates for Atmel SSC DAI Andrei Simion
2024-09-16  8:52 ` [PATCH 1/2] ASoC: atmel: atmel_ssc_dai: Add stream names Andrei Simion
2024-09-16 10:00   ` Alexandre Belloni
2024-09-16 11:32     ` [PATCH 2/2] ASoC: atmel: atmel_ssc_dai: Drop S24_LE support due to single channel limitation Andrei Simion
2024-09-16 12:30       ` Alexandre Belloni [this message]
2024-09-16  8:52 ` Andrei Simion
2024-09-16  9:59   ` Alexandre Belloni

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=2024091612304529f5ebe1@mail.local \
    --to=alexandre.belloni@bootlin.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=andrei.simion@microchip.com \
    --cc=broonie@kernel.org \
    --cc=claudiu.beznea@tuxon.dev \
    --cc=codrin.ciubotariu@microchip.com \
    --cc=lgirdwood@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-sound@vger.kernel.org \
    --cc=perex@perex.cz \
    --cc=tiwai@suse.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).