From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Kumar Gala <galak@codeaurora.org>
Cc: Mark Rutland <mark.rutland@arm.com>,
devicetree@vger.kernel.org, Adrian Chadd <adrian@freebsd.org>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>,
Andy Lutomirski <luto@amacapital.net>
Subject: Re: ath10k: calibration data through Device Tree?
Date: Wed, 22 Oct 2014 15:02:30 +0300 [thread overview]
Message-ID: <87tx2ws46h.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <F0D1326B-4716-4897-8259-1591B64EB55C@codeaurora.org> (Kumar Gala's message of "Fri, 17 Oct 2014 14:25:01 +0200")
Hi Kumar,
Kumar Gala <galak@codeaurora.org> 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
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-10-22 12:03 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 13:14 ath10k: calibration data through Device Tree? Kalle Valo
2014-10-02 13:27 ` Arnd Bergmann
2014-10-02 13:47 ` Kalle Valo
2014-10-02 14:19 ` Arnd Bergmann
2014-10-02 14:55 ` Kalle Valo
2014-10-02 15:58 ` Arnd Bergmann
2014-10-02 13:29 ` Mark Rutland
2014-10-02 13:44 ` Kalle Valo
2014-10-02 15:07 ` Mark Rutland
2014-10-02 19:05 ` Andy Lutomirski
2014-10-02 19:28 ` Adrian Chadd
2014-10-02 19:35 ` Andy Lutomirski
2014-10-07 16:44 ` Kalle Valo
2014-10-17 12:25 ` Kumar Gala
2014-10-22 12:02 ` Kalle Valo [this message]
2014-10-03 15:29 ` Arnd Bergmann
2014-10-03 16:24 ` Andy Lutomirski
2014-10-03 16:25 ` Mark Rutland
2014-10-03 16:42 ` Arnd Bergmann
2014-10-03 16:54 ` Andy Lutomirski
2014-10-03 17:21 ` Adrian Chadd
-- strict thread matches above, loose matches on Subject: below --
2014-10-02 13:05 Kalle Valo
2014-10-02 13:09 ` Kalle Valo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87tx2ws46h.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=adrian@freebsd.org \
--cc=ath10k@lists.infradead.org \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=luto@amacapital.net \
--cc=mark.rutland@arm.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox