From: Takashi Iwai <tiwai@suse.de>
To: "Cássio Gabriel" <cassiogabrielcontato@gmail.com>
Cc: Takashi Iwai <tiwai@suse.com>, Jaroslav Kysela <perex@perex.cz>,
linux-sound@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 1/2] ALSA: sscape: Cache per-card resources for board reinitialization
Date: Sat, 11 Apr 2026 10:07:58 +0200 [thread overview]
Message-ID: <87a4v9gbs1.wl-tiwai@suse.de> (raw)
In-Reply-To: <20260411-alsa-sscape-pm-v1-1-3058d988783a@gmail.com>
On Sat, 11 Apr 2026 06:54:29 +0200,
Cássio Gabriel wrote:
> +/*
> + * Restore the SoundScape's MIDI control state after the firmware
> + * upload has made the host interface available again.
> + */
> +static int sscape_restore_midi_state(struct soundscape *sscape)
> +{
> + int err = 1;
> +
> + guard(spinlock_irqsave)(&sscape->lock);
> + set_host_mode_unsafe(sscape->io_base);
> + err &= host_write_ctrl_unsafe(sscape->io_base, CMD_SET_MIDI_VOL, 100);
> + err &= host_write_ctrl_unsafe(sscape->io_base, sscape->midi_vol, 100);
> + err &= host_write_ctrl_unsafe(sscape->io_base, CMD_XXX_MIDI_VOL, 100);
> + err &= host_write_ctrl_unsafe(sscape->io_base, sscape->midi_vol, 100);
> + err &= host_write_ctrl_unsafe(sscape->io_base, CMD_SET_EXTMIDI, 100);
> + err &= host_write_ctrl_unsafe(sscape->io_base, 0, 100);
> + err &= host_write_ctrl_unsafe(sscape->io_base, CMD_ACK, 100);
> + set_midi_mode_unsafe(sscape->io_base);
> +
> + return err ? 0 : -EIO;
The above means it checks only the error of the last write.
Is it intentional?
thanks,
Takashi
next prev parent reply other threads:[~2026-04-11 8:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-11 4:54 [PATCH 0/2] ALSA: sscape: add suspend/resume support Cássio Gabriel
2026-04-11 4:54 ` [PATCH 1/2] ALSA: sscape: Cache per-card resources for board reinitialization Cássio Gabriel
2026-04-11 8:07 ` Takashi Iwai [this message]
2026-04-11 14:33 ` Cássio Gabriel Monteiro Pires
2026-04-11 4:54 ` [PATCH 2/2] ALSA: sscape: Add suspend and resume support Cássio Gabriel
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=87a4v9gbs1.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=cassiogabrielcontato@gmail.com \
--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