From: Mark Brown <broonie@kernel.org>
To: Nicolas Ferre <nicolas.ferre@atmel.com>
Cc: Bo Shen <voice.shen@atmel.com>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
alsa-devel@alsa-project.org, linux-sound@vger.kernel.org,
Alexander Morozov <linux@meltdown.ru>
Subject: Re: [PATCH v2 1/3] ASoC: codecs: wm8904: add dt ids table
Date: Mon, 26 Jan 2015 16:42:29 +0000 [thread overview]
Message-ID: <20150126164229.GB21293@sirena.org.uk> (raw)
In-Reply-To: <54C65C36.9050106@atmel.com>
[-- Attachment #1: Type: text/plain, Size: 1074 bytes --]
On Mon, Jan 26, 2015 at 04:24:38PM +0100, Nicolas Ferre wrote:
> Le 16/01/2015 02:17, Bo Shen a écrit :
> >> Does this end up in the i2c_driver_id driver data or do we need some
> >> extra code when devtype is assigned to check for an of_node and look at
> >> the DT data instead? That certainly used to be the case...
> > At the beginning I think as the same as you, and also add the code to
> > get the data as I do in <drivers/misc/atmel-ssc.c>. However, as I
> > remember, I2C seems only use the compatible string after the comma, that
> > means only for "wlf,wm8904", it uses "wm8904" to match. So, I remove all
> > the code I added, and just keep these, and it can get the device type
> > correctly.
> > So, when I submit the patch and keep the code as simple as possible.
> I don't understand what's keeping this patch from being applied. Voice,
> do you mind re-sending?
I need to convince myself that the above actually works and is doing the
right thing; the above explanation sounds like if it works it might be
relying on a bug.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]
next prev parent reply other threads:[~2015-01-26 16:42 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 3:31 [PATCH v2 1/3] ASoC: codecs: wm8904: add dt ids table Bo Shen
2014-12-15 3:31 ` [PATCH v2 2/3] ARM: at91: sama5d3xek/dt: use dt ids for wm8904 Bo Shen
2014-12-15 3:31 ` [PATCH v2 3/3] ARM: at91: at91sam9n12ek/dt: " Bo Shen
2015-01-13 15:20 ` [PATCH v2 1/3] ASoC: codecs: wm8904: add dt ids table Nicolas Ferre
2015-01-15 11:54 ` Mark Brown
2015-01-16 1:17 ` Bo Shen
2015-01-26 15:24 ` Nicolas Ferre
2015-01-26 16:42 ` Mark Brown [this message]
2015-01-26 16:49 ` [alsa-devel] " Lars-Peter Clausen
2015-01-27 1:35 ` Bo Shen
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=20150126164229.GB21293@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sound@vger.kernel.org \
--cc=linux@meltdown.ru \
--cc=nicolas.ferre@atmel.com \
--cc=voice.shen@atmel.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