[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAL_Jsq+8_O483raD97B8-ssaFGeVOPJcadyY4x7m0T64EbVA3g@mail.gmail.com>
Date: Tue, 29 Nov 2016 09:20:17 -0600
From: Rob Herring <robh+dt@...nel.org>
To: Lee Jones <lee.jones@...aro.org>
Cc: Tony Lindgren <tony@...mide.com>,
Samuel Ortiz <sameo@...ux.intel.com>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
linux-omap <linux-omap@...r.kernel.org>,
"devicetree@...r.kernel.org" <devicetree@...r.kernel.org>,
Marcel Partap <mpartap@....net>,
Mark Rutland <mark.rutland@....com>,
Michael Scott <michael.scott@...aro.org>
Subject: Re: [PATCH] mfd: cpcap: Add minimal support
On Thu, Nov 24, 2016 at 2:59 AM, Lee Jones <lee.jones@...aro.org> wrote:
> On Wed, 23 Nov 2016, Tony Lindgren wrote:
>
>> * Lee Jones <lee.jones@...aro.org> [161121 03:43]:
>> > On Fri, 18 Nov 2016, Tony Lindgren wrote:
>> > > --- a/drivers/mfd/Makefile
>> > > +++ b/drivers/mfd/Makefile
>> > > @@ -97,6 +97,7 @@ obj-$(CONFIG_MFD_MC13XXX_I2C) += mc13xxx-i2c.o
>> > > obj-$(CONFIG_MFD_CORE) += mfd-core.o
>> > >
>> > > obj-$(CONFIG_EZX_PCAP) += ezx-pcap.o
>> > > +obj-$(CONFIG_MFD_CPCAP) += cpcap.o
>> >
>> > Who is the manufacturer?
>>
>> Hmm that I don't know. There seems to be both ST and TI versions
>> of this chip manufactured for Motorola. So my guess is that it
>> should be Motorola unless there's some similar catalog part
>> available from ST used by others. If anybody has more info
>> on this please let me know :)
>
> If this IP is shared amongst vendors, it usually means it was designed
> by someone else? Synopsis perhaps?
xCAP names originated from Motorola cellular group with parts (going
back to analog/2G days) coming from Motorola Semi, TI, and ST it
seems. All individually developed AFAIK.
Rob
Powered by blists - more mailing lists