<div class="gmail_quote">On Sat, Nov 21, 2009 at 3:53 PM, Russell King - ARM Linux <span dir="ltr"><<a href="mailto:linux@arm.linux.org.uk">linux@arm.linux.org.uk</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On Fri, Nov 20, 2009 at 10:50:34AM +0000, Russell King - ARM Linux wrote:<br>
> -static int i2c_pnx_suspend(struct platform_device *pdev, pm_message_t state)<br>
> -{<br>
> - int retval = 0;<br>
> -#ifdef CONFIG_PM<br>
> - retval = set_clock_run(pdev);<br>
> -#endif<br>
<br>
</div>BTW, a comment from PNX folk (Vitaly/Kevin) would be appreciated. Why<br>
does PNX enable the clock when going into suspend? Should I assume that<br>
this should actually be disabling the clock?<br></blockquote><div><br>As far as I recall, at some point there was a function that was taking the second boolean parameter (enable or disable the clock). So now it is, yes, not making much sense.<br>
<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
Also, if Vitaly doesn't have anything to do with PNX4008 anymore, it<br>
would be a good idea to update the MAINTAINERS file.<br>
</blockquote></div><br>I'd like to keep maintaining this platform, but it's also up to NXP because I don't have the actual working hardware now so there's not much I can do.<br><br>Vitaly<br>