devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: Tamizh Chelvam <tamizhr@codeaurora.org>
Cc: ath10k@lists.infradead.org, devicetree@vger.kernel.org,
	linux-wireless@vger.kernel.org,
	Tamizh Chelvam <tamizhr@codeaurora.org>
Subject: Re: [PATCHv2 1/2] dt-bindings: ath10k: Add new dt entries to identify coex support
Date: Tue, 11 Feb 2020 14:23:26 +0000 (UTC)	[thread overview]
Message-ID: <20200211142326.546B4C433A2@smtp.codeaurora.org> (raw)
In-Reply-To: <1580152736-18654-1-git-send-email-tamizhr@codeaurora.org>

Tamizh Chelvam <tamizhr@codeaurora.org> wrote:

> This adds new dt entries qcom,coexist-support and qcom,coexist-gpio-pin
> which will be used by ath10k driver to identify coex support
> of a hardware and notify wifi firmware the gpio pin number.
> This pin number information is needed for the hardware QCA4019.
> 
> Signed-off-by: Tamizh Chelvam <tamizhr@codeaurora.org>
> Reviewed-by: Rob Herring <robh@kernel.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>

2 patches applied to ath-next branch of ath.git, thanks.

7354de9c6e2c dt-bindings: ath10k: Add new dt entries to identify coex support
9f83993e1a92 ath10k: Add support to read btcoex related data from DT

-- 
https://patchwork.kernel.org/patch/11353153/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

      parent reply	other threads:[~2020-02-11 14:23 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-27 19:18 [PATCHv2 1/2] dt-bindings: ath10k: Add new dt entries to identify coex support Tamizh Chelvam
2020-01-27 19:18 ` [PATCHv2 2/2] ath10k: Add support to read btcoex related data from DT Tamizh Chelvam
2020-02-05 17:49 ` [PATCHv2 1/2] dt-bindings: ath10k: Add new dt entries to identify coex support Rob Herring
2020-02-11 14:23 ` 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=20200211142326.546B4C433A2@smtp.codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath10k@lists.infradead.org \
    --cc=devicetree@vger.kernel.org \
    --cc=linux-wireless@vger.kernel.org \
    --cc=tamizhr@codeaurora.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;
as well as URLs for NNTP newsgroup(s).