From: Mark Brown <broonie@kernel.org>
To: Robert Jarzmik <robert.jarzmik@free.fr>
Cc: devicetree@vger.kernel.org, alsa-devel@alsa-project.org,
linux-kernel@vger.kernel.org,
patches@opensource.wolfsonmicro.com,
Liam Girdwood <lgirdwood@gmail.com>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
Takashi Iwai <tiwai@suse.com>,
linux-arm-kernel@lists.infradead.org,
Daniel Mack <daniel@zonque.org>
Subject: Re: [PATCH 1/4] ASoC: wm9713: add binding for WM9713 codec
Date: Sun, 21 Feb 2016 10:49:20 +0900 [thread overview]
Message-ID: <20160221014920.GK18327@sirena.org.uk> (raw)
In-Reply-To: <878u2fxbp9.fsf@belgarion.home>
[-- Attachment #1.1: Type: text/plain, Size: 1328 bytes --]
On Sat, Feb 20, 2016 at 11:24:02PM +0100, Robert Jarzmik wrote:
Please fix your mail client to word wrap within paragraphs at something
substantially less than 80 columns. Doing this makes your messages much
easier to read and reply to.
> Mark Brown <broonie@kernel.org> writes:
> > On Sat, Feb 20, 2016 at 09:32:58PM +0100, Robert Jarzmik wrote:
> > It will eumerate the AC'97 bus by itself and does not need the CODEC to
> > be described.
> I think I still don't get it.
> So let's rephrase it another way : how will the function wm9713_probe() be
> called, ie. what is the possible function backtrace leading to that call ?
It will not be called, the generic AC'97 code will be used.
> > They should be created as a function of enumerating the CODEC. If you
> > use the genric AC'97 stuff it doesn't use ASoC at all and this happens
> > as a side effect.
> I don't get that either. For me sound/soc/pci/ac97/ac97_codec.c is PCI specific,
> not generic, so what is "generic AC'97 stuff" ? I will never be able to use it
> as on my platforms CONFIG_PCI=n.
That is the generic code, there is no PCI dependency.
> Do you have a devicetree example somewhere, with (ac97 host, audio codec) pair I
> can have a look at to understand ?
Some Atmel boards do this IIRC, as does the AACI driver (via AMBA but
same effect).
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2016-02-21 1:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-20 14:37 [PATCH 1/4] ASoC: wm9713: add binding for WM9713 codec Robert Jarzmik
[not found] ` <1455979079-9030-1-git-send-email-robert.jarzmik-GANU6spQydw@public.gmane.org>
2016-02-20 14:37 ` [PATCH 2/4] ASoC: wm9713: add device tree support Robert Jarzmik
2016-02-20 14:37 ` [PATCH 3/4] ASoC: pxa: add binding for pxa2xx-ac97 audio complex Robert Jarzmik
[not found] ` <1455979079-9030-3-git-send-email-robert.jarzmik-GANU6spQydw@public.gmane.org>
2016-02-23 19:19 ` Rob Herring
2016-02-26 22:37 ` Robert Jarzmik
2016-02-20 17:14 ` [PATCH 1/4] ASoC: wm9713: add binding for WM9713 codec Mark Brown
[not found] ` <20160220171459.GA18327-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-02-20 18:22 ` Robert Jarzmik
[not found] ` <871t87z1gz.fsf-4ty26DBLk+jEm7gnYqmdkQ@public.gmane.org>
2016-02-20 19:59 ` Mark Brown
[not found] ` <20160220195925.GF18327-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-02-20 20:32 ` Robert Jarzmik
2016-02-20 21:16 ` Mark Brown
[not found] ` <20160220211659.GG18327-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2016-02-20 22:24 ` Robert Jarzmik
2016-02-21 1:49 ` Mark Brown [this message]
2016-02-26 1:33 ` Robert Jarzmik
[not found] ` <87povkuuf6.fsf-4ty26DBLk+jEm7gnYqmdkQ@public.gmane.org>
2016-02-26 2:30 ` Mark Brown
2016-02-26 21:04 ` Robert Jarzmik
[not found] ` <87k2lruqsw.fsf-4ty26DBLk+jEm7gnYqmdkQ@public.gmane.org>
2016-02-27 2:03 ` Mark Brown
2016-02-20 14:37 ` [PATCH 4/4] ASoC: pxa: add pxa2xx-ac97 devicetree support 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=20160221014920.GK18327@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=daniel@zonque.org \
--cc=devicetree@vger.kernel.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=robert.jarzmik@free.fr \
--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;
as well as URLs for NNTP newsgroup(s).