From: Arnd Bergmann <arnd@arndb.de>
To: Kalle Valo <kvalo@qca.qualcomm.com>
Cc: devicetree@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: ath10k: calibration data through Device Tree?
Date: Thu, 02 Oct 2014 15:27:53 +0200 [thread overview]
Message-ID: <3548219.ad4Qe1WtGp@wuerfel> (raw)
In-Reply-To: <87tx3mmx4s.fsf@kamboji.qca.qualcomm.com>
On Thursday 02 October 2014 16:14:43 Kalle Valo wrote:
> Hi Device Tree gurus,
>
> ath10k is a wireless driver for Qualcomm Atheros 802.11ac hardware and
> located in drivers/net/wireless/ath/ath10k/. Currently it only supports
> PCI devices.
>
> Some of the devices store the calibration data to the host flash and the
> bootloader reads the data from the flash. And now we need a method to
> deliver the calibration data from bootloader to ath10k. Basically our
> requirements are:
>
> * ath10k must support any number of radios (one radio per PCI device).
>
> * The calibration data is now 2116 bytes, in the future it might be
> longer. The data is unique for each radio and is created at the
> factory.
>
> * ath10k must be able to reliably map the PCI device (=radio) to the
> correct calibration data. Maybe with using PCI bus and slot numbers?
>
> We have been trying to find similar cases from other drivers but no
> luck. Basically my question is how to do this properly with Device Tree?
> Especially how to map the calibration data to correct PCI device? Are
> there any examples which would help us to implement this?
When you know the PCI bus/device/function ID of the device, you can put
a device node in the dts file that corresponds to the PCI dev, and you
can find the of_node pointer from pci_dev->dev.of_node. 2116 is probably
ok to put into a DT property of that device directly.
Arnd
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2014-10-02 13:28 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 [this message]
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
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=3548219.ad4Qe1WtGp@wuerfel \
--to=arnd@arndb.de \
--cc=ath10k@lists.infradead.org \
--cc=devicetree@vger.kernel.org \
--cc=kvalo@qca.qualcomm.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