A question about generated phandle during dtb=>dts conversion

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Hello, all
I extracted a dtb file from qemu execution (arm virt machine) and converted
the dtb file to dts file using dtc.
But for some node that is referenced by other nodes, the phandle is
generated like ?phandle = <0x8000>? as shown below.

apb-pclk {
        phandle = <0x8000>;
        clock-output-names = "clk24mhz";
        clock-frequency = <0x16e3600>;
        #clock-cells = <0x00>;
        compatible = "fixed-clock";

And another node is using this phandle like this. (the clocks is the phandle
for the apb-pclk above.)

pl061@9030000 {
        phandle = <0x8003>;
        clock-names = "apb_pclk";
        clocks = <0x8000>;
        interrupts = <0x00 0x07 0x04>;
        #gpio-cells = <0x02>;
        compatible = "arm,pl061\0arm,primecell";
        reg = <0x00 0x9030000 0x00 0x1000>;

When I convert the dts back to the dtb, dtc doesn?t understand the phandle
and complains that it is not a phandle referenece.

dts.dts:276.3-21: Warning (clocks_property): /pl061@9030000:clocks: cell 0
is not a phandle reference

I?ve checked event with this warning, the phandle reference is being
preserved through out the procedure.
So, if I want to extract a dtb and convert it to dts, edit some and convert
it back to dtb, how can I prevent this kind of phandle warning? 
And why doesn't dtc add labels to the referenced nodes and let other nodes
use that label as phandle?

Thank you!

Chan Kim

[Index of Archives]     [Device Tree]     [Device Tree Spec]     [Linux Driver Backports]     [Video for Linux]     [Linux USB Devel]     [Linux Audio Users]     [Linux Kernel]     [Linux SCSI]     [Yosemite Backpacking]

  Powered by Linux