On Thu, Mar 25, 2010 at 10:36 AM, Timur Tabi <ti...@freescale.com> wrote:
> Grant Likely wrote:
>> On Thu, Mar 25, 2010 at 9:29 AM, Mitch Bradley <w...@firmworks.com> wrote:
>>> It seems to me that there are plausible use cases for both direct-inclusion
>>> and indirection. I don't see any real problems with either, so I would vote
>>> for specifying both alternatives.
>>
>> Ugh. Then this one driver would need to implement both binding for
>> little, if any, actual benefit.
>
> Although I agree that I don't like supporting both bindings, we could
> encapsulate the locating of the firmware node in a function. The function
> will first look for a child firmware node, and if it doesn't find it, look
> for a fsl,firmware property. It will return a pointer to the firmware node
> regardless.
Wait... After eating dinner and mulling on it a bit, I think I've
changed my mind. I have no objections left if you do it the way Mitch
suggests with one minor change:
diff --git a/Documentation/powerpc/dts-bindings/fsl/cpm_qe/qe.txt
b/Documentation/powerpc/dts-bindings/fsl/cpm_qe/qe.txt
index 6e37be1..d9d6431 100644
--- a/Documentation/powerpc/dts-bindings/fsl/cpm_qe/qe.txt
+++ b/Documentation/powerpc/dts-bindings/fsl/cpm_qe/qe.txt
- fsl,qe-num-riscs: define how many RISC engines the QE has.
- fsl,qe-num-snums: define how many serial number(SNUM) the QE can use for the
threads.
+- fsl,firmware:
+ Usage: Optional.
+ Value type: <prop-encoded-array>, encoded array of bytes
+ Definition: Contains the QUICC engine firmware blob.
[plus any other properties needed for firmware metadata]
+- fsl,firmware-phandle:
+ Usage: Required if fsl,firmware property is not present.
+ Value type: <phandle>
+ Definition: Points to another fsl,qe node that has the
fsl,firmware property.
Recommended properties
- brg-frequency : the internal clock source frequency for baud-rate
[...]
+Example:
+ qe1: q...@e0080000 {
+ compatible = "fsl,qe";
+ fsl,firmware = /bininc/("firmware-blob.bin"); /* Or
squirted in by firmware */
+ ...
+ }
+
+ q...@e0090000 {
+ compatible = "fsl,qe";
+ fsl,firmware-phandle = <&qe1>;
+ ...
+ }
Putting the blob into just one of the qe nodes keeps everything nicely
contained with the device it actually applies to. No debates about
the best place to put device firmware blobs or new compatible values,
and it is applicable to any device where firmware needs to be passed
via the tree.
g.
_______________________________________________
Linuxppc-dev mailing list
Linuxppc-dev@lists.ozlabs.org
https://lists.ozlabs.org/listinfo/linuxppc-dev
