ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Behun <marek.behun@nic.cz>
To: ath10k@lists.infradead.org
Subject: QCA6174 SDIO support?
Date: Mon, 8 Jan 2018 01:28:51 +0100	[thread overview]
Message-ID: <20180108012851.389d37c7@nic.cz> (raw)

Hello,

we at CZ.NIC are trying the current ath10k driver with High Latency +
SDIO support (which was done by Silex Technology) on our board. The
supported chip, QCA9377, works, but we only have 1x1 MIMO boards with
this chip. We are trying to get it work with 8274B-SR (QCA6174)
( http://www.fn-link.com/a-b-g-n-ac-wi-fi-bt-module/8274b-sr.html )

There is already some code in sdio.c mentoining QCA6174, but there are
no nodes in ath10k_hw_params. Because QCA6174 is supported via PCI bus,
I tried to write the ath10k_hw_params node (see patch
http://blackhole.sk/~kabel/src/qca6174.patch ) but do not know if the
changes I did are enough, because the driver fails after loading
firmware.

And the firmware is another point: Does board-sdio.bin have to be
different from board.bin? Do we have to create this binary ourselves,
or should the 8274B-SR board manufacturer sent us one? (We didn't
receive anything from fn-link.)

Any information is good, please let us know even if you have NDA on
this and therefore cannot give any more information about this.

Thank you.

Marek Behun, CZ.NIC

_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k

             reply	other threads:[~2018-01-08  0:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-08  0:28 Marek Behun [this message]
2018-01-08  1:31 ` QCA6174 SDIO support? Sebastian Gottschall
2018-01-08  2:00   ` Marek Behun
2018-01-09  7:29     ` Sebastian Gottschall
2018-01-09  7:54     ` Alagu Sankar

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=20180108012851.389d37c7@nic.cz \
    --to=marek.behun@nic.cz \
    --cc=ath10k@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox