RE: Reg pinmux driver for OMAP based SoC- AM335X

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Tony,

On Tue, Jan 31, 2012 at 22:35:11, Tony Lindgren wrote:
> The plan is to deprecate the existing arch/arm/*omap*/*mux* code,
> and cut it down to minimum. And then add DT only mux support that should
> work for at least omap2+. That should work for am335x too.
> 
> There's currently some discussion going on regarding the pinmux device
> tree binding and how dynamic mux states should be handled. But I'd
> assume we'll have basic support available very soon.
> 
> The driver I'm working leaves all the data out of kernel, and the driver
> just knows how to handle a pinmux register instances. Then debugging
> tools can be done in userspace via debugfs to display more detailed
> SoC specific information.
> 
> So it might be worth waiting just a little bit longer. If you have
> resources to spend on the pinmuxing, then creating some userspace tool
> to display SoC specific information would be nice :) For the userspace
> tool, we can use the data in arch/arm/mach-omap2/mux*2*.[ch].

Thank you for the detailed reply.

I will wait for it and willing to help you in its testing.

I have been tasked on getting AM335X supported well in mainline,
and will move to other aspects of it while waiting.

Regards
Afzal
--
To unsubscribe from this list: send the line "unsubscribe linux-omap" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html


[Index of Archives]     [Linux Arm (vger)]     [ARM Kernel]     [ARM MSM]     [Linux Tegra]     [Linux WPAN Networking]     [Linux Wireless Networking]     [Maemo Users]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite Trails]     [Linux Kernel]     [Linux SCSI]

  Powered by Linux