public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: David Miller <davem@davemloft.net>
Cc: vivien.didelot@savoirfairelinux.com, netdev@vger.kernel.org,
	linux-kernel@vger.kernel.org, kernel@savoirfairelinux.com,
	f.fainelli@gmail.com
Subject: Re: [PATCH net-next 11/12] net: dsa: mv88e6xxx: add Energy Detect ops
Date: Mon, 17 Jul 2017 23:04:05 +0200	[thread overview]
Message-ID: <20170717210405.GC11719@lunn.ch> (raw)
In-Reply-To: <20170717.134549.2101398770863549187.davem@davemloft.net>

On Mon, Jul 17, 2017 at 01:45:49PM -0700, David Miller wrote:
> From: Vivien Didelot <vivien.didelot@savoirfairelinux.com>
> Date: Mon, 17 Jul 2017 15:32:52 -0400
> 
> > Hi Andrew,
> > 
> > Andrew Lunn <andrew@lunn.ch> writes:
> > 
> >> I never liked this. I think it is architecturally wrong for the switch
> >> to be poking around in the PHY. It should ask the PHY driver. This is
> >> especially true for external PHYs which might not be a Marvell PHY.
> > 
> > I share the same concern. However this patch is just isolating the
> > existing code so that we get rid of the last caps and flags and stop
> > writing (without reading them first) arbitrary registers.
> > 
> > Once this portion is moved to the PHY driver, one can remove it from
> > mv88e6xxx.
> 
> Seems a reasonable plan of action.
> 
> Andrew, do you agree?

Hi David

I just fear it will not get fixed, just put into a corner to
fester. Having to fix it properly before these patches are merged
provides some incentive.

	 Andrew

  reply	other threads:[~2017-07-17 21:04 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-17 17:03 [PATCH net-next 00/12] net: dsa: mv88e6xxx: cleanup capabilities Vivien Didelot
2017-07-17 17:03 ` [PATCH net-next 01/12] net: dsa: mv88e6xxx: remove unneeded dsa header Vivien Didelot
2017-07-17 18:57   ` Andrew Lunn
2017-07-17 17:03 ` [PATCH net-next 02/12] net: dsa: mv88e6xxx: remove LED control register Vivien Didelot
2017-07-17 18:57   ` Andrew Lunn
2017-07-17 17:03 ` [PATCH net-next 03/12] net: dsa: mv88e6xxx: fix 88E6321 family comment Vivien Didelot
2017-07-17 18:57   ` Andrew Lunn
2017-07-17 17:03 ` [PATCH net-next 04/12] net: dsa: mv88e6xxx: remove unused capabilities Vivien Didelot
2017-07-17 18:56   ` Andrew Lunn
2017-07-17 17:03 ` [PATCH net-next 05/12] net: dsa: mv88e6xxx: remove 88E6185 G2 interrupt Vivien Didelot
2017-07-17 18:55   ` Andrew Lunn
2017-07-17 17:03 ` [PATCH net-next 06/12] net: dsa: mv88e6xxx: add number of Global 2 IRQs Vivien Didelot
2017-07-17 17:43   ` Andrew Lunn
2017-07-17 17:03 ` [PATCH net-next 07/12] net: dsa: mv88e6xxx: distinguish Global 2 Rsvd2CPU Vivien Didelot
2017-07-17 17:03 ` [PATCH net-next 08/12] net: dsa: mv88e6xxx: add POT flag to 88E6390 Vivien Didelot
2017-07-17 19:15   ` Andrew Lunn
2017-07-17 17:03 ` [PATCH net-next 09/12] net: dsa: mv88e6xxx: add POT operation Vivien Didelot
2017-07-17 19:17   ` Andrew Lunn
2017-07-17 17:03 ` [PATCH net-next 10/12] net: dsa: mv88e6xxx: add a global2_addr info flag Vivien Didelot
2017-07-17 19:19   ` Andrew Lunn
2017-07-17 17:03 ` [PATCH net-next 11/12] net: dsa: mv88e6xxx: add Energy Detect ops Vivien Didelot
2017-07-17 19:27   ` Andrew Lunn
2017-07-17 19:32     ` Vivien Didelot
2017-07-17 20:45       ` David Miller
2017-07-17 21:04         ` Andrew Lunn [this message]
2017-07-17 21:10           ` David Miller
2017-07-18 16:01             ` Florian Fainelli
2017-07-18 17:46               ` David Miller
2017-07-18 18:59                 ` Vivien Didelot
2017-07-18 19:58                   ` Andrew Lunn
2017-07-17 17:03 ` [PATCH net-next 12/12] net: dsa: mv88e6xxx: add a multi_chip info flag Vivien Didelot
2017-07-17 19:32   ` Andrew Lunn
2017-07-18 18:11 ` [PATCH net-next 00/12] net: dsa: mv88e6xxx: cleanup capabilities David Miller
  -- strict thread matches above, loose matches on Subject: below --
2017-07-04 23:41 Vivien Didelot
2017-07-04 23:41 ` [PATCH net-next 11/12] net: dsa: mv88e6xxx: add Energy Detect ops Vivien Didelot

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=20170717210405.GC11719@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=davem@davemloft.net \
    --cc=f.fainelli@gmail.com \
    --cc=kernel@savoirfairelinux.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=vivien.didelot@savoirfairelinux.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: 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