[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20221121201917.080365ce@kernel.org>
Date: Mon, 21 Nov 2022 20:19:17 -0800
From: Jakub Kicinski <kuba@...nel.org>
To: Lorenzo Bianconi <lorenzo@...nel.org>
Cc: netdev@...r.kernel.org, nbd@....name, john@...ozen.org,
sean.wang@...iatek.com, Mark-MC.Lee@...iatek.com,
davem@...emloft.net, edumazet@...gle.com, pabeni@...hat.com,
lorenzo.bianconi@...hat.com, sujuan.chen@...iatek.com,
linux-mediatek@...ts.infradead.org
Subject: Re: [PATCH net-next 5/5] net: ethernet: mtk_wed: add reset to
tx_ring_setup callback
On Mon, 21 Nov 2022 22:18:33 +0100 Lorenzo Bianconi wrote:
> > On Mon, 21 Nov 2022 09:59:25 +0100 Lorenzo Bianconi wrote:
> > > +#define mtk_wed_device_tx_ring_setup(_dev, _ring, _regs, _reset) \
> > > + (_dev)->ops->tx_ring_setup(_dev, _ring, _regs, _reset)
> >
> > FWIW I find the "op macros" quite painful when trying to read a driver
> > I'm not familiar with. stmmac does this, too. Just letting you know,
> > it is what it is.
>
> ack, fine. I maintained the approach currently used in the driver.
> Do you prefer to run the function pointer directly?
That's a tiny bit better, yes, saves the reader one lookup.
Are the ops here serving as a HAL or a way of breaking the dependency
between the SoC/Eth and the WiFi drivers?
Powered by blists - more mailing lists