Hi Marek,
-----Original Message----- From: Marek Behún kabel@kernel.org Sent: Wednesday, October 27, 2021 10:40 AM To: Roman Bacik roman.bacik@broadcom.com Cc: Simon Glass sjg@chromium.org; U-Boot Mailing List <u- boot@lists.denx.de>; Bharat Gooty bharat.gooty@broadcom.com; Aswath Govindraju a-govindraju@ti.com; Bin Meng bmeng.cn@gmail.com; Franck LENORMAND franck.lenormand@nxp.com; Heinrich Schuchardt xypron.glpk@gmx.de; Kory Maincent kory.maincent@bootlin.com; Michal Simek michal.simek@xilinx.com; Patrick Delaunay patrick.delaunay@foss.st.com; Peng Fan peng.fan@nxp.com; Priyanka Jain priyanka.jain@nxp.com; Rayagonda Kokatanur rayagonda.kokatanur@broadcom.com; Sean Anderson sean.anderson@seco.com Subject: Re: [PATCH v3 2/2] cmd: brcm: netXtreme commands
On Wed, 27 Oct 2021 10:02:41 -0700 Roman Bacik roman.bacik@broadcom.com wrote:
Marek, Simon,
Thank you very much for your comments. We will remove bnxt commands
and will
probe bnxt driver each boot in the next version. Thanks,
Roman
I think that the idea of not loading fw or initializing the controller during every boot, but only when needed, is quite reasonable.
But it has to be done without the need to call custom commands, which the user may not know about.
It has to be done in such a way that if the user calls for example the dhcp command, it will work.
I think this could be achieved by creating a new DM driver flag, and wiring the DM and/or PCI code so that when this flag is set, the PCI subsystem won't probe the driver, only bind the driver.
Thank you very much for your suggestion. To simplify, we will decouple this issue from the current bnxt driver submission.
That way U-Boot will know that there is another ethernet controller which can be used by network commands when the `ethact` variable is set to point to that controller.
Marek
Thanks,
Roman