From: Sujeev Dias <sdias@codeaurora.org>
To: Pavel Machek <pavel@ucw.cz>
Cc: Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Arnd Bergmann <arnd@arndb.de>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
Tony Truong <truong@codeaurora.org>
Subject: Re: [PATCH v1 1/4] mhi_bus: core: Add support for MHI host interface
Date: Thu, 3 May 2018 20:05:04 -0700 [thread overview]
Message-ID: <d7c9fdd2-6078-503a-517a-f20dd6d8098f@codeaurora.org> (raw)
In-Reply-To: <20180503192110.bjd46afhe2ein3qm@devuan>
Hi Pavel
On 05/03/2018 12:21 PM, Pavel Machek wrote:
> Hi!
>
>> MHI Host Interface is a communication protocol to be used by the host
>> to control and communcate with modem over a high speed peripheral bus.
>> This module will allow host to communicate with external devices that
>> support MHI protocol.
> I have Motorola Droid 4 cellphone here, with Qualcomm GSM modem. But
> it talks over serial line and USB. I guess MHI is not applicable to my
> hardware?
>
MHI is for PCIe based modem, in any case I can't comment about
commercial devices.
>> +MHI Devices
>> +-----------
>> +Logical device that bind to maximum of two physical MHI channels. Once MHI is in
>> +powered on state, each supported channel by controller will be allocated as a
>> +mhi_device.
> What kind of protocol is running over MHI? I guess its not AT
> commands. QMI? Or something entirely different?
All modem services between external modem and host go over MHI.
So QMI, AT, all other data and control services go thru MHI host driver.
> Pavel
Thanks
Sujeev
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2018-05-04 3:05 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-27 2:23 MHI initial design review Sujeev Dias
2018-04-27 2:23 ` [PATCH v1 1/4] mhi_bus: core: Add support for MHI host interface Sujeev Dias
2018-04-27 7:22 ` Greg Kroah-Hartman
2018-04-28 14:28 ` Sujeev Dias
2018-04-28 15:50 ` Greg Kroah-Hartman
2018-04-27 7:23 ` Greg Kroah-Hartman
2018-04-27 12:18 ` Arnd Bergmann
2018-04-28 16:08 ` Sujeev Dias
2018-04-28 0:28 ` kbuild test robot
2018-04-28 2:52 ` kbuild test robot
2018-05-03 19:21 ` Pavel Machek
2018-05-04 3:05 ` Sujeev Dias [this message]
2018-06-22 23:03 ` Randy Dunlap
2018-04-27 2:23 ` [PATCH v1 2/4] mhi_bus: controller: MHI support for QCOM modems Sujeev Dias
2018-04-27 11:32 ` Arnd Bergmann
2018-04-28 15:40 ` Sujeev Dias
2018-04-28 3:05 ` kbuild test robot
2018-04-28 3:12 ` kbuild test robot
2018-04-27 2:23 ` [PATCH v1 3/4] mhi_bus: dev: netdev: add network interface driver Sujeev Dias
2018-04-27 11:19 ` Arnd Bergmann
2018-04-28 15:25 ` Sujeev Dias
2018-04-27 2:23 ` [PATCH v1 4/4] mhi_bus: dev: uci: add user space " Sujeev Dias
2018-04-27 11:36 ` Arnd Bergmann
2018-04-28 1:03 ` kbuild test robot
2018-04-28 5:16 ` [PATCH] mhi_bus: dev: uci: fix semicolon.cocci warnings kbuild test robot
2018-04-28 5:16 ` [PATCH v1 4/4] mhi_bus: dev: uci: add user space interface driver kbuild test robot
2018-07-09 20:08 ` MHI code review Sujeev Dias
2018-07-09 20:08 ` [PATCH v2 1/7] mhi_bus: core: initial checkin for modem host interface bus driver Sujeev Dias
2018-07-09 20:50 ` Greg Kroah-Hartman
2018-07-09 20:52 ` Greg Kroah-Hartman
2018-07-10 6:36 ` Greg Kroah-Hartman
2018-07-11 19:30 ` Rob Herring
2018-08-09 18:39 ` Randy Dunlap
2018-07-09 20:08 ` [PATCH v2 2/7] mhi_bus: core: add power management support Sujeev Dias
2018-07-09 20:08 ` [PATCH v2 3/7] mhi_bus: core: add support for data transfer Sujeev Dias
2018-07-10 6:29 ` Greg Kroah-Hartman
2018-07-09 20:08 ` [PATCH v2 4/7] mhi_bus: core: add support for handling ioctl cmds Sujeev Dias
2018-07-09 20:08 ` [PATCH v2 5/7] mhi_bus: core: add support to get external modem time Sujeev Dias
2018-07-11 19:32 ` Rob Herring
2018-08-09 20:17 ` Randy Dunlap
2018-07-09 20:08 ` [PATCH v2 6/7] mhi_bus: controller: MHI support for QCOM modems Sujeev Dias
2018-07-11 19:36 ` Rob Herring
2018-07-09 20:08 ` [PATCH v2 7/7] mhi_bus: dev: uci: add user space interface driver Sujeev Dias
2019-04-30 15:10 ` MHI code review Daniele Palmas
2019-06-12 17:54 ` Sujeev Dias
2019-06-12 20:58 ` Daniele Palmas
2019-06-12 18:00 ` Sujeev Dias
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=d7c9fdd2-6078-503a-517a-f20dd6d8098f@codeaurora.org \
--to=sdias@codeaurora.org \
--cc=arnd@arndb.de \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=truong@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).