From: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com> To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> Cc: Simon Horman <horms+renesas@verge.net.au>, netdev@vger.kernel.org, linux-sh@vger.kernel.org, devicetree-discuss@lists.ozlabs.org, Magnus Damm <magnus.damm@gmail.com> Subject: Re: [PATCH] net: sh_eth: Add support of device tree probe Date: Thu, 07 Feb 2013 00:58:58 +0000 [thread overview] Message-ID: <CABMQnVLr9WqMWC6z3BuYyBvNSXM491VwrZ+DcKd3qGu0UN-G3Q@mail.gmail.com> (raw) In-Reply-To: <87pq0dg7ot.wl%kuninori.morimoto.gx@renesas.com> Hi, On Wed, Feb 6, 2013 at 5:36 PM, Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> wrote: > > Hi Simon, Iwamatsu-san > >> +Required properties: >> +- compatible: "renesas,sh-eth"; >> +- interrupt-parent: The phandle for the interrupt controller that >> + services interrupts for this device. >> +- reg: Offset and length of the register set for the >> + device. >> +- interrupts: Interrupt mapping for the sh_eth interrupt >> + sources (vector id). >> +- phy-mode: String, operation mode of the PHY interface. >> +- sh-eth,edmac-endian: String, endian of sh_eth dmac. > > I believe endian is only little/big. > It can be "bool" settings, not "string" ? > If we use bool , we may use this as "sh-eth,edmac-endian-big" or sh-eth,edmac-endian-little. Or we define big-endian, and when using big-endian, we specify this. Either way is okay. >> +- sh-eth,endian: String, endian of sh_eth dmac. > > Is this really used it in this driver ? > Yes. In many cases, this uses little-endian, but user may specify big-endian, I think. Best regards, Nobuhiro -- Nobuhiro Iwamatsu
WARNING: multiple messages have this Message-ID (diff)
From: Nobuhiro Iwamatsu <nobuhiro.iwamatsu.yj@renesas.com> To: Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> Cc: Simon Horman <horms+renesas@verge.net.au>, netdev@vger.kernel.org, linux-sh@vger.kernel.org, devicetree-discuss@lists.ozlabs.org, Magnus Damm <magnus.damm@gmail.com> Subject: Re: [PATCH] net: sh_eth: Add support of device tree probe Date: Thu, 7 Feb 2013 09:58:58 +0900 [thread overview] Message-ID: <CABMQnVLr9WqMWC6z3BuYyBvNSXM491VwrZ+DcKd3qGu0UN-G3Q@mail.gmail.com> (raw) In-Reply-To: <87pq0dg7ot.wl%kuninori.morimoto.gx@renesas.com> Hi, On Wed, Feb 6, 2013 at 5:36 PM, Kuninori Morimoto <kuninori.morimoto.gx@renesas.com> wrote: > > Hi Simon, Iwamatsu-san > >> +Required properties: >> +- compatible: "renesas,sh-eth"; >> +- interrupt-parent: The phandle for the interrupt controller that >> + services interrupts for this device. >> +- reg: Offset and length of the register set for the >> + device. >> +- interrupts: Interrupt mapping for the sh_eth interrupt >> + sources (vector id). >> +- phy-mode: String, operation mode of the PHY interface. >> +- sh-eth,edmac-endian: String, endian of sh_eth dmac. > > I believe endian is only little/big. > It can be "bool" settings, not "string" ? > If we use bool , we may use this as "sh-eth,edmac-endian-big" or sh-eth,edmac-endian-little. Or we define big-endian, and when using big-endian, we specify this. Either way is okay. >> +- sh-eth,endian: String, endian of sh_eth dmac. > > Is this really used it in this driver ? > Yes. In many cases, this uses little-endian, but user may specify big-endian, I think. Best regards, Nobuhiro -- Nobuhiro Iwamatsu
next prev parent reply other threads:[~2013-02-07 0:58 UTC|newest] Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-02-06 2:00 [PATCH] net: sh_eth: Add support of device tree probe Simon Horman 2013-02-06 2:00 ` Simon Horman 2013-02-06 7:30 ` Denis Kirjanov 2013-02-06 7:30 ` Denis Kirjanov 2013-02-07 0:18 ` Nobuhiro Iwamatsu 2013-02-07 0:18 ` Nobuhiro Iwamatsu 2013-02-06 8:26 ` Magnus Damm 2013-02-06 8:26 ` Magnus Damm 2013-02-07 0:48 ` Nobuhiro Iwamatsu 2013-02-07 0:48 ` Nobuhiro Iwamatsu [not found] ` <1360116019-8870-1-git-send-email-horms+renesas-/R6kz+dDXgpPR4JQBCEnsQ@public.gmane.org> 2013-02-06 8:36 ` Kuninori Morimoto 2013-02-06 8:36 ` Kuninori Morimoto 2013-02-07 0:58 ` Nobuhiro Iwamatsu [this message] 2013-02-07 0:58 ` Nobuhiro Iwamatsu 2013-02-07 1:42 ` Kuninori Morimoto 2013-02-07 1:42 ` Kuninori Morimoto 2013-02-07 4:48 ` Nobuhiro Iwamatsu 2013-02-07 4:48 ` Nobuhiro Iwamatsu
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=CABMQnVLr9WqMWC6z3BuYyBvNSXM491VwrZ+DcKd3qGu0UN-G3Q@mail.gmail.com \ --to=nobuhiro.iwamatsu.yj@renesas.com \ --cc=devicetree-discuss@lists.ozlabs.org \ --cc=horms+renesas@verge.net.au \ --cc=kuninori.morimoto.gx@renesas.com \ --cc=linux-sh@vger.kernel.org \ --cc=magnus.damm@gmail.com \ --cc=netdev@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.