From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Raja Mani <rmani@qti.qualcomm.com>
Cc: linux-wireless@vger.kernel.org, ath10k@lists.infradead.org
Subject: Re: [PATCH 00/12] add ahb (qca4019) support
Date: Tue, 2 Feb 2016 13:19:58 +0200 [thread overview]
Message-ID: <87mvrjgy01.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <1453888473-2879-1-git-send-email-rmani@qti.qualcomm.com> (Raja Mani's message of "Wed, 27 Jan 2016 15:24:21 +0530")
Raja Mani <rmani@qti.qualcomm.com> writes:
> This patch series attempts to add ahb support (qca4019) in ath10k.
> All ahb related ops are grouped and kept in new file called ahb.c/ahb.h
> and will get compiled/linked to ath10k_pci.ko based on kernel config flag
> CONFIG_ATH10K_AHB flag. Most of function in pci.c file are reusable and
> called as it's without changing function name (ath10k_pci_*) in ahb.c.
>
> Still, some more work needs to be done in ath10k driver to make ahb
> functional (qca4019). Hence, i disabled device probing in ahb module
> for the time being. I'll post follow patch soon to enable it along
> with missing patches.
>
> The patch to update device tree bindings document with list of DT node
> attributes referred in this patch series is already committed in ath.git,
>
> https://patchwork.kernel.org/patch/8022221/
>
> Raja Mani (12):
> ath10k: make some of ath10k_pci_* func reusable
> ath10k: make ath10k_pci_read32/write32() ops more generic
> ath10k: pull reusable code from pci probe and remove for ahb
> ath10k: add basic skeleton to support ahb
> ath10k: include qca4019 register map table
> ath10k: add helper functions in ahb.c for reg rd/wr
> ath10k: add clock ctrl related functions in ahb
> ath10k: add reset ctrl related functions in ahb
> ath10k: add chip and bus halt logic in ahb
> ath10k: include irq related functions in ahb
> ath10k: add resource init and deinit in ahb
> ath10k: expose hif ops for ahb
Applied, thanks.
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
prev parent reply other threads:[~2016-02-02 11:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-27 9:54 [PATCH 00/12] add ahb (qca4019) support Raja Mani
2016-01-27 9:54 ` [PATCH 01/12] ath10k: make some of ath10k_pci_* func reusable Raja Mani
2016-01-27 9:54 ` [PATCH 02/12] ath10k: make ath10k_pci_read32/write32() ops more generic Raja Mani
2016-01-27 9:54 ` [PATCH 03/12] ath10k: pull reusable code from pci probe and remove for ahb Raja Mani
2016-01-27 9:54 ` [PATCH 04/12] ath10k: add basic skeleton to support ahb Raja Mani
2016-01-27 9:54 ` [PATCH 05/12] ath10k: include qca4019 register map table Raja Mani
2016-01-27 9:54 ` [PATCH 06/12] ath10k: add helper functions in ahb.c for reg rd/wr Raja Mani
2016-01-27 9:54 ` [PATCH 07/12] ath10k: add clock ctrl related functions in ahb Raja Mani
2016-01-27 9:54 ` [PATCH 08/12] ath10k: add reset " Raja Mani
2016-01-27 9:54 ` [PATCH 09/12] ath10k: add chip and bus halt logic " Raja Mani
2016-01-27 9:54 ` [PATCH 10/12] ath10k: include irq related functions " Raja Mani
2016-01-27 9:54 ` [PATCH 11/12] ath10k: add resource init and deinit " Raja Mani
2016-01-27 9:54 ` [PATCH 12/12] ath10k: expose hif ops for ahb Raja Mani
2016-02-02 11:19 ` Kalle Valo [this message]
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=87mvrjgy01.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=linux-wireless@vger.kernel.org \
--cc=rmani@qti.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