From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Bo Shen <voice.shen@atmel.com>, Mark Brown <broonie@kernel.org>
Cc: 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:24:38 +0100 [thread overview]
Message-ID: <54C65C36.9050106@atmel.com> (raw)
In-Reply-To: <54B866B9.8000900@atmel.com>
Le 16/01/2015 02:17, Bo Shen a écrit :
> Hi Mark,
>
> On 01/15/2015 07:54 PM, Mark Brown wrote:
>> On Mon, Dec 15, 2014 at 11:31:11AM +0800, Bo Shen wrote:
>>
>>> +#ifdef CONFIG_OF
>>> +static enum wm8904_type wm8904_data = WM8904;
>>> +static enum wm8904_type wm8912_data = WM8912;
>>> +
>>> +static const struct of_device_id wm8904_of_match[] = {
>>> + {
>>> + .compatible = "wlf,wm8904",
>>> + .data = &wm8904_data,
>>
>> 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.
>
> Thanks.
>
> Best Regards,
> Bo Shen
I don't understand what's keeping this patch from being applied. Voice,
do you mind re-sending?
On my side, I take the two patches that apply on AT91 DT (2/3 and 3/3).
Bye,
--
Nicolas Ferre
--
To unsubscribe from this list: send the line "unsubscribe linux-sound" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Bo Shen <voice.shen@atmel.com>, Mark Brown <broonie@kernel.org>
Cc: 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 15:24:38 +0000 [thread overview]
Message-ID: <54C65C36.9050106@atmel.com> (raw)
In-Reply-To: <54B866B9.8000900@atmel.com>
Le 16/01/2015 02:17, Bo Shen a écrit :
> Hi Mark,
>
> On 01/15/2015 07:54 PM, Mark Brown wrote:
>> On Mon, Dec 15, 2014 at 11:31:11AM +0800, Bo Shen wrote:
>>
>>> +#ifdef CONFIG_OF
>>> +static enum wm8904_type wm8904_data = WM8904;
>>> +static enum wm8904_type wm8912_data = WM8912;
>>> +
>>> +static const struct of_device_id wm8904_of_match[] = {
>>> + {
>>> + .compatible = "wlf,wm8904",
>>> + .data = &wm8904_data,
>>
>> 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.
>
> Thanks.
>
> Best Regards,
> Bo Shen
I don't understand what's keeping this patch from being applied. Voice,
do you mind re-sending?
On my side, I take the two patches that apply on AT91 DT (2/3 and 3/3).
Bye,
--
Nicolas Ferre
WARNING: multiple messages have this Message-ID (diff)
From: nicolas.ferre@atmel.com (Nicolas Ferre)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/3] ASoC: codecs: wm8904: add dt ids table
Date: Mon, 26 Jan 2015 16:24:38 +0100 [thread overview]
Message-ID: <54C65C36.9050106@atmel.com> (raw)
In-Reply-To: <54B866B9.8000900@atmel.com>
Le 16/01/2015 02:17, Bo Shen a ?crit :
> Hi Mark,
>
> On 01/15/2015 07:54 PM, Mark Brown wrote:
>> On Mon, Dec 15, 2014 at 11:31:11AM +0800, Bo Shen wrote:
>>
>>> +#ifdef CONFIG_OF
>>> +static enum wm8904_type wm8904_data = WM8904;
>>> +static enum wm8904_type wm8912_data = WM8912;
>>> +
>>> +static const struct of_device_id wm8904_of_match[] = {
>>> + {
>>> + .compatible = "wlf,wm8904",
>>> + .data = &wm8904_data,
>>
>> 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.
>
> Thanks.
>
> Best Regards,
> Bo Shen
I don't understand what's keeping this patch from being applied. Voice,
do you mind re-sending?
On my side, I take the two patches that apply on AT91 DT (2/3 and 3/3).
Bye,
--
Nicolas Ferre
WARNING: multiple messages have this Message-ID (diff)
From: Nicolas Ferre <nicolas.ferre@atmel.com>
To: Bo Shen <voice.shen@atmel.com>, Mark Brown <broonie@kernel.org>
Cc: <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:24:38 +0100 [thread overview]
Message-ID: <54C65C36.9050106@atmel.com> (raw)
In-Reply-To: <54B866B9.8000900@atmel.com>
Le 16/01/2015 02:17, Bo Shen a écrit :
> Hi Mark,
>
> On 01/15/2015 07:54 PM, Mark Brown wrote:
>> On Mon, Dec 15, 2014 at 11:31:11AM +0800, Bo Shen wrote:
>>
>>> +#ifdef CONFIG_OF
>>> +static enum wm8904_type wm8904_data = WM8904;
>>> +static enum wm8904_type wm8912_data = WM8912;
>>> +
>>> +static const struct of_device_id wm8904_of_match[] = {
>>> + {
>>> + .compatible = "wlf,wm8904",
>>> + .data = &wm8904_data,
>>
>> 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.
>
> Thanks.
>
> Best Regards,
> Bo Shen
I don't understand what's keeping this patch from being applied. Voice,
do you mind re-sending?
On my side, I take the two patches that apply on AT91 DT (2/3 and 3/3).
Bye,
--
Nicolas Ferre
next prev parent reply other threads:[~2015-01-26 15:24 UTC|newest]
Thread overview: 37+ 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 ` Bo Shen
2014-12-15 3:31 ` Bo Shen
2014-12-15 3:31 ` Bo Shen
[not found] ` <1418614273-2303-1-git-send-email-voice.shen-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
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 ` Bo Shen
2014-12-15 3:31 ` Bo Shen
2014-12-15 3:31 ` Bo Shen
2014-12-15 3:31 ` [PATCH v2 3/3] ARM: at91: at91sam9n12ek/dt: " Bo Shen
2014-12-15 3:31 ` Bo Shen
2014-12-15 3:31 ` Bo Shen
2014-12-15 3:31 ` Bo Shen
2015-01-13 15:20 ` [PATCH v2 1/3] ASoC: codecs: wm8904: add dt ids table Nicolas Ferre
2015-01-13 15:20 ` Nicolas Ferre
2015-01-13 15:20 ` Nicolas Ferre
2015-01-13 15:20 ` Nicolas Ferre
2015-01-15 11:54 ` Mark Brown
2015-01-15 11:54 ` Mark Brown
2015-01-16 1:17 ` Bo Shen
2015-01-16 1:17 ` Bo Shen
2015-01-16 1:17 ` Bo Shen
2015-01-16 1:17 ` Bo Shen
2015-01-26 15:24 ` Nicolas Ferre [this message]
2015-01-26 15:24 ` Nicolas Ferre
2015-01-26 15:24 ` Nicolas Ferre
2015-01-26 15:24 ` Nicolas Ferre
[not found] ` <54C65C36.9050106-AIFe0yeh4nAAvxtiuMwx3w@public.gmane.org>
2015-01-26 16:42 ` Mark Brown
2015-01-26 16:42 ` Mark Brown
2015-01-26 16:42 ` Mark Brown
[not found] ` <20150126164229.GB21293-GFdadSzt00ze9xe1eoZjHA@public.gmane.org>
2015-01-26 16:49 ` [alsa-devel] " Lars-Peter Clausen
2015-01-26 16:49 ` Lars-Peter Clausen
2015-01-26 16:49 ` Lars-Peter Clausen
2015-01-26 16:49 ` Lars-Peter Clausen
[not found] ` <54C67007.6000708-Qo5EllUWu/uELgA04lAiVw@public.gmane.org>
2015-01-27 1:35 ` Bo Shen
2015-01-27 1:35 ` Bo Shen
2015-01-27 1:35 ` Bo Shen
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=54C65C36.9050106@atmel.com \
--to=nicolas.ferre@atmel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.