From: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
To: linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: shmobile: koelsch: Conditionally select MICREL_PHY
Date: Mon, 16 Dec 2013 13:25:42 +0000 [thread overview]
Message-ID: <52AEFF56.5010602@cogentembedded.com> (raw)
In-Reply-To: <1387153872-8387-1-git-send-email-horms+renesas@verge.net.au>
Hello.
On 16-12-2013 4:31, Simon Horman wrote:
> The koelsch board uses has an SH ethernet controller which uses a Micrel
> phy. Select MICREL_PHY for koelsch if SH_ETH is enabled to make use of the
> Micrel-specific phy driver rather than relying on the generic phy driver.
Frankly speaking, I'm seeing no advantages to doing that.
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
Analogous changes are needed for BOCK-W and Lager boards since they all
use the same KSZ8041RNLI PHY chip. I was going to submit such changes with the
PHY IRQ patches but since no IRQ is generated still, this got delayed...
WBR, Sergei
WARNING: multiple messages have this Message-ID (diff)
From: sergei.shtylyov@cogentembedded.com (Sergei Shtylyov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: shmobile: koelsch: Conditionally select MICREL_PHY
Date: Mon, 16 Dec 2013 17:25:42 +0400 [thread overview]
Message-ID: <52AEFF56.5010602@cogentembedded.com> (raw)
In-Reply-To: <1387153872-8387-1-git-send-email-horms+renesas@verge.net.au>
Hello.
On 16-12-2013 4:31, Simon Horman wrote:
> The koelsch board uses has an SH ethernet controller which uses a Micrel
> phy. Select MICREL_PHY for koelsch if SH_ETH is enabled to make use of the
> Micrel-specific phy driver rather than relying on the generic phy driver.
Frankly speaking, I'm seeing no advantages to doing that.
> Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
Analogous changes are needed for BOCK-W and Lager boards since they all
use the same KSZ8041RNLI PHY chip. I was going to submit such changes with the
PHY IRQ patches but since no IRQ is generated still, this got delayed...
WBR, Sergei
next prev parent reply other threads:[~2013-12-16 13:25 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-16 0:31 [PATCH] ARM: shmobile: koelsch: Conditionally select MICREL_PHY Simon Horman
2013-12-16 0:31 ` Simon Horman
2013-12-16 13:25 ` Sergei Shtylyov [this message]
2013-12-16 13:25 ` Sergei Shtylyov
2013-12-16 22:31 ` Sergei Shtylyov
2013-12-16 23:31 ` Sergei Shtylyov
2013-12-17 0:31 ` Simon Horman
2013-12-17 0:31 ` Simon Horman
2013-12-17 10:10 ` Geert Uytterhoeven
2013-12-17 10:10 ` Geert Uytterhoeven
2013-12-18 0:53 ` Simon Horman
2013-12-18 0:53 ` Simon Horman
2013-12-19 9:04 ` Simon Horman
2013-12-19 9:04 ` Simon Horman
2013-12-17 0:30 ` Simon Horman
2013-12-17 0:30 ` Simon Horman
2013-12-19 22:05 ` Sergei Shtylyov
2013-12-19 23:05 ` Sergei Shtylyov
2013-12-26 5:30 ` Simon Horman
2013-12-26 5:30 ` 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=52AEFF56.5010602@cogentembedded.com \
--to=sergei.shtylyov@cogentembedded.com \
--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 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.