From: Takashi Iwai <tiwai@suse.de>
To: "Ismaïl Bahloul" <i.bahloul01@gmail.com>
Cc: linux-sound@vger.kernel.org, tiwai@suse.com, perex@perex.cz,
linux-usb@vger.kernel.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org, corbet@lwn.net,
skhan@linuxfoundation.org, rdunlap@infradead.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH v7 0/8] ALSA: usb: add RME Babyface Pro driver (proprietary mode)
Date: Mon, 02 Nov 2026 15:03:52 +0100 [thread overview]
Message-ID: <87zevr8h4n.wl-tiwai@suse.de> (raw)
In-Reply-To: <20261027113140.134257-1-i.bahloul01@gmail.com>
On Tue, 27 Oct 2026 12:31:31 +0100,
Ismaïl Bahloul wrote:
>
> Hi Takashi,
>
> This is v7 of the RME Babyface Pro proprietary-mode driver. The split
> is the one you asked for in the v4 review and that v5 introduced: a
> minimal core first, the mixer added piece by piece, suspend/resume near
> the end, the front panel and the DSP EQ last, and a design document.
> v7 keeps that split and folds in the fixes made since v6, and is
> rebased onto next-20261026, the most recent snapshot at the time of
> writing.
>
> This is not an RFC. The split you asked for in the v4 review has been
> in place since v5, the open points at the end are documented and none
> of them blocks a merge, so the series is submitted for merge rather
> than for another design round.
Thanks for the updates. The split patches look much better than
before, which made easier to review.
I haven't fully reviewed in details, but I see you've received quite a
few complaints from Sashiko, so please check them again, and fix if
they are valid. If they are to be ignored, just explain.
In general, a few things I noticed:
- Please try to use the new guard & co macros for spin/mutex locks and
RCU. They are much safer than manual lock/unlock. (A caveat is
that you need to be careful not to mix up with guard() and goto,
though.)
- The inner loop of babyface_playback_copy() and *_capture_copy() can
be simple memcpy(). You basically copy each 4 bytes as-is and they
are continuous for channels, after all.
- The bf_seen_before() may lead to unlimited amount of list contents,
which isn't really good.
thanks,
Takashi
prev parent reply other threads:[~2026-11-02 14:03 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 11:31 Ismaïl Bahloul
2026-10-27 11:31 ` [PATCH v7 1/8] ALSA: usb: add RME Babyface Pro driver core (probe, PCM stream) Ismaïl Bahloul
2026-10-27 11:31 ` [PATCH v7 2/8] ALSA: usb: babyfacepro: add output masters and crosspoint routing Ismaïl Bahloul
2026-10-27 11:31 ` [PATCH v7 3/8] ALSA: usb: babyfacepro: add mic preamp, phantom/pad and input trim Ismaïl Bahloul
2026-10-27 11:31 ` [PATCH v7 4/8] ALSA: usb: babyfacepro: add routing flags and varispeed pitch Ismaïl Bahloul
2026-10-27 11:31 ` [PATCH v7 5/8] ALSA: usb: babyfacepro: add S3 suspend/resume Ismaïl Bahloul
2026-10-27 11:31 ` [PATCH v7 6/8] ALSA: usb: babyfacepro: add the front-panel poll and controls Ismaïl Bahloul
2026-10-27 11:31 ` [PATCH v7 7/8] ALSA: usb: babyfacepro: add the hardware DSP EQ Ismaïl Bahloul
2026-10-27 11:31 ` [PATCH v7 8/8] Documentation: sound: add the Babyface Pro proprietary-mode design doc Ismaïl Bahloul
2026-11-02 14:03 ` Takashi Iwai [this message]
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=87zevr8h4n.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=corbet@lwn.net \
--cc=i.bahloul01@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=perex@perex.cz \
--cc=rdunlap@infradead.org \
--cc=skhan@linuxfoundation.org \
--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
all inboxes | Powered by JetHome®