ATH10K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Erik Stromdahl <erik.stromdahl@gmail.com>
To: Akesh M Chacko <akesh.chacko@vvdntech.in>
Cc: "Valo, Kalle" <kvalo@qca.qualcomm.com>,
	Ann Lo <annlo.tech@gmail.com>,
	"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Driver support for QCA6174 chip using SDIO interface
Date: Wed, 22 Feb 2017 21:58:57 +0100	[thread overview]
Message-ID: <13839ca7-e43e-8475-04de-8c705c4e3ee2@gmail.com> (raw)
In-Reply-To: <CAHNpzpeao2rT8JJ5rSALHknrkFHniixJftGLTnUxcd7RtoYdtQ@mail.gmail.com>



On 2017-02-21 12:26, Akesh M Chacko wrote:
> hi,
> I'm following your patch for adding SDIO support for QCA6174. Is the
> firmware image for PCIe and SDIO interface are same?
> If they are different, from where can i find the firmware image for
> SDIO interface support in QCA6174A-3 v3.2.
>
The firmware is not the same for sdio. You will need to obtain the firmware
from the module vendor and convert it into ath10k format with ath10k-fwencoder.

You need the tool qca-swiss-army-knife for this:

https://github.com/qca/qca-swiss-army-knife.git

Below is a script I have used when generating fw for my QCA9377 board:

### START ###
#! /bin/bash

ENCODER="./tools/scripts/ath10k/ath10k-fwencoder"

API_VER=5
HTT_OP_VERSION="tlv"
WMI_OP_VERSION="tlv"
FW="silex-SX-SDCAC-2830-SP/qwlan30.bin"
OTP="silex-SX-SDCAC-2830-SP/otp30.bin"
FEATURES="ignore-otp-result"

$ENCODER --create --otp=$OTP --firmware=$FW \
--set-wmi-op-version=$WMI_OP_VERSION \
--set-htt-op-version=$HTT_OP_VERSION \
--set-fw-api=$API_VER --features=$FEATURES

mv firmware-5.bin silex-SX-SDCAC-2830-SP/firmware-sdio-5.bin
### END ###

> Thanks & Regards
> Akesh M Chacko
>
>
> On Tue, Jan 31, 2017 at 5:04 PM, Akesh M Chacko
> <akesh.chacko@vvdntech.in> wrote:
>> Thanks for sharing the patches,
>> Our custom board is under assembly stage, once we have the board, will
>> test it and let u know
>> Thanks & Regards
>> Akesh M Chacko
>> Cell : +91 9567084416| Skype: akesh.vvdn | mail : akesh.chacko@vvdntech.in
>>
>>
>> On Mon, Jan 30, 2017 at 2:46 AM, Erik Stromdahl
>> <erik.stromdahl@gmail.com> wrote:
>>> If you are interested in trying the latest version of the sdio code
>>> you can clone the below repo:
>>>
>>> https://github.com/erstrom/linux-ath.git
>>>
>>> I have just pushed some updates for QCA9377 SDIO (that might work with
>>> QCA6174 chipsets as well).
>>>
>>> I will do some more testing of this code during the weeks to come.
>>>
>>> If you could try it out and give me feedback it would be great!
>>>
>>>
>>> On 2017-01-27 16:36, Valo, Kalle wrote:
>>>>
>>>> Akesh M Chacko <akesh.chacko@vvdntech.in> writes:
>>>>
>>>>> We are using QCA6174 chip on our embedded platform using SDIO
>>>>> interface. could you please help us to get the SDIO support for
>>>>> QCA6174 driver.
>>>>
>>>>
>>>> Erik Stromdahl is working on adding SDIO support to ath10k:
>>>>
>>>> https://patchwork.kernel.org/patch/9516477/
>>>>
>>>> But it's still WIP.
>>>>
>>>

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

  reply	other threads:[~2017-02-22 20:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-21 14:22 Driver support for QCA6174 chip using SDIO interface Akesh M Chacko
2017-01-27 15:36 ` Valo, Kalle
2017-01-29 21:16   ` Erik Stromdahl
2017-01-31 11:34     ` Akesh M Chacko
2017-02-21 11:26       ` Akesh M Chacko
2017-02-22 20:58         ` Erik Stromdahl [this message]
2017-03-01  5:52           ` Akesh M Chacko
2017-03-01  6:25             ` Erik Stromdahl
2017-03-04  4:41               ` Akesh M Chacko
2017-03-09  7:39               ` Valo, Kalle
2017-05-12  0:20     ` Ann Lo
2017-05-12 14:51       ` Erik Stromdahl
2017-05-12 17:30         ` Ann Lo
2017-05-15 17:50         ` Adrian Chadd
2017-05-16 12:59           ` Erik Stromdahl
2017-05-16  7:14         ` Kalle Valo
2017-05-16 13:13           ` Erik Stromdahl
2017-05-17  9:32             ` 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=13839ca7-e43e-8475-04de-8c705c4e3ee2@gmail.com \
    --to=erik.stromdahl@gmail.com \
    --cc=akesh.chacko@vvdntech.in \
    --cc=annlo.tech@gmail.com \
    --cc=ath10k@lists.infradead.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