From: Stephen Boyd <sboyd@codeaurora.org>
To: Neil Armstrong <narmstrong@baylibre.com>,
balbi@kernel.org, gregkh@linuxfoundation.org
Cc: linux-kernel@vger.kernel.org, linux-usb@vger.kernel.org,
"linux-arm-msm@vger.kernel.org" <linux-arm-msm@vger.kernel.org>
Subject: Re: [PATCH 0/2] usb: phy: Add support for the Qualcomm HSIC USB PHY
Date: Fri, 17 Jun 2016 09:39:56 -0700 [thread overview]
Message-ID: <576427DC.9010906@codeaurora.org> (raw)
In-Reply-To: <1466159119-20310-1-git-send-email-narmstrong@baylibre.com>
On 06/17/2016 03:25 AM, Neil Armstrong wrote:
> In order to support the Qualcomm MDM9615 in the Sierra Wireless WP8548
> Modules, add the Qualcomm HSIC USB PHY used inside the MDM9615 SoC.
>
> This patchset is part of a global SoC + Module + Board support for the
> Sierra Wireless mangOH Board support with the WP8548 module.
>
>
I've been working on an hsic driver for apq8074 which matches the same
hardware. I was going to send it out this week but got dragged down into
the HS phy part of it and fixing all the OTG handling. I'd prefer we
don't go down the route of your patches which ioremap the controller
address space in the phy driver. Instead we should use the ULPI bus that
was recently introduced. Care to take my patches for a spin[1]? I'll Cc
you on them once I send them out, which should be very soon.
[1]
https://git.linaro.org/people/stephen.boyd/linux.git/shortlog/refs/heads/usb-hsic-8074
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
next parent reply other threads:[~2016-06-17 16:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1466159119-20310-1-git-send-email-narmstrong@baylibre.com>
2016-06-17 16:39 ` Stephen Boyd [this message]
2016-06-20 9:21 ` [PATCH 0/2] usb: phy: Add support for the Qualcomm HSIC USB PHY Neil Armstrong
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=576427DC.9010906@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=balbi@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=narmstrong@baylibre.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;
as well as URLs for NNTP newsgroup(s).