Re: ath10k: calibration data through Device Tree?

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

 




Hi Kumar,

Kumar Gala <galak@xxxxxxxxxxxxxx> writes:

> As Arnd mentioned you would have something like:
>
> pci {   
>         pcie@0 {
>                 reg = <0 0 0 0 0>; 
>                 #interrupt-cells = <1>;
>                 #size-cells = <2>;
>                 #address-cells = <3>;
>                 device_type = "pci";
>
>                 ath10k@0,0 {
>                         reg = <0x0000 0x0 0x0 0x0 0x0>;
>                         device_type = "pci";
>                         qcom,ath10k-calibration-data = [ 01 03 04 05 06 … ];
>                 };      
>         };
> };
>
> On the driver side you can do something like:
>
> 	struct device_node *np;
>
> 	np = pci_device_to_OF_node(dev);
>
> than you can do normal OF calls on ‘np’.

Ah, now I understand how this is supposed to work. Thank you very much
for providing an example.

-- 
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html




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