From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Bard Liao <bardliao@realtek.com>,
Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Oder Chiou <oder_chiou@realtek.com>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>,
"lars@metafoo.de" <lars@metafoo.de>,
"zhengxing@rock-chips.com" <zhengxing@rock-chips.com>,
"yang.a.fang@intel.com" <yang.a.fang@intel.com>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>,
John Lin <john.lin@realtek.com>,
"koro.chen@mediatek.com" <koro.chen@mediatek.com>,
"broonie@kernel.org" <broonie@kernel.org>,
Flove <flove@realtek.com>
Subject: Re: [PATCH 3/3] ASoC: rt5645: add device tree support
Date: Thu, 07 May 2015 19:07:27 +0200 [thread overview]
Message-ID: <554B9BCF.8040201@intel.com> (raw)
In-Reply-To: <1430997961.17543.38.camel@loki>
On 5/7/2015 1:26 PM, Liam Girdwood wrote:
> On Thu, 2015-05-07 at 05:34 +0000, Bard Liao wrote:
>>>>> +static int rt5645_parse_dt(struct rt5645_priv *rt5645, struct
>>>>> +device_node *np) {
>>>>> + rt5645->pdata.in2_diff = of_property_read_bool(np,
>>>>> + "realtek,in2-differential");
>>>>> + of_property_read_u32(np,
>>>>> + "realtek,dmic1-data-pin",
>>> &rt5645->pdata.dmic1_data_pin);
>>>> We should really be using device_property_() instead of
>> of_property_()
>>>> APIs since we will have to support both DT and ACPI properties.
>> Unfortunately, I can't find a way to test it.
> device_property() API calls abstract the device tree calls and ACPI
> calls. So testing with your DT based HW will work.
>
>> Is that ok we just replace all of_property_ with device_property_?
> Yes, that's the intention.
>
>> Also, is there any corresponding API for of_get_named_gpio?
>> Or we can replace it with device_property_read_u32?
>> I tried the change above, and it can build. However I don't know
>> if it can work.
> Oh, I think that's a question for Rafael. I think the intention is to
> have a 1:1 mapping between the APIs so that there are no gaps ?
Yes, that's the idea, but then the GPIO maintainers would like to clean
up the API too.
Mika is more familiar with the GPIO area than I am.
Mika, can you please help us here?
Rafael
next prev parent reply other threads:[~2015-05-07 17:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-05 13:42 [PATCH 1/3] ASoC: rt5645: fix add missing widget Bard Liao
2015-05-05 13:42 ` [PATCH 2/3] ASoC: rt5645: remove unused field in pdata Bard Liao
2015-05-06 17:50 ` Mark Brown
2015-05-05 13:42 ` [PATCH 3/3] ASoC: rt5645: add device tree support Bard Liao
2015-05-05 14:45 ` Liam Girdwood
2015-05-06 6:42 ` Bard Liao
2015-05-07 5:34 ` Bard Liao
2015-05-07 11:26 ` Liam Girdwood
2015-05-07 17:07 ` Rafael J. Wysocki [this message]
[not found] ` <20150508081339.GP1541@lahna.fi.intel.com>
2015-05-08 10:25 ` Mark Brown
2015-05-07 12:51 ` Mark Brown
2015-05-07 18:28 ` Pierre-Louis Bossart
2015-05-07 18:36 ` Mark Brown
2015-05-08 13:30 ` Pierre-Louis Bossart
2015-05-08 16:46 ` Mark Brown
2015-05-08 19:05 ` Pierre-Louis Bossart
2015-05-06 17:48 ` [PATCH 1/3] ASoC: rt5645: fix add missing widget Mark Brown
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=554B9BCF.8040201@intel.com \
--to=rafael.j.wysocki@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=flove@realtek.com \
--cc=john.lin@realtek.com \
--cc=koro.chen@mediatek.com \
--cc=lars@metafoo.de \
--cc=lgirdwood@gmail.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=oder_chiou@realtek.com \
--cc=yang.a.fang@intel.com \
--cc=zhengxing@rock-chips.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).