From: Sebastian Andrzej Siewior <bigeasy-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
To: Ben Hutchings
<ben.hutchings-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org>,
Roger Quadros <rogerq-l0cyMroinI0@public.gmane.org>
Cc: tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org,
nm-l0cyMroinI0@public.gmane.org,
grygorii.strashko-l0cyMroinI0@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] ARM: dts: dra7xx: Fix compatible string for PCF8575 chip
Date: Mon, 9 May 2016 08:49:29 +0200 [thread overview]
Message-ID: <573032F9.50604@linutronix.de> (raw)
In-Reply-To: <1462386203.2360.12.camel-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org>
On 05/04/2016 08:23 PM, Ben Hutchings wrote:
> On Mon, 2016-04-25 at 15:53 +0300, Roger Quadros wrote:
>> The boards use a TI variant of the PCF8575 so specify that
>> in the compatible string.
>>
>> Signed-off-by: Roger Quadros <rogerq-l0cyMroinI0@public.gmane.org>
> [...]
>
> 1. This compatible string is still not documented (AFAIK).
> 2. As I understand it, TI is a second source for this NXP-designed chip,
> i.e. it manufactures chips with identical logic (not clones) under
> license. They should not be distinguishable in software.
Mistakes don't happen on purpose.
> 3. For the same reason, there is no guarantee that the board
> manufacturer won't populate boards with PCF8575 chips from the other
> source in future.
If it is a redesign it is likely that they replace more than just one
part.
>
> Ben.
>
Sebastian
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2016-05-09 6:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-25 12:53 [PATCH] ARM: dts: dra7xx: Fix compatible string for PCF8575 chip Roger Quadros
[not found] ` <1461588834-20908-1-git-send-email-rogerq-l0cyMroinI0@public.gmane.org>
2016-04-26 17:09 ` Tony Lindgren
2016-05-04 18:23 ` Ben Hutchings
[not found] ` <1462386203.2360.12.camel-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org>
2016-05-09 6:49 ` Sebastian Andrzej Siewior [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=573032F9.50604@linutronix.de \
--to=bigeasy-hfztesqfncyowbw4kg4ksq@public.gmane.org \
--cc=ben.hutchings-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=grygorii.strashko-l0cyMroinI0@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=nm-l0cyMroinI0@public.gmane.org \
--cc=rogerq-l0cyMroinI0@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.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 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).