From: Arnd Bergmann <arnd@arndb.de>
To: Ley Foon Tan <lftan@altera.com>
Cc: Linux-Arch <linux-arch@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
cltang@codesourcery.com
Subject: Re: [PATCH 19/28] nios2: Device tree support
Date: Wed, 23 Apr 2014 09:35:32 +0200 [thread overview]
Message-ID: <5432420.laaqgJK4HL@wuerfel> (raw)
In-Reply-To: <CAFiDJ588Gr0yNBT2jSgDAo+SY-e-xCB5Rs4uS5ZNeskqasgNpA@mail.gmail.com>
On Wednesday 23 April 2014 14:52:47 Ley Foon Tan wrote:
> On Tue, Apr 22, 2014 at 9:42 PM, Arnd Bergmann <arnd@arndb.de> wrote:
> > On Friday 18 April 2014, Ley Foon Tan wrote:
> >> diff --git a/arch/nios2/boot/dts/3c120_devboard.dts b/arch/nios2/boot/dts/3c120_devboard.dts
>
> >> +/dts-v1/;
> >> +
> >> +/ {
> >> + model = "ALTR,qsys_ghrd_3c120";
> >> + compatible = "ALTR,qsys_ghrd_3c120";
> >
> > You have a mix of "ALTR" and "altr" prefixes. The general recommendation
> > is to use lower-case letters, which is also what is used on ARM socfpga,
> > and what is documented in Documentation/devicetree/bindings/vendor-prefixes.txt
> > for Altera.
> Yes, the vendor prefix should be changed to lower case. FYI, this dts
> file is generated by our dts generator tool called sopc2dts.
> Our tool already aware of this requirement, but haven't support this yet.
> I can edit this file manually to change 'ALTR' to 'altr', but I will
> update nios2 code to match for both "ALTR" and "altr" for backward
> compatibility. "ALTR" will be deprecated later. Are you okay with
> this?
You seem to have a large number of "ALTR" strings at the moment.
I don't think it would be good to allow matching both variants
everywhere, that would be a lot of extra code.
If it's only about the root compatible property, I have no objections,
but I don't know if it will help you when all the other strings don't
match.
> >> + sopc@0 {
> >> + device_type = "soc";
> >> + ranges;
> >> + #address-cells = < 1 >;
> >> + #size-cells = < 1 >;
> >> + compatible = "ALTR,avalon", "simple-bus";
> >> + bus-frequency = < 125000000 >;
> >> +
> >> + pb_cpu_to_io: bridge@0x8000000 {
> >> + compatible = "simple-bus";
> >> + reg = < 0x08000000 0x00800000 >;
> >
> > Are these all synthesized devices, or is there also some hardwired
> > logic? It often makes sense to split out the reusable parts into
> > a separate .dtsi file that gets included by every implementation.
> All these are synthesized devices and the system hierarchy is also not
> fixed and it is depends on user hardware design. It is highly
> configurable.
> So, we can't have a common .dtsi file.
Ok, I see.
> >> + #address-cells = < 1 >;
> >> + #size-cells = < 1 >;
> >> + ranges = < 0x00400000 0x08400000 0x00000020
> >> + 0x00004D40 0x08004D40 0x00000008
> >> + 0x00004D50 0x08004D50 0x00000008
> >> + 0x00004000 0x08004000 0x00000400
> >> + 0x00004400 0x08004400 0x00000040
> >> + 0x00004800 0x08004800 0x00000040
> >> + 0x00002000 0x08002000 0x00002000
> >> + 0x00004C80 0x08004C80 0x00000020
> >> + 0x00004CC0 0x08004CC0 0x00000010
> >> + 0x00004CE0 0x08004CE0 0x00000010
> >> + 0x00004D00 0x08004D00 0x00000010 >;
> >
> > - The ranges should reflect what the bus actually translates,
> > which is typically not individual bytes but rather whole
> > address ranges.
> The ranges here reflect the address range translate by each device and
> user can assign any base address they desired in our FPGA. The address
> ranges might not in continuous regions as well. So, we will keep this
> translation way.
If you can support any address, why not just have an empty 'ranges'
property?
> >> + timer_1ms: timer@0x400000 {
> >> + compatible = "ALTR,timer-1.0";
> >> +
> >> + sysid: sysid@0x4d40 {
> >> + compatible = "ALTR,sysid-1.0";
> >> + reg = < 0x00004D40 0x00000008 >;
> >
> >> + jtag_uart: serial@0x4d50 {
> >> + compatible = "ALTR,juart-1.0";
> >> + reg = < 0x00004D50 0x00000008 >;
> >> +
> >> + tse_mac: ethernet@0x4000 {
> >> + compatible = "ALTR,tse-1.0";
> >
> >
> > Does each one of these have a binding document in
> > Documentation/devicetree/bindings?
> jtag_uart and tse drivers are upstreamed. They already have their own
> bindings doc:
> Documentation/devicetree/bindings/serial/altera_jtaguart.txt
> Documentation/devicetree/bindings/net/altera_tse.txt
>
> I will add the binding doc for timer, but sysid driver is not in
> mainline kernel yet. I will remove sysid entry from this file.
Ok. BTW, could the sysid be used for the soc device strings, or
is that something else?
> >> + reg = < 0x00004000 0x00000400
> >> + 0x00004400 0x00000040
> >> + 0x00004800 0x00000040
> >> + 0x00002000 0x00002000 >;
> >> + reg-names = "control_port", "rx_csr", "tx_csr", "s1";
> >
> > - wrong order, missing "tx_desc" and "rx_desc" entries
> FYI, TSE driver supports both SGDMA and MSGDMA soft IP and "tx_desc"
> and "rx_desc" entries are for MSGDMA (see below). But this 3c120
> hardware design is using TSE + SGDMA. So, the expect entries are
> "control_port", "rx_csr", "tx_csr", "s1".
> I can sort the entries order by their addresses.
You can't reorder the registers, as they can be accessed by
index in some OS, the strings are just annotations really.
> Excerpt from Documentation/devicetree/bindings/net/altera_tse.txt
> - reg-names: Should contain the reg names
> "control_port": MAC configuration space region
> "tx_csr": xDMA Tx dispatcher control and status space region
> "tx_desc": MSGDMA Tx dispatcher descriptor space region
> "rx_csr" : xDMA Rx dispatcher control and status space region
> "rx_desc": MSGDMA Rx dispatcher descriptor space region
> "rx_resp": MSGDMA Rx dispatcher response space region
> "s1": SGDMA descriptor memory
The important part is
- reg: Address and length of the register set for the device. It contains
the information of registers in the same order as described by reg-names.
You can either provide dummy entries for tx_desc, rx_desc and rx_resp,
or change the binding to reflect the current usage, and provide two
different lists depending on the compatible string.
> >> + max-frame-size = < 1518 >;
> >> + local-mac-address = [ 02 00 00 00 00 00 ];
> >> + phy-mode = "rgmii-id";
> >> + ALTR,mii-id = < 0 >;
> >
> > ALTR,mii-id is not documented, and required "phy-addr" is missing.
> Will remove ALTR,mii-id. "phy-addr" is not required if we provide "phy-handle".
>
> Excerpt from Documentation/devicetree/bindings/net/altera_tse.txt:
> - phy-addr: See ethernet.txt in the same directory. A configuration should
> include phy-handle or phy-addr.
Ok.
> >> diff --git a/arch/nios2/boot/linked_dtb.S b/arch/nios2/boot/linked_dtb.S
> >> new file mode 100644
> >> index 0000000..071f922db338e2cb4064bc77bf346f50e584d04f
> >> --- /dev/null
> >> +++ b/arch/nios2/boot/linked_dtb.S
> >> + */
> >> +.section .dtb.init.rodata,"a"
> >> +.incbin "arch/nios2/boot/system.dtb"
> >
> > Linking in the dtb file is really against the point of device trees.
> > You should require boot loaders to pass the dtb seperately.
> We do support pass the dtb from boot loaders. This is optional feature
> that allow user to linking in dtb into kernel image if
> CONFIG_DTB_SOURCE_BOOL is enabled. This is very useful for develpment
> stage/debugging stage, where we can download vmlinux image directly
> into SDRAM and boot without boot loader.
> Noticed that other architectures have linking in dtd file as well, eg:
> c6x and microblaze.
Ok.
Arnd
next prev parent reply other threads:[~2014-04-23 7:35 UTC|newest]
Thread overview: 126+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 12:26 [PATCH 00/28] nios2 Linux kernel port Ley Foon Tan
2014-04-18 12:26 ` [PATCH 01/28] nios2: Build infrastructure Ley Foon Tan
2014-04-18 14:35 ` Sam Ravnborg
2014-04-21 3:03 ` Ley Foon Tan
2014-04-18 19:16 ` Paul Bolle
2014-04-21 5:02 ` Ley Foon Tan
2014-04-18 19:41 ` Paul Bolle
2014-04-21 3:26 ` Ley Foon Tan
2014-04-18 12:26 ` [PATCH 02/28] nios2: Assembly macros and definitions Ley Foon Tan
2014-04-18 12:26 ` [PATCH 04/28] nios2: Exception handling Ley Foon Tan
2014-04-22 10:57 ` Ezequiel Garcia
2014-04-22 11:08 ` Ley Foon Tan
2014-04-22 12:33 ` Arnd Bergmann
2014-04-23 2:47 ` Ley Foon Tan
2014-04-23 7:20 ` Geert Uytterhoeven
2014-04-23 12:23 ` Arnd Bergmann
2014-04-24 6:04 ` Ley Foon Tan
2014-04-18 12:26 ` [PATCH 06/28] nios2: Memory management Ley Foon Tan
2014-04-22 14:24 ` Ezequiel Garcia
2014-04-22 15:14 ` Tobias Klauser
2014-04-22 15:35 ` Ezequiel Garcia
2014-04-22 16:01 ` Chung-Lin Tang
2014-04-22 16:27 ` Ezequiel Garcia
2014-04-22 16:36 ` Chung-Lin Tang
2014-04-22 16:24 ` Sam Ravnborg
2014-04-23 2:53 ` LF.Tan
2014-04-23 7:24 ` Geert Uytterhoeven
2014-04-18 12:26 ` [PATCH 08/28] nios2: MMU Fault handling Ley Foon Tan
2014-04-22 14:30 ` Ezequiel Garcia
2014-04-24 6:42 ` Ley Foon Tan
2014-04-24 15:22 ` Ezequiel Garcia
2014-04-24 16:02 ` Ley Foon Tan
2014-04-24 16:18 ` Ezequiel Garcia
2014-04-24 7:18 ` Geert Uytterhoeven
2014-04-18 12:26 ` [PATCH 09/28] nios2: Page table management Ley Foon Tan
2014-04-19 16:05 ` Pavel Machek
2014-04-22 8:09 ` Ley Foon Tan
2014-04-18 12:26 ` [PATCH 10/28] nios2: Process management Ley Foon Tan
2014-04-18 12:26 ` [PATCH 11/28] nios2: Cache handling Ley Foon Tan
2014-04-18 12:26 ` [PATCH 12/28] nios2: TLB handling Ley Foon Tan
2014-04-18 12:26 ` [PATCH 13/28] nios2: Interrupt handling Ley Foon Tan
2014-04-18 12:26 ` [PATCH 15/28] nios2: ELF definitions Ley Foon Tan
2014-04-18 12:26 ` [PATCH 16/28] nios2: System calls handling Ley Foon Tan
2014-04-19 16:09 ` Pavel Machek
2014-04-21 17:32 ` Ley Foon Tan
2014-04-21 17:52 ` Richard Weinberger
2014-04-21 20:48 ` Pavel Machek
2014-04-22 8:24 ` Ley Foon Tan
2014-04-21 20:46 ` Pavel Machek
2014-04-19 20:12 ` Geert Uytterhoeven
2014-04-21 17:23 ` Ley Foon Tan
2014-04-22 12:30 ` Arnd Bergmann
2014-04-24 16:23 ` Ley Foon Tan
2014-04-18 12:27 ` [PATCH 17/28] nios2: Signal handling support Ley Foon Tan
2014-04-19 19:29 ` Richard Weinberger
2014-04-24 10:01 ` Ley Foon Tan
2014-04-24 10:07 ` Richard Weinberger
2014-04-24 10:13 ` Ley Foon Tan
2014-04-24 10:17 ` Richard Weinberger
2014-04-24 10:29 ` Ley Foon Tan
2014-04-24 10:39 ` Richard Weinberger
2014-04-24 10:46 ` Ley Foon Tan
2014-04-24 16:16 ` Richard Weinberger
2014-04-18 12:27 ` [PATCH 18/28] nios2: Library functions Ley Foon Tan
2014-04-18 12:27 ` [PATCH 19/28] nios2: Device tree support Ley Foon Tan
2014-04-22 13:42 ` Arnd Bergmann
2014-04-23 6:52 ` Ley Foon Tan
2014-04-23 7:35 ` Arnd Bergmann [this message]
2014-04-23 9:52 ` Ley Foon Tan
2014-04-24 16:05 ` Ezequiel Garcia
2014-04-18 12:27 ` [PATCH 20/28] nios2: Time keeping Ley Foon Tan
2014-04-22 13:44 ` Arnd Bergmann
2014-04-23 3:21 ` Ley Foon Tan
2014-04-18 12:27 ` [PATCH 21/28] nios2: Cpuinfo handling Ley Foon Tan
2014-04-18 12:27 ` [PATCH 22/28] nios2: Miscellaneous header files Ley Foon Tan
2014-04-18 12:27 ` [PATCH 23/28] nios2: Nios2 registers Ley Foon Tan
2014-04-22 12:39 ` Tobias Klauser
2014-04-23 7:10 ` Ley Foon Tan
2014-04-23 8:00 ` Tobias Klauser
2014-04-18 12:27 ` [PATCH 24/28] nios2: Module support Ley Foon Tan
2014-04-18 12:27 ` [PATCH 25/28] nios2: ptrace support Ley Foon Tan
2014-04-25 23:52 ` Pedro Alves
2014-04-28 6:03 ` Ley Foon Tan
2014-04-18 12:27 ` [PATCH 26/28] Add ELF machine define for Nios2 Ley Foon Tan
2014-04-18 12:27 ` [PATCH 27/28] MAINTAINERS: Add nios2 maintainer Ley Foon Tan
2014-04-18 12:27 ` [PATCH 28/28] Documentation: Add documentation for Nios2 architecture Ley Foon Tan
2014-04-22 12:28 ` Tobias Klauser
2014-04-23 7:48 ` Ley Foon Tan
2014-04-18 18:19 ` [PATCH 03/28] nios2: Kernel booting and initialization Ley Foon Tan
2014-04-18 18:19 ` [PATCH 05/28] nios2: Traps exception handling Ley Foon Tan
2014-04-22 14:28 ` Ezequiel Garcia
2014-04-23 10:07 ` Ley Foon Tan
2014-04-18 18:19 ` [PATCH 07/28] nios2: I/O Mapping Ley Foon Tan
2014-04-22 13:59 ` Arnd Bergmann
2014-04-24 6:02 ` Ley Foon Tan
2014-04-24 7:43 ` Arnd Bergmann
2014-04-24 15:51 ` Ley Foon Tan
2014-05-02 10:37 ` Ley Foon Tan
2014-05-02 12:22 ` Arnd Bergmann
2014-05-05 7:13 ` Ley Foon Tan
2014-04-18 18:19 ` [PATCH 14/28] nios2: DMA mapping API Ley Foon Tan
2014-04-22 13:52 ` Arnd Bergmann
2014-04-25 10:13 ` Ley Foon Tan
2014-04-25 10:33 ` Arnd Bergmann
2014-04-25 10:36 ` Ley Foon Tan
2014-04-18 20:48 ` [PATCH 00/28] nios2 Linux kernel port H. Peter Anvin
2014-04-19 15:30 ` Arnd Bergmann
2014-04-21 5:23 ` Ley Foon Tan
2014-04-21 5:31 ` H. Peter Anvin
2014-04-21 8:14 ` Chung-Lin Tang
2014-04-22 10:37 ` Ley Foon Tan
2014-04-22 10:56 ` Arnd Bergmann
2014-04-22 11:20 ` Ley Foon Tan
2014-04-22 14:48 ` Chung-Lin Tang
2014-04-23 17:59 ` Chung-Lin Tang
2014-04-23 18:15 ` Pinski, Andrew
2014-04-23 19:21 ` H. Peter Anvin
2014-04-24 6:26 ` Chung-Lin Tang
2014-04-24 8:55 ` Chung-Lin Tang
2014-04-24 15:28 ` Catalin Marinas
2014-04-24 18:37 ` Chung-Lin Tang
2014-04-24 18:42 ` Pinski, Andrew
2014-04-25 6:06 ` Chung-Lin Tang
2014-04-25 8:37 ` Pinski, Andrew
2014-04-25 13:19 ` Chung-Lin Tang
2014-04-25 8:49 ` Geert Uytterhoeven
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=5432420.laaqgJK4HL@wuerfel \
--to=arnd@arndb.de \
--cc=cltang@codesourcery.com \
--cc=lftan@altera.com \
--cc=linux-arch@vger.kernel.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/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;
as well as URLs for NNTP newsgroup(s).