From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Padma Venkat <padma.kvr@gmail.com>
Cc: alsa-devel@alsa-project.org,
linux-arm-kernel@lists.infradead.org,
linux-samsung-soc@vger.kernel.org,
Sangbeom Kim <sbkim73@samsung.com>,
Kukjin Kim <kgene.kim@samsung.com>,
devicetree-discuss@lists.ozlabs.org
Subject: Re: [GIT PULL] ASoC: Samsung: Updates for v3.8
Date: Wed, 28 Nov 2012 09:08:40 +0000 [thread overview]
Message-ID: <20121128090840.GH32691@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <CAAgF-Bfv46Xt0hFdPmviCdZbpje1M4MBnmCsHGgdOjcq4SnuJw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 858 bytes --]
On Wed, Nov 28, 2012 at 11:21:31AM +0530, Padma Venkat wrote:
> On Wed, Nov 28, 2012 at 10:55 AM, Sangbeom Kim <sbkim73@samsung.com> wrote:
> >> > The requirement for an alias is also very odd, where does that come from?
> >> I don't know that Which one is odd. Please let me know.
> > Having them at all is odd - it's not something other DT bindings have needed and there was nothing
> > saying what it was for.
> What is the exact requirement here? Should I remove the alias ids or
> I2S1 and I2S2 nodes as they are in disabled state? This is done same
> way as SPI and I2C. Please explain me.
If you need those aliases you need to explain why. They're listed as
mandatory so presumably they must be needed for something? It might be
that this is a good idea we didn't think of before so the answer is just
to document that rather than remove them.
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2012-11-28 9:08 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <001601cdcd28$ce5204c0$6af60e40$@com>
2012-11-28 5:51 ` [GIT PULL] ASoC: Samsung: Updates for v3.8 Padma Venkat
2012-11-28 9:08 ` Mark Brown [this message]
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=20121128090840.GH32691@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=kgene.kim@samsung.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-samsung-soc@vger.kernel.org \
--cc=padma.kvr@gmail.com \
--cc=sbkim73@samsung.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).