From: Simon Horman <horms@kernel.org>
To: "Christian Marangi (Ansuel)" <ansuelsmth@gmail.com>
Cc: Lorenzo Bianconi <lorenzo@kernel.org>,
netdev@vger.kernel.org, andrew+netdev@lunn.ch,
davem@davemloft.net, edumazet@google.com, kuba@kernel.org,
pabeni@redhat.com, nbd@nbd.name, sean.wang@mediatek.com,
upstream@airoha.com
Subject: Re: Move airoha in a dedicated folder
Date: Tue, 4 Feb 2025 09:37:37 +0000 [thread overview]
Message-ID: <20250204093737.GL234677@kernel.org> (raw)
In-Reply-To: <CA+_ehUwFTa2VvfqeTPyedFDWBHj3PeUem=ASMrrh1h3++yLc_A@mail.gmail.com>
On Sun, Feb 02, 2025 at 04:50:33PM +0100, Christian Marangi (Ansuel) wrote:
> Il giorno sab 1 feb 2025 alle ore 16:50 Simon Horman
> <horms@kernel.org> ha scritto:
> >
> > On Sat, Feb 01, 2025 at 01:44:53PM +0100, Lorenzo Bianconi wrote:
> > > Hi all,
> > >
> > > Since more features are on the way for airoha_eth driver (support for flowtable
> > > hw offloading, 10g phy support, ..), I was wondering if it is neater to move
> > > the driver in a dedicated folder (e.g. drivers/net/ethernet/airoha or
> > > drivers/net/ethernet/mediatek/airoha) or if you prefer to keep current
> > > approach. Thanks.
> >
> > <2c>
> >
> > Hi Lorenzo,
> >
> > There already seem drivers to be drivers under drivers/net/ethernet/mediatek/
> > which are built from more than once .c file. So I think it is fine
> > to leave Airoha's source there. But, OTOH, I do think it would
> > be neater to move it into it's own directory. Which is to say,
> > I for one am happy either way.
> >
> > If you do chose to go for a new directory, I would suggest
> > drivers/net/ethernet/mediatek/airoha assuming as it is a Mediatek device.
> >
>
> Hi,
> may I push for a dedicated Airoha directory? (/net/ethernet/airoha ?)
>
> With new SoC it seems Airoha is progressively detaching from Mediatek.
>
> There are some similarities but for example for the PPE only the logical entry
> table is similar but rest of the stuff is handled by a coprocessor
> with dedicated
> firmware. My big concern is that we will start to bloat the mediatek directory
> with very different kind of code.
>
> Putting stuff in ethernet/mediatek/airoha would imply starting to use
> format like
> #include "../stuff.h" and maybe we would start to import stuff from
> mediatek that
> should not be used by airoha.
>
> Keeping the 2 thing split might make the similarities even more
> evident and easier
> to handle as we will have to rework the header to use the generic include/linux.
>
> Hope all of this makes sense, it's really to prevent situation and keep things
> organized from the start.
Thanks Christian,
Given the above and the conversation thus far elsewhere in this thread
I now agree that drivers/net/ethernet/airoha is a good option.
prev parent reply other threads:[~2025-02-04 9:37 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-01 12:44 Move airoha in a dedicated folder Lorenzo Bianconi
2025-02-01 15:43 ` Andrew Lunn
2025-02-01 15:50 ` Simon Horman
2025-02-02 15:50 ` Christian Marangi (Ansuel)
2025-02-02 16:49 ` Andrew Lunn
2025-02-02 17:00 ` Christian Marangi (Ansuel)
2025-02-02 20:59 ` Lorenzo Bianconi
2025-02-04 9:37 ` Simon Horman [this message]
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=20250204093737.GL234677@kernel.org \
--to=horms@kernel.org \
--cc=andrew+netdev@lunn.ch \
--cc=ansuelsmth@gmail.com \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=kuba@kernel.org \
--cc=lorenzo@kernel.org \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=sean.wang@mediatek.com \
--cc=upstream@airoha.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.