From: David Miller <davem@davemloft.net>
To: manivannan.sadhasivam@linaro.org
Cc: kvalo@codeaurora.org, bjorn.andersson@linaro.org,
hemantk@codeaurora.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, clew@codeaurora.org,
gregkh@linuxfoundation.org, netdev@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Add QRTR MHI client driver
Date: Thu, 07 May 2020 13:21:36 -0700 (PDT) [thread overview]
Message-ID: <20200507.132136.2063178280963548327.davem@davemloft.net> (raw)
In-Reply-To: <20200507125306.32157-1-manivannan.sadhasivam@linaro.org>
From: Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>
Date: Thu, 7 May 2020 18:23:04 +0530
> Here is the series adding MHI client driver support to Qualcomm IPC router
> protocol. MHI is a newly added bus to kernel which is used to communicate to
> external modems over a physical interface like PCI-E. This driver is used to
> transfer the QMI messages between the host processor and external modems over
> the "IPCR" channel.
>
> For QRTR, this driver is just another driver acting as a transport layer like
> SMD.
>
> Currently this driver is needed to control the QCA6390 WLAN device from ath11k.
> The ath11k MHI controller driver will take care of booting up QCA6390 and
> bringing it to operating state. Later, this driver will be used to transfer QMI
> messages over the MHI-IPCR channel.
>
> The second patch of this series removes the ARCH_QCOM dependency for QRTR. This
> is needed because the QRTR driver will be used with x86 machines as well to talk
> to devices like QCA6390.
Series applied to net-next, thanks.
prev parent reply other threads:[~2020-05-07 20:21 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-07 12:53 [PATCH v2 0/2] Add QRTR MHI client driver Manivannan Sadhasivam
2020-05-07 12:53 ` [PATCH v2 1/2] net: qrtr: Add MHI transport layer Manivannan Sadhasivam
2020-05-07 12:53 ` [PATCH v2 2/2] net: qrtr: Do not depend on ARCH_QCOM Manivannan Sadhasivam
2020-05-07 20:21 ` David Miller [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=20200507.132136.2063178280963548327.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=bjorn.andersson@linaro.org \
--cc=clew@codeaurora.org \
--cc=gregkh@linuxfoundation.org \
--cc=hemantk@codeaurora.org \
--cc=kvalo@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=netdev@vger.kernel.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).