Hi Andre,
On Fri, Feb 05, 2016 at 10:04:01AM +0000, Andre Przywara wrote:
> >> +&uart0 {
> >> + pinctrl-names = "default";
> >> + pinctrl-0 = <&uart0_pins_a>;
> >> + status = "okay";
> >> +};
> >> +
> >> +&uart2 {
> >> + pinctrl-names = "default";
> >> + pinctrl-0 = <&uart2_pins>;
> >> + status = "okay";
> >> +};
> >> +
> >> +&uart3 {
> >> + pinctrl-names = "default";
> >> + pinctrl-0 = <&uart3_pins_a>;
> >> + status = "okay";
> >> +};
> >> +
> >> +&uart4 {
> >> + pinctrl-names = "default";
> >> + pinctrl-0 = <&uart4_pins>;
> >> + status = "okay";
> >> +};
> >
> > Our policy for boards with "open" pin headers the user can plug
> > anything he wants is that unless the pin is explicitly dedicated to
> > that usage, we simply leave them aside so that we don't enforce
> > anything.
>
> Makes sense, I just wonder what a user is expected to do if she wants to
> use the serial ports?
> Hack the DT?
> Use U-Boot to create those nodes on the fly?
> Use overlays?
> Directly setup serial ports from userland? (thinking of this bloody
> mechanism x86 (used to?) have)Until we have a configfs overlay interface, then yeah, we have to hack the DT. That's not very much different than what you'd have to do if you wanted some other bus exposed on those pins though. Thanks! Maxime -- Maxime Ripard, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com -- You received this message because you are subscribed to the Google Groups "linux-sunxi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
signature.asc
Description: Digital signature
