[U-Boot] RFC Pin Configuration Device Tree Bindings for Altera Arria10 SOCFPGA

Marek Vasut marex at denx.de
Tue Dec 16 20:39:11 CET 2014


On Thursday, December 04, 2014 at 11:08:32 PM, mgerlach wrote:
> On Wed, 3 Dec 2014, Pavel Machek wrote:
> > Hi!
> > 
> > > >>>         altr,pinmux-regs = <0xF 0xF 0xF 0xF 0xF 0xF 0xF 0xF 0xF 0xF
> > > >>>         reg = <0xffd07300 0x00000048>;
> > > >>>         altr,pinmux-regs = <0x00000 0x51010 0x51010 0x51010 0x40605
> > > >>>         
> > > >>>                    0x40605 0x00605 0x40605 0x40605 0x40605
> > > >>>                    0x10605 0x51010 0x51010 0x51010 0x51010
> > > >>>                    0x51010 0x03030 0x23030>;
> > > >>>     
> > > >>>     };
> > > >>>     fpga {
> > > >>>     
> > > >>>         reg = <0xffd07400 0x00000044>;
> > > >>>         altr,pinmux-regs = <0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0 0x0
> > > >>>         
> > > >>>                    0x0 0x0 0x0 0x0 0x0 0x0 0x0>;
> > > >>>     
> > > >>>     };
> > > >>> 
> > > >>> };
> > > >>
> > > >>Does this match the kernel? Or does the kernel have no such binding
> > > >>yet?
> > > >>
> > > > There are no such bindings in the kernel yet.  Dynamic pinmuxing is
> > > > not supported by the Arria 10; so we don't anticipate the kernel
> > > > needing pinmux information.
> > > 
> > > OK. Currently device tree files are stored in the kernel, so it might
> > > be worth submitting it there one day regardless.
> > 
> > Actually, I believe you should use standard pinmux format. Just
> > because dynamic pinmuxing is not supported now does not mean it will
> > not be supported in Arria 11... And it was already supported in older
> > chipsets (right?).
> > 
> > 									Pavel
> 
> Hi Pavel,
> 
> Thanks for the suggestion.  I had another look at the pinctlr bindings
> in the kernel.  I think we should be using standard bindings defined in
> Documentation/devicetree/bindings/pinctrl/pinctrl-single.txt for
> the Arria 10 SOCFPGA.

Thanks for letting me know about the discussion today.

As for the SPL, we agreed that the SPL should parse the DT and do the 
configuration from the DT. The DT for the SPL might be stripped down
in case there was a problem with fitting the full-size DT into the memory.

As for the DT bindings (in general), these should go to the DT mailing list,
see http://elinux.org/Device_Tree#Device-tree_Mailing_List . By running those
bindings against the DT ML, you will get some kind of a guarantee that their
design is sound and these bindings will be somewhat future-proof.

Best regards,
Marek Vasut


More information about the U-Boot mailing list