From: Stefan Wahren <stefan.wahren@i2se•com>
To: Ben Hutchings <ben@decadent•org.uk>
Cc: Stefan Wahren <info@lategoodbye•de>,
netdev@vger•kernel.org,
"Fabio.Estevam@freescale•com" <Fabio.Estevam@freescale•com>
Subject: Re: Porting ethernet over spi driver (powerline device)
Date: Fri, 25 Apr 2014 09:24:57 +0200 [thread overview]
Message-ID: <535A0DC9.8060102@i2se.com> (raw)
In-Reply-To: <1398180075.3624.191.camel@deadeye.wl.decadent.org.uk>
Am 22.04.2014 17:21, schrieb Ben Hutchings:
> On Tue, 2014-04-22 at 12:02 +0200, Stefan Wahren wrote:
>> Am 22.04.2014 04:22, schrieb Ben Hutchings:
> [..]
>>> Most of the interesting new features are related to multiqueue and
>>> protocol offloads that I wouldn't expect to exist in an SPI-attached
>>> Ethernet controller.
>> You are right.
>>
>> Btw, is simple power management (suspend, resume) a must-have feature?
> If you're intending to get the driver in-tree, I don't think those are
> an absolute requirement but I would certainly recommend implementing
> them.
>
> Ben.
>
Yes, that's my intension. The QCA7000 isn't a typical ethernet over spi
device, it's a serial-to-powerline bridge. Acting like a ethernet over
spi device simplifies the implementation. This leads to an important
question.
Should the QCA7000 be handled strict as an ethernet device or a little
bit more distinguished as a powerline device?
I think that would have influence on the following aspects:
* Interface naming scheme in user space
Currently the interface has the interface pattern qca%d instead of
eth%d. I think this won't be acceptable for in-tree. But the interface
pattern pwl%d for powerline could also be possible.
* Node name in devicetree sources
Currently the node is named as qca7000, but from my understanding it's
should be ethernet or powerline.
* Driver directory in kernel sources
In my development i store the sources under drivers/net/ethernet. But
for in-tree i see the following candidates:
drivers/net/ethernet/qca/
drivers/net/ethernet/qualcomm/
drivers/net/powerline/qca/
Any suggestions?
Kind regards
Stefan Wahren
next prev parent reply other threads:[~2014-04-25 7:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-18 9:17 Porting ethernet over spi driver Stefan Wahren
2014-04-22 2:22 ` Ben Hutchings
2014-04-22 10:02 ` Stefan Wahren
2014-04-22 15:21 ` Ben Hutchings
2014-04-25 7:24 ` Stefan Wahren [this message]
2014-04-26 13:45 ` Porting ethernet over spi driver (powerline device) Ben Hutchings
2014-04-22 2:32 ` Porting ethernet over spi driver Fabio Estevam
2014-04-22 9:42 ` Stefan Wahren
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=535A0DC9.8060102@i2se.com \
--to=stefan.wahren@i2se$(echo .)com \
--cc=Fabio.Estevam@freescale$(echo .)com \
--cc=ben@decadent$(echo .)org.uk \
--cc=info@lategoodbye$(echo .)de \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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