From: Heiner Kallweit <hkallweit1@gmail.com>
To: Andrew Lunn <andrew@lunn.ch>
Cc: Daniel Gomez <dagmcr@gmail.com>,
f.fainelli@gmail.com, davem@davemloft.net,
netdev@vger.kernel.org, javier@dowhile0.org,
"linux-spi@vger.kernel.org" <linux-spi@vger.kernel.org>,
Mark Brown <broonie@kernel.org>
Subject: Re: [PATCH 1/2] spi: Micrel eth switch: declare missing of table
Date: Tue, 23 Apr 2019 19:33:10 +0200 [thread overview]
Message-ID: <0d2f503f-bd45-0009-343c-e6d47d7d6fe1@gmail.com> (raw)
In-Reply-To: <20190423122857.GB3371@lunn.ch>
On 23.04.2019 14:28, Andrew Lunn wrote:
>> I wonder why this SPI driver is under drivers/net/phy. Just because
>> the SPI IP is found on an ethernet switch chip? And even then it
>> would be wrong, I see no link to a PHY at all. I'd say the driver
>> belongs to drivers/spi. Shouldn't we move it?
>
> This driver is old. It is probably from before the time of DSA. At
> least in the OpenWRT world, switches have been thought of as PHY
> devices, since they connect to a MAC. All the OpenWRT switch drivers
> are in the phy directory.
>
> There is no good place for this. It is not a PHY, but it is a network
> driver so should be somewhere under driver/net. There are no other net
> drivers in driver/spi, etc.
>
Except having "switch" in the name this driver is solely a SPI driver
and it uses no network code at all. And it has no dependency on any
network driver. Therefore I wouldn't consider it a network driver.
Else any functionality found on a SoC would need to be under drivers/soc ;)
> Since there is not a good place for it, not moving it is the easiest
> thing to do.
>
> Andrew
>
Heiner
next prev parent reply other threads:[~2019-04-23 17:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1555960084-8462-1-git-send-email-dagmcr@gmail.com>
2019-04-23 6:04 ` [PATCH 1/2] spi: Micrel eth switch: declare missing of table Heiner Kallweit
2019-04-23 12:28 ` Andrew Lunn
2019-04-23 17:33 ` Heiner Kallweit [this message]
2019-04-25 18:04 ` Mark Brown
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=0d2f503f-bd45-0009-343c-e6d47d7d6fe1@gmail.com \
--to=hkallweit1@gmail.com \
--cc=andrew@lunn.ch \
--cc=broonie@kernel.org \
--cc=dagmcr@gmail.com \
--cc=davem@davemloft.net \
--cc=f.fainelli@gmail.com \
--cc=javier@dowhile0.org \
--cc=linux-spi@vger.kernel.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).