From: Charles Keepax <ckeepax@opensource.cirrus.com>
To: Lee Jones <lee@kernel.org>
Cc: broonie@kernel.org, robh@kernel.org, krzk+dt@kernel.org,
conor+dt@kernel.org, lgirdwood@gmail.com,
linux-sound@vger.kernel.org, devicetree@vger.kernel.org,
mfd@lists.linux.dev, linux-kernel@vger.kernel.org,
patches@opensource.cirrus.com
Subject: Re: [PATCH 3/3] mfd: cs42l43: Add support for new cs42l44 variant
Date: Thu, 16 Jul 2026 16:47:33 +0100 [thread overview]
Message-ID: <alj9FS+pm5gm8Fp3@opensource.cirrus.com> (raw)
In-Reply-To: <20260716151437.GA1409595@google.com>
On Thu, Jul 16, 2026 at 04:14:37PM +0100, Lee Jones wrote:
> On Wed, 08 Jul 2026, Charles Keepax wrote:
> > The cs42l44 is a cost optimised variant of cs42l43b. Add basic support
> > for this new device.
> >
> > Signed-off-by: Charles Keepax <ckeepax@opensource.cirrus.com>
> > ---
> > switch (devid) {
> > case CS42L43_DEVID_VAL:
> > + valid_id = (cs42l43->variant_id == CS42L43_DEVID_VAL);
> > + break;
> > case CS42L43B_DEVID_VAL:
> > - if (devid != cs42l43->variant_id) {
> > - dev_err(cs42l43->dev,
> > - "Device ID (0x%06x) does not match variant ID (0x%06lx)\n",
> > - devid, cs42l43->variant_id);
> > - goto err;
> > - }
>
> Needs a fall-through statement.
I thought they weren't typically used if the case had no content,
the resultant code looks like:
case CS42L43B_DEVID_VAL:
case CS42L44_DEVID_VAL:
valid_id = (cs42l43->variant_id == CS42L43B_DEVID_VAL);
break;
But happy to add one if we really want it?
> > + case CS42L44_DEVID_VAL:
> > + valid_id = (cs42l43->variant_id == CS42L43B_DEVID_VAL);
> > break;
> > default:
> > dev_err(cs42l43->dev, "Unrecognised devid: 0x%06x\n", devid);
> > goto err;
> > }
> >
> > + if (!valid_id) {
>
> How is this nor handled in the default branch?
The default case ends in goto err; so this doesn't run in that
case.
Thanks,
Charles
next prev parent reply other threads:[~2026-07-16 15:47 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-08 14:00 [PATCH 0/3] Add support for cs42l44 Charles Keepax
2026-07-08 14:00 ` [PATCH 1/3] ASoC: dt-bindings: cirrus,cs42l43: Add CS42L44 variant Charles Keepax
2026-07-08 14:00 ` [PATCH 2/3] mfd: cs42l43: Tidy up formatting on sdw_device_id table Charles Keepax
2026-07-16 15:16 ` (subset) " Lee Jones
2026-07-08 14:00 ` [PATCH 3/3] mfd: cs42l43: Add support for new cs42l44 variant Charles Keepax
2026-07-16 15:14 ` Lee Jones
2026-07-16 15:47 ` Charles Keepax [this message]
2026-07-16 16:08 ` Lee Jones
2026-07-16 16:26 ` Charles Keepax
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=alj9FS+pm5gm8Fp3@opensource.cirrus.com \
--to=ckeepax@opensource.cirrus.com \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=mfd@lists.linux.dev \
--cc=patches@opensource.cirrus.com \
--cc=robh@kernel.org \
/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