-----Original Message----- From: Marek Behún kabel@kernel.org Sent: Tuesday, October 26, 2021 6:18 AM To: Roman Bacik roman.bacik@broadcom.com Cc: 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; Simon Glass sjg@chromium.org Subject: Re: [PATCH v3 2/2] cmd: brcm: netXtreme commands
On Mon, 25 Oct 2021 16:44:44 -0700 Roman Bacik roman.bacik@broadcom.com wrote:
From: Bharat Gooty bharat.gooty@broadcom.com
Following netXtreme commands are supported: probe, remove.
Signed-off-by: Bharat Gooty bharat.gooty@broadcom.com
Signed-off-by: Roman Bacik roman.bacik@broadcom.com
Hi Roman,
why do you need to have custom command for probing / removing the driver?
U-Boot PCI code should probe the driver automatically upon recognizing PCI vendor / device ID.
Even if not, adding custom command for such a thing isn't nice, when we have the `dm` command for communicating with driver model.
Marek
Hi Marek,
We do not want this driver to be automatically probed. It is not needed all the time and also slows down the boot time. We have stripped down everything else to bare minimum. Thanks,
Roman