From: Sebastian Andrzej Siewior <bigeasy-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
To: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
Nishanth Menon <nm-l0cyMroinI0@public.gmane.org>
Cc: Ben Hutchings
<ben.hutchings-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org>,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
CT kernel
<linux-kernel-81qHHgoATdFT9dQujB1mzip2UmYkHbXO@public.gmane.org>,
Grygorii Strashko
<grygorii.strashko-l0cyMroinI0@public.gmane.org>,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Roger Quadros <rogerq-l0cyMroinI0@public.gmane.org>
Subject: Re: [PATCH v2] ARM: dts: dra7xx: Fix compatible string for PCF8575 chip
Date: Wed, 13 Apr 2016 08:59:39 +0200 [thread overview]
Message-ID: <570DEE5B.1010001@linutronix.de> (raw)
In-Reply-To: <20160412210438.GA5995-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
On 04/12/2016 11:04 PM, Tony Lindgren wrote:
>> While at it, do you want to fix up (+Seb):
>> a) Documentation/devicetree/bindings/i2c/i2c-pxa-pci-ce4100.txt which
>> also seems to refer to ti,pcf in example (introduced by df2634f43f51
>> x86: dtb: Add a device tree for CE4100 )
>> b) arch/x86/platform/ce4100/falconfalls.dts as well?
>
> Applying this one with Roger's ack, seems like those should be
> additional patches.
Okay. I looked it up on the board and it says NXP PCF8575 and not TI.
TI's was probably the first hit while I was looking for it (I think
CE4100 manual mentioned just PCF8575).
But if it would have a TI branding on it I would keep the TI prefix in
front and add the NXP prefix. As of today we might not know a
functional difference between those two but this does not mean we might
find one in the future.
That said, are you people sure that the DRA7 has a TI or a NXP branding
on it?
>
> Tony
>
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
next prev parent reply other threads:[~2016-04-13 6:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-16 16:52 [PATCH v2] ARM: dts: dra7xx: Fix compatible string for PCF8575 chip Ben Hutchings
[not found] ` <1458147150.20441.2.camel-4yDnlxn2s6sWdaTGBSpHTA@public.gmane.org>
2016-03-16 22:31 ` Nishanth Menon
[not found] ` <56E9DED9.6020909-l0cyMroinI0@public.gmane.org>
2016-04-12 21:04 ` Tony Lindgren
[not found] ` <20160412210438.GA5995-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2016-04-13 6:59 ` Sebastian Andrzej Siewior [this message]
[not found] ` <570DEE5B.1010001-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
2016-04-13 7:11 ` Roger Quadros
[not found] ` <570DF110.3070805-l0cyMroinI0@public.gmane.org>
2016-04-13 7:16 ` Sebastian Andrzej Siewior
[not found] ` <570DF235.6040705-hfZtesqFncYOwBW4kG4KsQ@public.gmane.org>
2016-04-13 7:21 ` Roger Quadros
[not found] ` <570DF38C.8000600-l0cyMroinI0@public.gmane.org>
2016-04-13 15:17 ` Tony Lindgren
2016-03-18 8:47 ` Roger Quadros
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=570DEE5B.1010001@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-kernel-81qHHgoATdFT9dQujB1mzip2UmYkHbXO@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).