From: Lars-Peter Clausen <lars@metafoo.de>
To: Stephen Warren <swarren@wwwdotorg.org>
Cc: Linux-ALSA <alsa-devel@alsa-project.org>,
Stephen Warren <swarren@nvidia.com>,
Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Mark Brown <broonie@kernel.org>,
Liam Girdwood <lgirdwood@gmail.com>, Simon <horms@verge.net.au>,
Kuninori Morimoto <kuninori.morimoto.gx@gmail.com>
Subject: Re: [PATCH] ASoC: ak4554: add DT support
Date: Fri, 05 Jul 2013 19:04:10 +0200 [thread overview]
Message-ID: <51D6FC8A.1050908@metafoo.de> (raw)
In-Reply-To: <51D6FA9D.30105@wwwdotorg.org>
On 07/05/2013 06:55 PM, Stephen Warren wrote:
> On 07/05/2013 03:37 AM, Lars-Peter Clausen wrote:
>>> + - compatible : "asahi-kasei,ak4554"
>>
>> The vendor prefix for Asahi Kasei is documented as "ak" in
>> Documentation/devicetree/bindings/vendor-prefixes.txt. But it doesn;t seem
>> to be used in any upstream drivers, Stephen add that prefix maybe he knows
>> if it is used. If it is unused you should probably send a patch updating the
>> Documentation.
>
> It's used at:
>
> arch/arm/boot/dts/tegra20-seaboard.dts:499: compatible = "ak,ak8975";
>
> ... although I see that somebody has incorrectly modified
> ./drivers/iio/magnetometer/ak8975.c to support the "asahi-kasei," vendor
> prefix:-(
It looks as if the ak prefix was never in an upstream kernel and the commit
date that added the dt table predates the commit date for your devicetree.
- Lars
next prev parent reply other threads:[~2013-07-05 17:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-05 2:42 [PATCH] ASoC: ak4554: add DT support Kuninori Morimoto
2013-07-05 9:17 ` Mark Brown
2013-07-05 9:37 ` Lars-Peter Clausen
2013-07-05 16:55 ` Stephen Warren
2013-07-05 17:04 ` Lars-Peter Clausen [this message]
2013-07-05 17:13 ` Stephen Warren
[not found] ` <51D868CF.5080105@gmail.com>
2013-07-07 17:56 ` Lars-Peter Clausen
2013-07-08 16:03 ` Stephen Warren
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=51D6FC8A.1050908@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=horms@verge.net.au \
--cc=kuninori.morimoto.gx@gmail.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=swarren@nvidia.com \
--cc=swarren@wwwdotorg.org \
/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.