public inbox for linuxppc-dev@ozlabs.org
 help / color / mirror / Atom feed
From: Alistair Popple <alistair@popple.id.au>
To: Ben Hutchings <bhutchings@solarflare.com>
Cc: linuxppc-dev@lists.ozlabs.org,
	"David S. Miller" <davem@davemloft.net>,
	netdev@vger.kernel.org
Subject: Re: [PATCH 3/7] IBM Akebono: Add support for a new PHY to the IBM emac driver
Date: Wed, 06 Nov 2013 12:34:30 +1100	[thread overview]
Message-ID: <3555701.fBbreSn0Lp@mexican> (raw)
In-Reply-To: <1383693110.2868.17.camel@bwh-desktop.uk.level5networks.com>

On Tue, 5 Nov 2013 23:11:50 Ben Hutchings wrote:
> On Wed, 2013-11-06 at 06:54 +1100, Benjamin Herrenschmidt wrote:

[snip]

> > It's an SoC bit so there's little point making it generally
> > selectable by the user.
> 
> I think a better way to do this is:
> 
> config IBM_EMAC_RGMII_WOL
> 	bool "IBM EMAC RGMII wake-on-LAN support"
> 	depends on MY_WONDERFUL_NEW_SOC || COMPILE_TEST
> 	default y if MY_WONDERFUL_NEW_SOC
> 
> Then anyone making an API change that affects this driver can check that
> it still complies.

The method used in this patch is the same as what is currently used by the 
other IBM EMAC PHY interfaces (eg. config IBM_EMAC_ZMII etc). I'm happy to 
send a patch to update all of those as well for consistency but that would 
mean adding what each platform requires into EMACS Kconfig as well.

Personally I think it is nicer to keep the definitions of what each platform 
requires in one place (ie. arch/powerpc/platforms/44x/Kconfig) as it is 
consistent with what we do for other 44x drivers, however I am happy to use 
the above method if people think it's better.

Alternatively we could do something like this:

config IBM_EMAC_RGMII_WOL
        bool
        default y if COMPILE_TEST
        default n

This would leave the platform dependencies as they are currently but still 
allow compile testing.

Regards,

Alistair

> Ben.
> 
> > Alistair: The commit name should be different, it's not a PHY you are
> > adding, it's a PHY interface (the PHY itself is off chip).

  reply	other threads:[~2013-11-06  1:34 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-05  5:31 [PATCH 1/7] IBM Akebono: Add support to AHCI platform driver Alistair Popple
2013-11-05  5:31 ` [PATCH 2/7] IBM Akebono: Add a SDHCI " Alistair Popple
2013-11-05  5:31 ` [PATCH 3/7] IBM Akebono: Add support for a new PHY to the IBM emac driver Alistair Popple
2013-11-05 18:16   ` Ben Hutchings
2013-11-05 19:54     ` Benjamin Herrenschmidt
2013-11-05 23:11       ` Ben Hutchings
2013-11-06  1:34         ` Alistair Popple [this message]
2013-11-06 16:40           ` Ben Hutchings
2013-11-07  2:39             ` Alistair Popple
2013-11-05 18:47   ` Florian Fainelli
2013-11-06  0:08     ` Alistair Popple
2013-11-06  0:16       ` Florian Fainelli
2013-11-06  1:38         ` Alistair Popple
2013-11-06  2:17           ` Benjamin Herrenschmidt
2013-11-06  2:23             ` Florian Fainelli
2013-11-05  5:31 ` [PATCH 4/7] IBM Akebono: Add support to the OHCI platform driver for Akebono Alistair Popple
2013-11-05 15:04   ` Alan Stern
2013-11-07  3:34     ` Alistair Popple
2013-11-07  4:55       ` Benjamin Herrenschmidt
2013-11-07 15:04       ` Alan Stern
2013-11-05  5:31 ` [PATCH 5/7] IBM Akebono: Add support to the EHCI " Alistair Popple
2013-11-05 15:04   ` Alan Stern
2013-11-05 19:52     ` Benjamin Herrenschmidt
2013-11-06  3:50       ` Alistair Popple
2013-11-06  3:58         ` Benjamin Herrenschmidt
2013-11-06  7:39           ` [RFC PATCH] ehci-platform: Merge ppc-of EHCI driver into the ehci-platform driver Alistair Popple
2013-11-06 16:14             ` Alan Stern
2013-11-07  2:34               ` Alistair Popple
2013-11-06 19:57             ` Benjamin Herrenschmidt
2013-11-07  2:35               ` Alistair Popple
2013-11-05  5:31 ` [PATCH 6/7] IBM Currituck: Clean up board specific code before adding Akebono code Alistair Popple
2013-11-05  5:31 ` [PATCH 7/7] IBM Akebono: Add the Akebono platform Alistair Popple

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=3555701.fBbreSn0Lp@mexican \
    --to=alistair@popple.id.au \
    --cc=bhutchings@solarflare.com \
    --cc=davem@davemloft.net \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --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: 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