ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Sven Eckelmann <seckelmann@datto.com>
To: ath11k@lists.infradead.org
Cc: Rob Herring <robh@kernel.org>,
	Anilkumar Kolli <akolli@codeaurora.org>,
	Sricharan R <sricharan@codeaurora.org>,
	Kalle Valo <kvalo@codeaurora.org>,
	Bjorn Andersson <bjorn.andersson@linaro.org>
Subject: Re: [PATCH] ath11k: add driver [q6_rproc DTS property)
Date: Wed, 10 Apr 2019 09:33:56 +0200	[thread overview]
Message-ID: <2317190.UUFvc8mrDS@bentobox> (raw)
In-Reply-To: <1698032.ruk2XY5Ikj@bentobox>


[-- Attachment #1.1: Type: text/plain, Size: 2707 bytes --]

On Monday, 8 April 2019 19:42:24 CEST Sven Eckelmann wrote:
[...]
> What is this q6_rproc DTS property (and why doesn't have it a qcom, prefix and 
> not just called qcom,rproc)? I cannot find a public use of this and there also 
> doesn't seem to be documentation for it. Still it is required to bring up the 
> device without IPQ_SUBSYSTEM_RESTART (which is not available in the upstream 
> kernel) but with remoteproc.
> 
> The first reference I could find this in your internal linux-msm [1] was also 
> in this driver. There were also some function named similar in the q6v6 adsp/
> q6v5 wcss driver [2] but no actual use in a dts or documentation. A wcss pil 
> driver for remoteproc seems to be upstream now [3] but it isn't used 
> anywhere.

I just saw the commit 

    Subject: ath11k: add qmi API support and rproc_boot for Q6
    
    rproc_boot() is used to power up the Q6 remote processor.
    Q6 has the QMI server running. on Q6 power up 'qrtr-cfg'
    and 'qrtr-ns' applications will send the .new_server()
    notification to ath11k driver.
      - qrtr source 'https://github.com/andersson/qrtr'
    
    Load the BDF/cal-data and share the CE config to Q6 target
    using the below list of QMI messages.
    
    QMI Client [ATH11K]             QMI server [Q6 FW]
            <-----  ATH11K_QMI_EVENT_SERVER_ARRIVE  ----
            ---- QMI_WLANFW_IND_REGISTER_REQ_V01 ----->
            <---- QMI_WLANFW_IND_REGISTER_RESP_V01 ----
            ---- QMI_WLANFW_HOST_CAP_REQ_V01 ---->
            <---- QMI_WLFW_HOST_CAP_RESP_V01 ----
            <---- ATH11K_QMI_EVENT_REQUEST_MEM ----
            ---- QMI_WLANFW_RESPOND_MEM_REQ_V01 ---->
            <---- QMI_WLANFW_RESPOND_MEM_RESP_V01 ----
            <---- ATH11K_QMI_EVENT_FW_MEM_READY ----
            ---- QMI_WLANFW_CAP_REQ_V01 ---->
            <---- QMI_WLANFW_CAP_RESP_V01 ----
            ---- QMI_WLANFW_BDF_DOWNLOAD_REQ_V01 ---->
            <---- QMI_WLANFW_BDF_DOWNLOAD_RESP_V01 ----
            ---- QMI_WLANFW_BDF_DOWNLOAD_REQ_V01 ---->
            <---- QMI_WLANFW_BDF_DOWNLOAD_RESP_V01 ----
            ---- QMI_WLANFW_M3_INFO_REQ_V01 ---->
            <---- QMI_WLANFW_M3_INFO_RESP_V01 ----
            <---- ATH11K_QMI_EVENT_FW_READY ----
            ---- QMI_WLANFW_WLAN_CFG_REQ_V01 ---->
            <---- QMI_WLANFW_WLAN_CFG_RESP_V01 ----
            ---- QMI_WLANFW_WLAN_MODE_REQ_V01 ---->
            <---- QMI_WLANFW_WLAN_MODE_RESP_V01 ----

This one basically removes the support for the QCA 4.4 kernel with 
IPQ_SUBSYSTEM_RESTART - which is the one we tried to use in the past. What is 
now the correct one to use and where can I find the info what qcom,rproc 
refers to in the DTS?

Kind regards,
	Sven

[-- Attachment #1.2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

[-- Attachment #2: Type: text/plain, Size: 146 bytes --]

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

      reply	other threads:[~2019-04-10  7:34 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-08 17:42 [PATCH] ath11k: add driver [q6_rproc DTS property) Sven Eckelmann
2019-04-10  7:33 ` Sven Eckelmann [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=2317190.UUFvc8mrDS@bentobox \
    --to=seckelmann@datto.com \
    --cc=akolli@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=bjorn.andersson@linaro.org \
    --cc=kvalo@codeaurora.org \
    --cc=robh@kernel.org \
    --cc=sricharan@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