From: Mark Brown <broonie@kernel.org>
To: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
Cc: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com>,
Liam Girdwood <lgirdwood@gmail.com>,
alsa-devel@alsa-project.org, linux-kernel@vger.kernel.org,
Masahiro Yamada <yamada.masahiro@socionext.com>,
Masami Hiramatsu <masami.hiramatsu@linaro.org>
Subject: Re: ASoC: About graph node issue without 'reg' property
Date: Thu, 13 Dec 2018 16:24:28 +0000 [thread overview]
Message-ID: <20181213162428.GR10669@sirena.org.uk> (raw)
In-Reply-To: <20181213193944.CCC9.4A936039@socionext.com>
[-- Attachment #1: Type: text/plain, Size: 661 bytes --]
On Thu, Dec 13, 2018 at 07:39:45PM +0900, Kunihiko Hayashi wrote:
> Maybe I think that we'd better add 'reg' properties to each port,
> however, there might be same matter in other SoCs, so I'm not sure
> whether your patch breaks the backword compatibility or
> our devicetrees are wrong.
> I'd be glad if I could hear something about this issue from you.
There's an ongoing thread between Morimoto-san and Tony Lindgren around
the graph card including this issue, there Morimoto-san proposed some
code which would let the reg property be optional. Device trees should
still be updated but that way we wouldn't actually break anything which
would be good.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2018-12-13 16:24 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-13 10:39 Kunihiko Hayashi
2018-12-13 16:24 ` Mark Brown [this message]
2018-12-13 18:27 ` Mark Brown
2018-12-14 0:05 ` Kuninori Morimoto
2018-12-14 2:13 ` Kunihiko Hayashi
2018-12-17 0:47 ` Kuninori Morimoto
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=20181213162428.GR10669@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=hayashi.kunihiko@socionext.com \
--cc=kuninori.morimoto.gx@renesas.com \
--cc=lgirdwood@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=masami.hiramatsu@linaro.org \
--cc=yamada.masahiro@socionext.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
all inboxes | Powered by JetHome®