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 16:54:40 +0100 [thread overview]
Message-ID: <20140320165440.195cd2ea@armhf> (raw)
In-Reply-To: <20140320151934.GV7528@n2100.arm.linux.org.uk>
On Thu, 20 Mar 2014 15:19:34 +0000
Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> I'm not saying that it has to match the physical device fitted - I'm
> merely suggesting not using nxp,tda1998x which could (and as Sebastian
> has found, does) conflict with other devices with different properties.
>
> We still auto-detect the exact device type by reading the ID register
> because that's the most reliable way to detect exactly what kind of
> device is fitted to the board.
I don't see the problem.
Actually the driver handles the tda9989, tda19988 and tda19989 (2
variants). If some board has, for example, the tda9983 and if the
driver is extended to handle this chip (i.e. mainly ignore the CEC
part), setting 'nxp,tda998x' in the associated DT will still work.
There could be a problem if somebody would write a specific driver for,
say, a tda9985. But, then, the compatible would be 'nxp,tda9985'.
--
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
next prev parent reply other threads:[~2014-03-20 15:54 UTC|newest]
Thread overview: 15+ 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
[not found] ` <20140320092639.48F68A6279-0zphjBnwxSw1Wri2s2gf/1AUjnlXr6A1@public.gmane.org>
2014-03-20 12:32 ` Sebastian Hesselbarth
2014-03-20 12:36 ` Russell King - ARM Linux
2014-03-20 13:01 ` Jean-Francois Moine
2014-03-20 13:25 ` Jean-Francois Moine
2014-03-20 13:26 ` Russell King - ARM Linux
2014-03-20 13:32 ` Sebastian Hesselbarth
2014-03-20 13:52 ` Jean-Francois Moine
2014-03-20 14:19 ` Sebastian Hesselbarth
2014-03-20 14:31 ` Russell King - ARM Linux
2014-03-20 14:59 ` Jean-Francois Moine
2014-03-20 15:15 ` Robert Nelson
2014-03-20 15:19 ` Russell King - ARM Linux
2014-03-20 15:54 ` Jean-Francois Moine [this message]
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=20140320165440.195cd2ea@armhf \
--to=moinejf@free.fr \
--cc=devicetree@vger.kernel.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=sebastian.hesselbarth@gmail.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).