netdev.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Florian Fainelli <f.fainelli@gmail.com>
To: Linus Walleij <linus.walleij@linaro.org>,
	Andrew Lunn <andrew@lunn.ch>,
	"David S . Miller" <davem@davemloft.net>
Cc: netdev@vger.kernel.org,
	Laurent Pinchart <Laurent.pinchart@ideasonboard.com>
Subject: Re: [PATCH net-next 0/5] Modernize bitbanged GPIO MDIO
Date: Tue, 27 Feb 2018 06:00:33 -0800	[thread overview]
Message-ID: <421c14be-a712-5427-f3d6-ba29d69ed02c@gmail.com> (raw)
In-Reply-To: <20180225125132.25275-1-linus.walleij@linaro.org>



On 02/25/2018 04:51 AM, Linus Walleij wrote:
> This kills off the platform data support from the bitbanged
> GPIO-based MDIO driver and moves it over to using GPIO
> descriptors exclusively.
> 
> We are certainly not going to merge any more platforms into
> the kernel using platform data, and nothing is using it at the
> moment. The only concern would be out-of-tree platforms, and
> those are not the concern of the kernel community. They need
> to move to use device tree (or ACPI etc) like everyone else.

Please refrain from making statements like those because there are
perfectly valid use cases for never seeing ACPI or Device Tree for a
given platform, yes there will be push back, and yes, if DT or ACPI is
possible, it should be used but I can guarantee you there are platforms
out there that won't be converted to DT (e.g: tons of MIPS-based router,
x86 add-on modules etc.).

Nack on patches 1 and 3, because I am slowly resuming work on an x86
platform driver that uses the mdio-gpio driver with platform data, and
DT is not an option there, and I would rather not have to revert your
changes.

> 
> This was tested on the bit-banged GPIO MDIO on the D-Link
> DNS-313 and works fine for me.
> 
> Linus Walleij (5):
>   net: mdio-gpio: Localize platform data
>   net: mdio-gpio: Allocate state in probe()
>   net: mdio-gpio: Remove non-DT probe path
>   net: mdio-gpio: Merge platform data into state
>   net: mdio-gpio: Move to gpiod API
> 
>  MAINTAINERS                             |   1 -
>  drivers/net/phy/Kconfig                 |   2 +-
>  drivers/net/phy/mdio-gpio.c             | 151 ++++++++++----------------------
>  include/linux/platform_data/mdio-gpio.h |  33 -------
>  4 files changed, 47 insertions(+), 140 deletions(-)
>  delete mode 100644 include/linux/platform_data/mdio-gpio.h
> 

-- 
Florian

  parent reply	other threads:[~2018-02-27 14:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-02-25 12:51 [PATCH net-next 0/5] Modernize bitbanged GPIO MDIO Linus Walleij
2018-02-25 12:51 ` [PATCH net-next 1/5] net: mdio-gpio: Localize platform data Linus Walleij
2018-02-25 12:51 ` [PATCH net-next 2/5] net: mdio-gpio: Allocate state in probe() Linus Walleij
2018-02-25 12:51 ` [PATCH net-next 3/5] net: mdio-gpio: Remove non-DT probe path Linus Walleij
2018-02-25 12:51 ` [PATCH net-next 4/5] net: mdio-gpio: Merge platform data into state Linus Walleij
2018-02-25 12:51 ` [PATCH net-next 5/5] net: mdio-gpio: Move to gpiod API Linus Walleij
2018-02-25 19:08 ` [PATCH net-next 0/5] Modernize bitbanged GPIO MDIO Andrew Lunn
2018-02-27  8:53   ` Linus Walleij
2018-02-27 14:00 ` Florian Fainelli [this message]
2018-02-27 23:10   ` Andrew Lunn
2018-02-27 23:46     ` Florian Fainelli
2018-03-02  9:44   ` Linus Walleij

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=421c14be-a712-5427-f3d6-ba29d69ed02c@gmail.com \
    --to=f.fainelli@gmail.com \
    --cc=Laurent.pinchart@ideasonboard.com \
    --cc=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=linus.walleij@linaro.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;
as well as URLs for NNTP newsgroup(s).