From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Peter Ujfalusi <peter.ujfalusi@ti.com>
Cc: Liam Girdwood <lrg@ti.com>, Tony Lindgren <tony@atomide.com>,
Benoit Cousson <b-cousson@ti.com>,
Misael Lopez Cruz <misael.lopez@ti.com>,
alsa-devel@alsa-project.org, linux-omap@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [PATCH 1/5] ASoC: omap-dmic: Add device tree bindings
Date: Sun, 11 Dec 2011 11:20:47 +0800 [thread overview]
Message-ID: <20111211032046.GH2800@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4EDF27A5.7090909@ti.com>
On Wed, Dec 07, 2011 at 10:45:25AM +0200, Peter Ujfalusi wrote:
> I felt it is the right thing to document the current situation.
If we're going to document bindings like this it feels like we should
have a split in the directories in the same way that we handle the
different stability levels for sysfs documentation.
> The documentation will be updated as we can move away from the
> "ti,hwmods" tag from DT.
> I can place comment in the documentation for omap-dmic, omap-mcpdm
> stating that the use of "ti,hwmods" is required at the moment, but it is
> temporally solution.
At the very least, yes.
WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] ASoC: omap-dmic: Add device tree bindings
Date: Sun, 11 Dec 2011 11:20:47 +0800 [thread overview]
Message-ID: <20111211032046.GH2800@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4EDF27A5.7090909@ti.com>
On Wed, Dec 07, 2011 at 10:45:25AM +0200, Peter Ujfalusi wrote:
> I felt it is the right thing to document the current situation.
If we're going to document bindings like this it feels like we should
have a split in the directories in the same way that we handle the
different stability levels for sysfs documentation.
> The documentation will be updated as we can move away from the
> "ti,hwmods" tag from DT.
> I can place comment in the documentation for omap-dmic, omap-mcpdm
> stating that the use of "ti,hwmods" is required at the moment, but it is
> temporally solution.
At the very least, yes.
next prev parent reply other threads:[~2011-12-11 3:20 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-02 9:52 [PATCH 0/5] ASoC: OMAP4: Device tree support for DMIC, McPDM Peter Ujfalusi
2011-12-02 9:52 ` Peter Ujfalusi
2011-12-02 9:52 ` [PATCH 1/5] ASoC: omap-dmic: Add device tree bindings Peter Ujfalusi
2011-12-02 9:52 ` Peter Ujfalusi
2011-12-02 12:25 ` Mark Brown
2011-12-02 12:25 ` Mark Brown
2011-12-02 12:29 ` Cousson, Benoit
2011-12-02 12:29 ` Cousson, Benoit
2011-12-02 12:32 ` Peter Ujfalusi
2011-12-02 12:32 ` Peter Ujfalusi
2011-12-02 13:02 ` Mark Brown
2011-12-02 13:02 ` Mark Brown
2011-12-02 13:31 ` Cousson, Benoit
2011-12-02 13:31 ` Cousson, Benoit
2011-12-02 14:00 ` Mark Brown
2011-12-02 14:00 ` Mark Brown
2011-12-02 14:59 ` Cousson, Benoit
2011-12-02 14:59 ` Cousson, Benoit
2011-12-02 15:29 ` Mark Brown
2011-12-02 15:29 ` Mark Brown
2011-12-03 11:22 ` Mark Brown
2011-12-03 11:22 ` Mark Brown
2011-12-05 13:45 ` Peter Ujfalusi
2011-12-05 13:45 ` Peter Ujfalusi
2011-12-05 15:46 ` Mark Brown
2011-12-05 15:46 ` Mark Brown
2011-12-07 8:45 ` Peter Ujfalusi
2011-12-07 8:45 ` Peter Ujfalusi
2011-12-11 3:20 ` Mark Brown [this message]
2011-12-11 3:20 ` Mark Brown
2011-12-02 9:52 ` [PATCH 2/5] ASoC: omap-mcpdm: " Peter Ujfalusi
2011-12-02 9:52 ` Peter Ujfalusi
2011-12-02 9:52 ` [PATCH 3/5] OMAP4: devices: Do not create dmic device if the dtb has been provided Peter Ujfalusi
2011-12-02 9:52 ` Peter Ujfalusi
2011-12-02 9:52 ` [PATCH 4/5] OMAP4: devices: Do not create mcpdm " Peter Ujfalusi
2011-12-02 9:52 ` Peter Ujfalusi
2011-12-02 9:53 ` [PATCH 5/5] ARM: OMAP4: DTS: Support for dmic, and McPDM in device tree Peter Ujfalusi
2011-12-02 9:53 ` Peter Ujfalusi
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=20111211032046.GH2800@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=b-cousson@ti.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-omap@vger.kernel.org \
--cc=lrg@ti.com \
--cc=misael.lopez@ti.com \
--cc=peter.ujfalusi@ti.com \
--cc=tony@atomide.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.