Re: [PATCH 1/3] mfd: allow mfd_cell association with device tree node
From: Daniel Drake
Date: Mon Oct 03 2011 - 06:39:54 EST
On Mon, Oct 3, 2011 at 11:28 AM, Mark Brown
> I'd really expect that if we're adding stuff to the framework then it
> should be suitable for random drivers to use.
It is suitable. If other drivers would otherwise run into the data
reuse problem you have described, they can use the kmemdup solution
you have described.
> To be honest I don't
> really understand why you're changing the framework at all here, the
> child driver is entirely specific to the parent as far as I can see.
Because I'm trying to get devicetree-driven HDD LED support driven,
and Grant stated that doing it this way is a hard rule:
"What is a hard rule is that the code creating the children needs to
know what the binding is and populate the child's of_node
I also confirmed that extending the mfd_cell layer is exactly what
Grant was suggesting:
And Grant is undoubtedly a source of authority on device tree
So I seem to be stuck between two people giving me conflicting
requirements for merge of my work (which commenced in July, and has
already seen several discussions and rounds of patches). Any help
appreciated - I'm just trying to make a HDD LED blink.
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/