From: Takashi Iwai <tiwai@suse.de>
To: "Robert Jarzmik" <robert.jarzmik@free.fr>
Cc: "Haojian Zhuang" <haojian.zhuang@gmail.com>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"Mark Brown" <broonie@kernel.org>,
"Jaroslav Kysela" <perex@perex.cz>,
"Daniel Mack" <daniel@zonque.org>, <alsa-devel@alsa-project.org>,
<linux-arm-kernel@lists.infradead.org>,
<patches@opensource.wolfsonmicro.com>,
<linux-kernel@vger.kernel.org>
Subject: Re: [RFC PATCH 0/7] AC97 device/driver model revamp
Date: Mon, 09 May 2016 11:04:15 +0200 [thread overview]
Message-ID: <s5hlh3j8uwg.wl-tiwai@suse.de> (raw)
In-Reply-To: <1462050939-27940-1-git-send-email-robert.jarzmik@free.fr>
On Sat, 30 Apr 2016 23:15:32 +0200,
Robert Jarzmik wrote:
>
> It all started in the pxa device-tree submission here :
> https://lkml.org/lkml/2016/2/25/965
> It will be maintained in :
> git fetch https://github.com/rjarzmik/linux.git work/ac97
>
> And now it transformed into this RFC, which would bring a ground for AC'97
> devices closer to the linux device/driver model.
>
> This is just an RFC to see if we understand each other Mark.
>
> Amongst the driving ideas behind this RFC :
> - use device/driver model for AC'97
> device/driver binding is based on vendor_id{1,2}
> - use auto-probe of the AC'97 bus to enumerate codecs and create devices
> - be compatible with previous platform_data model for codecs
> => this enables a smooth transition, where a codec (here wm9713) can
> be used either through platform_device or automatic discovery
> - struct snd_ac97 is not used
> This structure is really heavy, and doesn't represent an AC97 device, but
> rather an AC'97 codec internals IIUC.
> I think it's right place would be in include/sound/ac97/codec.h.
> This is also a problem for regmap adherence, hence the
> include/sound/ac97/compat.h.
> - a new AC'97 bus Kconfig is created
> This was done for a smooth transition ... let's see if it's a good idea.
> - split the AC'97 into :
> - the codec
> - the digital controller
> - the bus
>
> Amongst the things that are not all touched yet :
> - ac97_codec.c
> The generic AC'97 codec in sound/pci/ac97/ac97_codec.c has really a lot
> features, which are not at all PCI related. They could be transfered to
> sound/ac97, without the pci specific field.
> => this deserves a deep ahead thinking, which I'll do if the current approach
> is accepted by the communauty.
>
> The most important patch is 2/7 "ALSA: ac97: add an ac97 bus". This is the main
> evaluation point for the serie, the others are here so that I can test it all.
>
> Well, this is a long term effort, which might need a complete rewrite according
> to the comments it'll get. Let's expose it for comments and see how I can
> progress with it.
I think it's good in general. The implementation looks fairly simple
and thin enough.
An open question is whether migrating the former AC97 layer into the
new bus. I'm not sure about this. Transition to a new layer always
brings subtle bugs, especially when the target devices are in wide
range of legacy ones... If any, we should start just wrapping via
the new bus ops.
Some other nitpicks:
- We usually use snd_ prefix for sound stuff. Better to keep this for
exported symbols at least.
- I don't see much value in the usefulness of compat_* stuff.
For example, it doesn't cover the actual reset procedure or such
done as in the old ac97 code. So it won't work compatibly. If it's
a few lines of changes, the direct call would be likely simpler in
the end.
- The order of patches needs reconsideration. The current patchset
will break the build, as the hook to sound/ac97/* is done in the
last patch, while you're already building against to the new stuff
beforehand.
I'll comment more on each patch if any...
thanks,
Takashi
next prev parent reply other threads:[~2016-05-09 9:04 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-30 21:15 Robert Jarzmik
2016-04-30 21:15 ` [RFC PATCH 1/7] ALSA: ac97: split out the generic ac97 registers Robert Jarzmik
2016-05-03 11:51 ` Mark Brown
2016-05-03 19:22 ` Robert Jarzmik
2016-05-04 9:07 ` Mark Brown
2016-05-05 19:06 ` Robert Jarzmik
2016-05-05 19:17 ` Mark Brown
2016-05-05 19:46 ` Robert Jarzmik
2016-05-06 17:17 ` Mark Brown
2017-09-04 17:25 ` Applied "ALSA: ac97: split out the generic ac97 registers" to the asoc tree Mark Brown
2016-04-30 21:15 ` [RFC PATCH 2/7] ALSA: ac97: add an ac97 bus Robert Jarzmik
2016-05-03 16:29 ` Mark Brown
2016-05-03 19:43 ` Robert Jarzmik
2016-05-04 16:22 ` Mark Brown
2016-05-05 19:14 ` Robert Jarzmik
2016-05-09 9:31 ` Takashi Iwai
2016-05-14 9:50 ` Robert Jarzmik
2016-05-14 15:13 ` Takashi Iwai
2016-05-15 21:29 ` Robert Jarzmik
2016-05-16 5:40 ` Takashi Iwai
2016-05-16 8:53 ` Robert Jarzmik
2016-05-16 12:58 ` Takashi Iwai
2016-05-16 13:12 ` Mark Brown
2016-04-30 21:15 ` [RFC PATCH 3/7] ASoC: wm9713: add ac97 new bus support Robert Jarzmik
2016-04-30 21:15 ` [RFC PATCH 4/7] ASoC: pxa: switch to new ac97 " Robert Jarzmik
2016-04-30 21:15 ` [RFC PATCH 5/7] ARM: pxa: mioa701 remove wm9713 from platform devices Robert Jarzmik
2016-04-30 21:15 ` [RFC PATCH 6/7] ASoC: mioa701_wm9713: convert to new ac97 bus Robert Jarzmik
2016-04-30 21:15 ` [RFC PATCH 7/7] ASoC: add new ac97 bus support Robert Jarzmik
2016-05-09 9:04 ` Takashi Iwai [this message]
2016-05-14 8:13 ` [RFC PATCH 0/7] AC97 device/driver model revamp Robert Jarzmik
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=s5hlh3j8uwg.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=daniel@zonque.org \
--cc=haojian.zhuang@gmail.com \
--cc=lgirdwood@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=patches@opensource.wolfsonmicro.com \
--cc=perex@perex.cz \
--cc=robert.jarzmik@free.fr \
/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®