From: Roland Stigge <stigge@antcom.de>
To: Kevin Wells <kevin.wells@nxp.com>
Cc: Wolfram Sang <w.sang@pengutronix.de>,
"vitalywool@gmail.com" <vitalywool@gmail.com>,
"khali@linux-fr.org" <khali@linux-fr.org>,
"ben-linux@fluff.org" <ben-linux@fluff.org>,
"grant.likely@secretlab.ca" <grant.likely@secretlab.ca>,
"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Srinivas Bakki <srinivas.bakki@nxp.com>,
"aletes.xgr@gmail.com" <aletes.xgr@gmail.com>,
"jonsmirl@gmail.com" <jonsmirl@gmail.com>,
linux-arm-kernel@lists.infradead.org, arm@kernel.org,
Russell King <linux@arm.linux.org.uk>
Subject: Re: [PATCH RESEND 1/2] i2c: pnx: Fix bit definitions
Date: Mon, 20 Aug 2012 18:47:58 +0200 [thread overview]
Message-ID: <50326A3E.9070607@antcom.de> (raw)
In-Reply-To: <083DF309106F364B939360100EC290F823A0354A3D@eu1rdcrdc1wx030.exi.nxp.com>
On 08/20/2012 06:26 PM, Kevin Wells wrote:
>>>> This patch for i2c-pnx affects PNX4008 and LPC32xx (and LPC31xx,
>>>> not yet in mainline). Can you please test and double-check the
>>>> manuals of PNX4008 and LPC31xx? I only found this via the manual
>>>> of LPC32xx but assume it's the same for the others, also.
>>>>
>>>> Thanks in advance!
>>>
>>> Kevin, since the other manuals seem to be not easily available, can
>>> you please check?
>>
>> Yes, would be great if someone at NXP could confirm that PNX actually
>> uses the same IP core for the I2C controller as LPCs do (which is
>> currently assumed by Linux anyway).
>
> I've never had my hands on a PNX4008 chip at NXP, but I do believe they
> are the same IP. That specific I2C IP was used in a number of NXP/Phillips
> chips besides the PNX4008/LPC32xx. I don't think there are any PNX4008's in
> the wild, and even working in NXP, I can't find any non-marketing reference
> material for that part (including the user manual).
Considering this, it might be a good idea to remove support for PNX4008
(arch/arm/mach-pnx4008/) altogether. It's hard to maintain support for
hardware which isn't available, even at NXP. It would also simplify
maintenance of mach-lpc32xx because the overlap currently makes me
always wonder if the respective changes still work with mach-pnx4008.
Any opposition?
Roland
PS: I just wonder how mach-pnx4008 came into the kernel at all...
next prev parent reply other threads:[~2012-08-20 16:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-08 7:42 Roland Stigge
2012-08-08 7:42 ` [PATCH RESEND 2/2] i2c: pnx: Fix read transactions of >= 2 bytes Roland Stigge
2012-08-18 9:52 ` Wolfram Sang
2012-08-19 8:45 ` Roland Stigge
2012-08-18 9:51 ` [PATCH RESEND 1/2] i2c: pnx: Fix bit definitions Wolfram Sang
2012-08-19 8:47 ` Roland Stigge
2012-08-20 16:26 ` Kevin Wells
2012-08-20 16:47 ` Roland Stigge [this message]
2012-08-20 19:49 ` Arnd Bergmann
2012-08-20 17:55 ` Wolfram Sang
2012-08-20 20:47 ` Roland Stigge
2012-09-03 20:16 ` Roland Stigge
2012-09-04 9:20 ` Wolfram Sang
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=50326A3E.9070607@antcom.de \
--to=stigge@antcom.de \
--cc=aletes.xgr@gmail.com \
--cc=arm@kernel.org \
--cc=ben-linux@fluff.org \
--cc=grant.likely@secretlab.ca \
--cc=jonsmirl@gmail.com \
--cc=kevin.wells@nxp.com \
--cc=khali@linux-fr.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=srinivas.bakki@nxp.com \
--cc=vitalywool@gmail.com \
--cc=w.sang@pengutronix.de \
/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
Powered by JetHome