From: "Heiko Stübner" <heiko@sntech.de> To: Arnd Bergmann <arnd@arndb.de> Cc: Romain Perier <romain.perier@gmail.com>, linux-rockchip@lists.infradead.org, linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org Subject: Re: [PATCH v2] ethernet: arc: Add support for Rockchip SoC layer device tree bindings Date: Wed, 27 Aug 2014 22:19:22 +0200 [thread overview] Message-ID: <33554745.SgNonHnYhV@diego> (raw) In-Reply-To: <3619843.a6HHkMsuOu@wuerfel> Am Mittwoch, 27. August 2014, 22:11:29 schrieb Arnd Bergmann: > On Wednesday 27 August 2014 06:55:27 Romain Perier wrote: > > This patch defines a platform glue layer for Rockchip SoCs which > > support arc-emac driver. It ensures that regulator for the rmii is on > > before trying to connect to the ethernet controller. It applies right > > speed and mode changes to the grf when ethernet settings change. > > > > Signed-off-by: Romain Perier <romain.perier@gmail.com> > > --- > > > > drivers/net/ethernet/arc/Kconfig | 15 +++ > > drivers/net/ethernet/arc/Makefile | 1 + > > drivers/net/ethernet/arc/emac.h | 2 + > > drivers/net/ethernet/arc/emac_main.c | 2 + > > drivers/net/ethernet/arc/emac_rockchip.c | 224 > > +++++++++++++++++++++++++++++++ 5 files changed, 244 insertions(+) > > create mode 100644 drivers/net/ethernet/arc/emac_rockchip.c > > > > diff --git a/drivers/net/ethernet/arc/Kconfig > > b/drivers/net/ethernet/arc/Kconfig index 89e04fd..6d96a82 100644 > > --- a/drivers/net/ethernet/arc/Kconfig > > +++ b/drivers/net/ethernet/arc/Kconfig > > @@ -32,4 +32,19 @@ config ARC_EMAC > > > > non-standard on-chip ethernet device ARC EMAC 10/100 is used. > > Say Y here if you have such a board. If unsure, say N. > > > > +config EMAC_ROCKCHIP > > + tristate "Rockchip EMAC support" > > + select ARC_EMAC_CORE > > + depends on OF_IRQ > > + depends on OF_NET > > + depends on ARCH_ROCKCHIP > > + depends on REGULATOR_ACT8865 > > + depends on SMSC_PHY > > + depends on MFD_SYSCON > > You should generally not add 'depends on' for specific drivers out > of a subsystems. Just list the build-time dependencies, like > > depends on OF_IRQ && OF_NET && PHYLIB && REGULATOR && MFD_SYSCON in this case even MFD_SYSCON can go away, as the syscon functions provide stubs for !MFD_SYSCON . [...] > > + rate = 50000000; > > Where does this number come from? The RMII interface needs always a rate of 50MHz ... my questions would be why the 50000000 are not in the clk_set_rate directly and need an extra var :-) Heiko
WARNING: multiple messages have this Message-ID (diff)
From: heiko@sntech.de (Heiko Stübner) To: linux-arm-kernel@lists.infradead.org Subject: [PATCH v2] ethernet: arc: Add support for Rockchip SoC layer device tree bindings Date: Wed, 27 Aug 2014 22:19:22 +0200 [thread overview] Message-ID: <33554745.SgNonHnYhV@diego> (raw) In-Reply-To: <3619843.a6HHkMsuOu@wuerfel> Am Mittwoch, 27. August 2014, 22:11:29 schrieb Arnd Bergmann: > On Wednesday 27 August 2014 06:55:27 Romain Perier wrote: > > This patch defines a platform glue layer for Rockchip SoCs which > > support arc-emac driver. It ensures that regulator for the rmii is on > > before trying to connect to the ethernet controller. It applies right > > speed and mode changes to the grf when ethernet settings change. > > > > Signed-off-by: Romain Perier <romain.perier@gmail.com> > > --- > > > > drivers/net/ethernet/arc/Kconfig | 15 +++ > > drivers/net/ethernet/arc/Makefile | 1 + > > drivers/net/ethernet/arc/emac.h | 2 + > > drivers/net/ethernet/arc/emac_main.c | 2 + > > drivers/net/ethernet/arc/emac_rockchip.c | 224 > > +++++++++++++++++++++++++++++++ 5 files changed, 244 insertions(+) > > create mode 100644 drivers/net/ethernet/arc/emac_rockchip.c > > > > diff --git a/drivers/net/ethernet/arc/Kconfig > > b/drivers/net/ethernet/arc/Kconfig index 89e04fd..6d96a82 100644 > > --- a/drivers/net/ethernet/arc/Kconfig > > +++ b/drivers/net/ethernet/arc/Kconfig > > @@ -32,4 +32,19 @@ config ARC_EMAC > > > > non-standard on-chip ethernet device ARC EMAC 10/100 is used. > > Say Y here if you have such a board. If unsure, say N. > > > > +config EMAC_ROCKCHIP > > + tristate "Rockchip EMAC support" > > + select ARC_EMAC_CORE > > + depends on OF_IRQ > > + depends on OF_NET > > + depends on ARCH_ROCKCHIP > > + depends on REGULATOR_ACT8865 > > + depends on SMSC_PHY > > + depends on MFD_SYSCON > > You should generally not add 'depends on' for specific drivers out > of a subsystems. Just list the build-time dependencies, like > > depends on OF_IRQ && OF_NET && PHYLIB && REGULATOR && MFD_SYSCON in this case even MFD_SYSCON can go away, as the syscon functions provide stubs for !MFD_SYSCON . [...] > > + rate = 50000000; > > Where does this number come from? The RMII interface needs always a rate of 50MHz ... my questions would be why the 50000000 are not in the clk_set_rate directly and need an extra var :-) Heiko
next prev parent reply other threads:[~2014-08-27 20:17 UTC|newest] Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top 2014-08-27 6:55 [PATCH v2] ethernet: arc: Add support for Rockchip SoC layer device tree bindings Romain Perier 2014-08-27 6:55 ` Romain Perier 2014-08-27 15:28 ` PERIER Romain 2014-08-27 15:28 ` PERIER Romain 2014-08-27 20:11 ` Arnd Bergmann 2014-08-27 20:11 ` Arnd Bergmann 2014-08-27 20:19 ` Heiko Stübner [this message] 2014-08-27 20:19 ` Heiko Stübner
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=33554745.SgNonHnYhV@diego \ --to=heiko@sntech.de \ --cc=arnd@arndb.de \ --cc=linux-arm-kernel@lists.infradead.org \ --cc=linux-rockchip@lists.infradead.org \ --cc=netdev@vger.kernel.org \ --cc=romain.perier@gmail.com \ /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.