From: moinejf@free.fr (Jean-Francois Moine)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ASoC: tda998x: Fix lack of required reg in DT documentation
Date: Thu, 20 Mar 2014 15:59:35 +0100 [thread overview]
Message-ID: <20140320155935.7a474173@armhf> (raw)
In-Reply-To: <20140320143110.GU7528@n2100.arm.linux.org.uk>
On Thu, 20 Mar 2014 14:31:10 +0000
Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> 1. change the DT compatible strings the driver has to accept both
> nxp,tda19988 and nxp,tda19989, and set the appropriate device
> in the DT file (tda19988). I'm a bit nervous about using
> "nxp,tda1998x" in case we're clashing with devices with different
> characteristics.
The Cubox is sold with either the TDA19988 or the TDA19989 (I don't
know about the AMX33XX boards). Then, setting the exact type in the DT
would ask for 2 differents DTs or for having two tda998x definitions in
a same DT...
--
Ken ar c'henta? | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
WARNING: multiple messages have this Message-ID (diff)
From: Jean-Francois Moine <moinejf@free.fr>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
dri-devel@lists.freedesktop.org,
Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>
Subject: Re: [PATCH] ASoC: tda998x: Fix lack of required reg in DT documentation
Date: Thu, 20 Mar 2014 15:59:35 +0100 [thread overview]
Message-ID: <20140320155935.7a474173@armhf> (raw)
In-Reply-To: <20140320143110.GU7528@n2100.arm.linux.org.uk>
On Thu, 20 Mar 2014 14:31:10 +0000
Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> 1. change the DT compatible strings the driver has to accept both
> nxp,tda19988 and nxp,tda19989, and set the appropriate device
> in the DT file (tda19988). I'm a bit nervous about using
> "nxp,tda1998x" in case we're clashing with devices with different
> characteristics.
The Cubox is sold with either the TDA19988 or the TDA19989 (I don't
know about the AMX33XX boards). Then, setting the exact type in the DT
would ask for 2 differents DTs or for having two tda998x definitions in
a same DT...
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/dri-devel
WARNING: multiple messages have this Message-ID (diff)
From: Jean-Francois Moine <moinejf@free.fr>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Sebastian Hesselbarth <sebastian.hesselbarth@gmail.com>,
devicetree@vger.kernel.org, dri-devel@lists.freedesktop.org,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ASoC: tda998x: Fix lack of required reg in DT documentation
Date: Thu, 20 Mar 2014 15:59:35 +0100 [thread overview]
Message-ID: <20140320155935.7a474173@armhf> (raw)
In-Reply-To: <20140320143110.GU7528@n2100.arm.linux.org.uk>
On Thu, 20 Mar 2014 14:31:10 +0000
Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> 1. change the DT compatible strings the driver has to accept both
> nxp,tda19988 and nxp,tda19989, and set the appropriate device
> in the DT file (tda19988). I'm a bit nervous about using
> "nxp,tda1998x" in case we're clashing with devices with different
> characteristics.
The Cubox is sold with either the TDA19988 or the TDA19989 (I don't
know about the AMX33XX boards). Then, setting the exact type in the DT
would ask for 2 differents DTs or for having two tda998x definitions in
a same DT...
--
Ken ar c'hentañ | ** Breizh ha Linux atav! **
Jef | http://moinejf.free.fr/
next prev parent reply other threads:[~2014-03-20 14:59 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-20 8:58 [PATCH] ASoC: tda998x: Fix lack of required reg in DT documentation Jean-Francois Moine
2014-03-20 8:58 ` Jean-Francois Moine
2014-03-20 8:58 ` Jean-Francois Moine
2014-03-20 12:32 ` Sebastian Hesselbarth
2014-03-20 12:32 ` Sebastian Hesselbarth
2014-03-20 12:32 ` Sebastian Hesselbarth
2014-03-20 12:36 ` Russell King - ARM Linux
2014-03-20 12:36 ` Russell King - ARM Linux
2014-03-20 12:36 ` Russell King - ARM Linux
2014-03-20 13:01 ` Jean-Francois Moine
2014-03-20 13:01 ` Jean-Francois Moine
2014-03-20 13:01 ` Jean-Francois Moine
2014-03-20 13:25 ` Jean-Francois Moine
2014-03-20 13:25 ` Jean-Francois Moine
2014-03-20 13:25 ` Jean-Francois Moine
2014-03-20 13:26 ` Russell King - ARM Linux
2014-03-20 13:26 ` Russell King - ARM Linux
2014-03-20 13:26 ` Russell King - ARM Linux
2014-03-20 13:32 ` Sebastian Hesselbarth
2014-03-20 13:32 ` Sebastian Hesselbarth
2014-03-20 13:52 ` Jean-Francois Moine
2014-03-20 13:52 ` Jean-Francois Moine
2014-03-20 13:52 ` Jean-Francois Moine
2014-03-20 14:19 ` Sebastian Hesselbarth
2014-03-20 14:19 ` Sebastian Hesselbarth
2014-03-20 14:19 ` Sebastian Hesselbarth
2014-03-20 14:31 ` Russell King - ARM Linux
2014-03-20 14:31 ` Russell King - ARM Linux
2014-03-20 14:31 ` Russell King - ARM Linux
2014-03-20 14:59 ` Jean-Francois Moine [this message]
2014-03-20 14:59 ` Jean-Francois Moine
2014-03-20 14:59 ` Jean-Francois Moine
2014-03-20 15:15 ` Robert Nelson
2014-03-20 15:15 ` Robert Nelson
2014-03-20 15:15 ` Robert Nelson
2014-03-20 15:19 ` Russell King - ARM Linux
2014-03-20 15:19 ` Russell King - ARM Linux
2014-03-20 15:19 ` Russell King - ARM Linux
2014-03-20 15:54 ` Jean-Francois Moine
2014-03-20 15:54 ` Jean-Francois Moine
2014-03-20 15:54 ` Jean-Francois Moine
2014-03-20 16:22 ` Russell King - ARM Linux
2014-03-20 16:22 ` Russell King - ARM Linux
2014-03-20 16:22 ` Russell King - ARM Linux
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=20140320155935.7a474173@armhf \
--to=moinejf@free.fr \
--cc=linux-arm-kernel@lists.infradead.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.