On 1/11/2012 2:29 PM, Paul Walmsley wrote:

On Wed, 11 Jan 2012, Shubhrajyoti wrote:

quoted

On Tuesday 10 January 2012 08:56 PM, Kevin Hilman wrote:

quoted

"Datta, Shubhrajyoti"[off-list ref]  writes:

quoted

On Tue, Jan 10, 2012 at 11:53 AM, Datta, Shubhrajyoti
[off-list ref]  wrote:

quoted

On Fri, Dec 16, 2011 at 2:29 PM, Shubhrajyoti[off-list ref]  wrote:

quoted

On Friday 16 December 2011 02:10 PM, Paul Walmsley wrote:

quoted

This patch either needs to be acked by Ben with a note that it's okay for
us to merge through the OMAP tree, or needs to be merged by Ben during the
3.4 merge window, after patches 1-3 have reached the mainline tree.

I agree.
Ben do you have any comments .

If there are no further comments can this be merged also ?

As Benoit mentioned earlier, the addition of new pdata fields will cause
problems with the DT support already queued for v3.3.

This series should be reworked on top of the DT support which Ben has
now queued for v3.3 (my branch: for_3.3/i2c/misc)

Yes will rework it.

Depending on what you plan to do, you'll probably need to coordinate this
with Tony also.  He's already pulled some of the patches from this series
into his i2c branch.

The real question is how you plan to handle the device reset function,
given that the driver should compile on a non-OMAP build (meaning that you
can't call omap_device*() functions from the driver directly), nor should
the driver touch the SYSCONFIG register directly.

Something that puzzle me on that point is most architecture does not use 
plateform_device and thus does not have any pdata to hack some custom 
function pointers here an there.
It means that there is probably some better solution to handle that.

AFAIU, the way PPC is handling that is by splitting the driver in a 
generic part and in a platform specific part.

You can then add any OMAP specific hacks in the OMAP specific part while 
keeping most of generic code in a generic driver.

In this case, we just have to implement a small shim that will handle 
the OMAP specific code for the reset. The generic driver will handle the 
rest.

Maybe I'm missing some important details, but that does seems easily 
doable for the i2c case.

Regards,
Benoit