From: horms@verge.net.au (Simon Horman)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] ARM: shmobile: BOCK-W: add Ether support
Date: Sat, 25 May 2013 14:30:10 +0900 [thread overview]
Message-ID: <20130525053007.GA9293@verge.net.au> (raw)
In-Reply-To: <201305170141.59791.sergei.shtylyov@cogentembedded.com>
On Fri, May 17, 2013 at 01:41:59AM +0400, Sergei Shtylyov wrote:
> Register Ether device from bockw_init(), passing the platform data to it, adding
> only the RMII pin group to bockw_pinctrl_map[]. Although the LINK signal exists
> on the board, it's connected to the link/activity LED output of the PHY, thus
> the link disappears and reappears after each packet. We'd be better off ignoring
> such signal and getting the link state from the PHY indirectly.
>
> Also, Ether has pin conflict with VIN1, so the latter is not registered when the
> 'sh_eth' driver is enabled now.
>
> Signed-off-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
>
> ---
> The patch is atop of Simon's 'renesas.git' repo, 'renesas-next-20130515v2' tag
> and my recent yet unapplied patches.
>
> Note that it's compile and run time dependent on the current Linus' tree.
>
> Changes from the original posting:
> - refreshed the patch.
Thanks, would it be possible for you to rebase it on top of
renesas-next-20130523.
renesas-next-20130523 is based on v3.10-rc2, so I think it should
have whatever dependencies that were in Linus's tree at the time
that you posted this patch.
next prev parent reply other threads:[~2013-05-25 5:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-16 21:41 [PATCH v2] ARM: shmobile: BOCK-W: add Ether support Sergei Shtylyov
2013-05-25 5:30 ` Simon Horman [this message]
2013-05-25 18:08 ` Sergei Shtylyov
2013-05-25 23:22 ` Simon Horman
2013-05-25 23:40 ` Sergei Shtylyov
2013-05-26 13:33 ` Simon Horman
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=20130525053007.GA9293@verge.net.au \
--to=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.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).