[dpdk-dev] [PATCH] eal: bus scan and probe never fail

Thomas Monjalon thomas at monjalon.net
Fri Oct 6 01:21:41 CEST 2017

19/09/2017 20:51, Jan Blunck:
> On Mon, Sep 18, 2017 at 1:36 PM, Hemant Agrawal <hemant.agrawal at nxp.com> wrote:
> > Tested-by: Hemant Agrawal <hemant.agrawal at nxp.com>
> >
> >
> > On 8/12/2017 3:52 PM, Shreyansh Jain wrote:
> >>
> >> Bus scan is responsible for finding devices over *all* buses.
> >> Some of these buses might not be able to scan but that should
> >> not prevent other buses to be scanned.
> >>
> If scanning the bus fails this is signaling an error. In that case we
> might even want to unregister the bus.

A scan error seems important enough to be reported to the caller.
OK to continue scanning other buses, but an error code should be returned.

> >> Same is the case for probing. It is possible that some devices which
> >> were scanned didn't have a specific driver. That should not prevent
> >> other buses from being probed.
> Absolutely correct.

When we will have a probe notification, we will be able
to notify the upper layer that a device probing has failed.

More information about the dev mailing list