[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <fbbc0963-fba5-4178-b886-fbb35c0c8df2@sirena.org.uk>
Date: Thu, 8 Jun 2023 11:15:38 +0100
From: Mark Brown <broonie@...nel.org>
To: Walker Chen <walker.chen@...rfivetech.com>
Cc: Claudiu Beznea <Claudiu.Beznea@...rochip.com>,
Dan Carpenter <dan.carpenter@...aro.org>,
Liam Girdwood <lgirdwood@...il.com>,
Takashi Iwai <tiwai@...e.com>,
Jaroslav Kysela <perex@...ex.cz>, alsa-devel@...a-project.org,
linux-kernel@...r.kernel.org
Subject: Re: [PATCH v1] ASoC: starfive: Cleanup and fix error check for
JH7110 TDM
On Thu, Jun 08, 2023 at 10:15:03AM +0800, Walker Chen wrote:
> On 2023/6/7 19:44, Mark Brown wrote:
> >> - (tdm->rx.wl << WL_BIT) |
> >> - (tdm->rx.sscale << SSCALE_BIT) |
> >> - (tdm->rx.sl << SL_BIT) |
> >> - (tdm->rx.lrj << LRJ_BIT);
> >> + datarx = (tdm->rxwl << 8) |
> >> + (tdm->rxsscale << 4) |
> >> + (tdm->rxsl << 2) |
> >> + TDM_PCMRXCR_LEFT_J;
> > I'm not sure this change to use numbers here is a win - the _BIT
> > definitions look fine (I might've called them _SHIFT but whatever).
> This is Claudiu's advice. Using the macro BIT() to replace these definition of *_BIT,
> it will result in big changes in the code.
I'm questioning doing a change at all.
> Please refer to previous comments:
> https://lore.kernel.org/all/143e2fa2-e85d-8036-4f74-ca250c026c1b@microchip.com/
I can't find the comments you're referring to in there.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists