From: Kalle Valo <kvalo@qca.qualcomm.com>
To: devicetree@vger.kernel.org
Cc: ath10k@lists.infradead.org
Subject: ath10k: calibration data through Device Tree?
Date: Thu, 2 Oct 2014 16:14:43 +0300 [thread overview]
Message-ID: <87tx3mmx4s.fsf@kamboji.qca.qualcomm.com> (raw)
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?
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
WARNING: multiple messages have this Message-ID (diff)
From: Kalle Valo <kvalo-A+ZNKFmMK5xy9aJCnZT0Uw@public.gmane.org>
To: devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: ath10k-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org
Subject: ath10k: calibration data through Device Tree?
Date: Thu, 2 Oct 2014 16:14:43 +0300 [thread overview]
Message-ID: <87tx3mmx4s.fsf@kamboji.qca.qualcomm.com> (raw)
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?
--
Kalle Valo
--
To unsubscribe from this list: send the line "unsubscribe devicetree" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2014-10-02 13:15 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-10-02 13:14 Kalle Valo [this message]
2014-10-02 13:14 ` ath10k: calibration data through Device Tree? Kalle Valo
2014-10-02 13:27 ` Arnd Bergmann
2014-10-02 13:27 ` Arnd Bergmann
2014-10-02 13:47 ` Kalle Valo
2014-10-02 13:47 ` Kalle Valo
2014-10-02 14:19 ` Arnd Bergmann
2014-10-02 14:19 ` Arnd Bergmann
2014-10-02 14:55 ` Kalle Valo
2014-10-02 14:55 ` Kalle Valo
2014-10-02 15:58 ` Arnd Bergmann
2014-10-02 15:58 ` Arnd Bergmann
2014-10-02 13:29 ` Mark Rutland
2014-10-02 13:29 ` Mark Rutland
2014-10-02 13:44 ` Kalle Valo
2014-10-02 13:44 ` Kalle Valo
2014-10-02 15:07 ` Mark Rutland
2014-10-02 15:07 ` Mark Rutland
2014-10-02 19:05 ` Andy Lutomirski
2014-10-02 19:05 ` Andy Lutomirski
2014-10-02 19:28 ` Adrian Chadd
2014-10-02 19:28 ` Adrian Chadd
2014-10-02 19:35 ` Andy Lutomirski
2014-10-02 19:35 ` Andy Lutomirski
2014-10-07 16:44 ` Kalle Valo
2014-10-07 16:44 ` Kalle Valo
2014-10-17 12:25 ` Kumar Gala
2014-10-17 12:25 ` Kumar Gala
2014-10-22 12:02 ` Kalle Valo
2014-10-22 12:02 ` Kalle Valo
2014-10-03 15:29 ` Arnd Bergmann
2014-10-03 15:29 ` Arnd Bergmann
2014-10-03 16:24 ` Andy Lutomirski
2014-10-03 16:24 ` Andy Lutomirski
2014-10-03 16:25 ` Mark Rutland
2014-10-03 16:25 ` Mark Rutland
2014-10-03 16:42 ` Arnd Bergmann
2014-10-03 16:42 ` Arnd Bergmann
2014-10-03 16:54 ` Andy Lutomirski
2014-10-03 16:54 ` Andy Lutomirski
2014-10-03 17:21 ` Adrian Chadd
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=87tx3mmx4s.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=devicetree@vger.kernel.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.