From: Ivan Orlov <ivan.orlov0322@gmail.com>
To: Takashi Iwai <tiwai@suse.de>
Cc: corbet@lwn.net, akpm@linux-foundation.org, perex@perex.cz,
tiwai@suse.com, broonie@kernel.org, skhan@linuxfoundation.org,
linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org,
alsa-devel@alsa-project.org, linux-kselftest@vger.kernel.org,
gregkh@linuxfoundation.org, himadrispandya@gmail.com,
linux-kernel-mentees@lists.linuxfoundation.org
Subject: Re: [PATCH 2/3] ALSA: Implement the new virtual driver
Date: Sun, 14 May 2023 14:08:53 +0400 [thread overview]
Message-ID: <6f6d09b3-39e7-58b6-221f-6276d3ce213a@gmail.com> (raw)
In-Reply-To: <878rdr8e5f.wl-tiwai@suse.de>
On 5/14/23 13:18, Takashi Iwai wrote:
> The idea is interesting, and it's a definitely good thing to have.
>
> I wonder, though, whether it could be better provided as an extention
> to the existing snd-dummy driver. The advantage of extending
> snd-dummy driver would be that it already supports different formats,
> etc. OTOH, if we create an individual driver, the pro side is the
> simpleness of the code.
>
> I'm inclined to go with a separate driver, but I'm open about this.
> Maybe Jaroslav and Mark have some opinions?
>
> About this patch set: the driver name should be a bit more specific,
> as this isn't a generic virtual driver that is used for general
> purpose but it's only for testing. And it's only for testing PCM.
> So, a name like snd-test-pcm would be more appropriate, IMO.
>
> And, we want the coverage of different formats, channels, rates and
> accesses (interleaved vs non-interleaved). How can we extend somehow
> more for that?
>
>
> thanks,
>
> Takashi
Hello Takashi! Thank you for your reply. I fully agree with the naming
issue, and I'll change it in the future versions of the patch set in
case we choose to have it as a separate driver. I also prefer this
option because in my opinion the use cases of these drivers are a little
bit different. Also, I believe I can extend the driver to support
different formats, channels and accesses in the near future.
Additionally, implementing these changes would be a perfect task for the
end of the Linux Kernel Mentorship program I'm going through :) However,
I'm open to other views on this, and I'm ready to move the functionality
from my driver to the snd-dummy in case we prefer this option.
Thanks again for considering my changes!
Kind regards,
Ivan Orlov.
next prev parent reply other threads:[~2023-05-14 10:09 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-13 20:20 [PATCH 1/3] docs: admin-guide: add valsa driver documentation Ivan Orlov
2023-05-13 20:20 ` [PATCH 2/3] ALSA: Implement the new virtual driver Ivan Orlov
2023-05-14 9:18 ` Takashi Iwai
2023-05-14 10:08 ` Ivan Orlov [this message]
2023-05-13 20:20 ` [PATCH 3/3] selftests: ALSA: Add test for the 'valsa' driver Ivan Orlov
2023-05-15 1:28 ` Mark Brown
2023-05-15 5:58 ` Ivan Orlov
2023-05-14 9:21 ` [PATCH 1/3] docs: admin-guide: add valsa driver documentation Takashi Iwai
2023-05-14 10:12 ` Ivan Orlov
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=6f6d09b3-39e7-58b6-221f-6276d3ce213a@gmail.com \
--to=ivan.orlov0322@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=corbet@lwn.net \
--cc=gregkh@linuxfoundation.org \
--cc=himadrispandya@gmail.com \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel-mentees@lists.linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-kselftest@vger.kernel.org \
--cc=perex@perex.cz \
--cc=skhan@linuxfoundation.org \
--cc=tiwai@suse.com \
--cc=tiwai@suse.de \
/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®