Re: [CORRECTED] I2C driver supporting Moorestown and Medfield platform

2010-08-31 Thread Ben Dooks
On Mon, Aug 09, 2010 at 01:23:45PM +0100, Alan Cox wrote: I would much prefer this to be called i2c-moorsetown, we have modern systems which can handle 8 character names. Moorestown. Everything else in the kernel uses 'mrst' so this would make the driver differ from the rest of the tree. I

Re: [CORRECTED] I2C driver supporting Moorestown and Medfield platform

2010-08-09 Thread Ben Dooks
On 03/08/10 15:34, Alan Cox wrote: (And the correct patch attached this time) From: Wen Wang wen.w.w...@intel.com Initial release of the driver. Updated and verified on hardware. Cleaned up as follows Alan Cox: Squash down the switches into tables, and use the PCI ident field. We

Re: [CORRECTED] I2C driver supporting Moorestown and Medfield platform

2010-08-09 Thread Alan Cox
I would much prefer this to be called i2c-moorsetown, we have modern systems which can handle 8 character names. Moorestown. Everything else in the kernel uses 'mrst' so this would make the driver differ from the rest of the tree. I don't care too much what its called. Given its now for

Re: [CORRECTED] I2C driver supporting Moorestown and Medfield platform

2010-08-09 Thread Shinya Kuribayashi
On 8/9/2010 8:07 PM, Alan Cox wrote: There are various little differences along with the PCI, power management, timing and configuration side. I've also looked at the two I'm interested in those little diffs. side by side and agreed with the original Intel authors that it seemed best to keep

[CORRECTED] I2C driver supporting Moorestown and Medfield platform

2010-08-03 Thread Alan Cox
(And the correct patch attached this time) From: Wen Wang wen.w.w...@intel.com Initial release of the driver. Updated and verified on hardware. Cleaned up as follows Alan Cox: Squash down the switches into tables, and use the PCI ident field. We could perhaps take this further and put