Thread (29 messages) read the whole thread 29 messages, 4 authors, 2015-07-17

Re: [alsa-devel] [PATCH v2 11/12] ASoC: tegra: register dependency parser for firmware nodes

From: Mark Brown <broonie@kernel.org>
Date: 2015-07-13 15:44:59
Also in: alsa-devel, dri-devel, linux-acpi, linux-devicetree, linux-gpio, linux-pwm, linux-tegra, lkml

On Mon, Jul 13, 2015 at 02:10:45PM +0200, Tomeu Vizoso wrote:
On 1 July 2015 at 19:38, Mark Brown [off-list ref] wrote:
quoted
On Wed, Jul 01, 2015 at 11:41:06AM +0200, Tomeu Vizoso wrote:
quoted
quoted
+static void tegra_max98090_get_dependencies(struct fwnode_handle *fwnode,
+                                         struct list_head *deps)
+{
+     add_dependency(fwnode, "nvidia,i2s-controller", deps);
+     add_dependency(fwnode, "nvidia,audio-codec", deps);
+}
quoted
Why is this all being open coded in an individual driver (we already
know about and manage all these dependencies in the core...)?  If we're
going to do this I'd expect the interface for specifying DT nodes to the
core to be changed to support this.
Are you thinking of changing drivers to acquire their resources
through Arnd's devm_probe (only that the resource table would have to
be in struct device_driver)?
https://lkml.kernel.org/g/4742258.TBitC3hVuO@wuerfel
No, I'm looking at how we already have all the "did all my dependencies
appear" logic in the core based on data provided by the drivers.

Attachments

Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help