From: Matthew Gerlach <mgerlach@opensource.altera.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] RFC Pin Configuration Device Tree Bindings for Altera Arria10 SOCFPGA
Date: Sat, 29 Nov 2014 18:20:13 +0000 [thread overview]
Message-ID: <1417285212343.65836@opensource.altera.com> (raw)
Altera Arria10 SOCFPGA Pin Configuration Bindings
This document describes device tree bindings required to perform configuration
of the pins for an Altera Arria10 SOCFPGA . The bindings are intended to
be compact and easy to be consumed only by a SPL running in a small on-chip
ram before external memory is available. The Arria10 SOCFPGA does not support
dynamic modification of the pin configuration.
Each set of pins is represented by its own subnode. For each subnode, the
altr,pinmux-regs data will be written to sequential 32 bit addresses starting
at the address in the reg property.
Required properties:
- compatible : Must be "altr,arria10-pinmux" for Arria10 SOCFPGA
- one subnode for each set of pins to be configured
Required subnode properties:
- reg : The start address to write pinmux-data as 32 bit quantities and the
number of bytes of registers to be written.
- altr,pinmux-regs : Pin configuration data to be written to registers
Example:
pinmux at 0xffd07000 {
#address-cells = <1>;
#size-cells = <0>;
compatible = "altr,arria10-pinmux";
shared {
reg = <0xffd07000 0x000000c0>;
altr,pinmux-regs = <0xF 0xF 0xF 0xF 0xF 0xF 0xF 0xF 0xF 0xF
0xF 0xF 0xF 0xF 0xF 0xF 0xF 0xF 0xF 0xF
0xD 0xD 0xD 0xD 0xD 0xD 0xD 0xD 0xF 0xF
0xF 0xF 0xF 0xF 0xF 0xF 0xF 0xF 0xF 0xF
0xF 0xF 0xF 0xF 0xF 0xF 0xF 0xF>;
};
dedicated {
reg = <0xffd07200 0x00000044>;
altr,pinmux-regs = <0x0 0x0 0x0 0x8 0x8 0x8 0x8 0x8 0x8 0x8
0xF 0xF 0xF 0xF 0xF 0xD 0xD>;
};
dedicated_cfg {
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>;
};
};
next reply other threads:[~2014-11-29 18:20 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-29 18:20 Matthew Gerlach [this message]
2014-12-03 14:48 ` [U-Boot] RFC Pin Configuration Device Tree Bindings for Altera Arria10 SOCFPGA Pavel Machek
2014-12-03 17:36 ` Simon Glass
2014-12-03 17:45 ` Dinh Nguyen
2014-12-03 17:49 ` Matthew Gerlach
2014-12-03 19:00 ` Simon Glass
2014-12-03 20:36 ` Pavel Machek
2014-12-04 22:08 ` mgerlach
2014-12-16 19:39 ` Marek Vasut
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1417285212343.65836@opensource.altera.com \
--to=mgerlach@opensource.altera.com \
--cc=u-boot@lists.denx.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox