On Thursday 19 December 2013 02:26 AM, Stephen Warren wrote:
On 12/18/2013 05:52 AM, Laxman Dewangan wrote:
Compare the initial population of default pinmux configuration of Venice2
with the chrome branch and add/fix the missing configurations.
Wow, that's a big chunk of changes. Are you sure this is correct? Why
was the original patch (which added the pinctrl nodes) so incorrect?
The pinmux which got added is based on the venice2 pinmux spreadsheet
where I covered only the SFIO pin groups.
https://wiki.nvidia.com/engwiki/index.php/Platform_Design_Center/Projects_Archive/PM371#pinmux
After comparing with the chrome, I also added the pinmux for all pins
which are used as GPIO and hence the change is big.
This is complete pinmux based on chrome kernel-next.
I booted chrome with this pinmux and not observe any behavioral change.
Thierry, I thought you had mentioned comparing the pinctrl setup in
linux-next with the downstream kernel for Venice2 and only found a
difference in the PWM settings, which you sent a patch for. However,
this patch is much larger than that. Where's the disconnect?
--
To unsubscribe from this list: send the line "unsubscribe linux-tegra" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
