Re: [PATCH 00/13] Discover and probe dependencies

Mark Brown
2015-06-18T10:37:13Z

[-- Attachment #1: Type: text/plain, Size: 1227 bytes --]

On Thu, Jun 18, 2015 at 11:42:01AM +0200, Andrzej Hajda wrote:

There's something really messed up with how your mailer is word wrapping
paragraphs, might want to check it out - it looks like it's making lines
that are longer than 80 columns and then randomly breaking them 80
columns in rather than reflowing things.

> 3. Dependencies are mandatory, ie without it driver will not be able to
> successfully finish
> the probe.
> It should be not true. Sometimes device will require given resource
> only in specific
> scenario, or it can still probe successfully and ask for the
> resource later.
> I can also imagine that firmware can describe more information than
> given driver require,
> some resources even if they are present in the dts, will be not
> requested by the driver, it
> can be the case of drivers providing limited functionality, or just
> obsolete bindings.

Well, this isn't clear - the model here seems to be that the
dependencies are those that are explicitly listed for a given platform.
For those our current expectation is that we will try to control them
and will defer probe until the resources that are mapped in on the
platform are present so this doesn't seem like a change.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]