From: Andy Gross <andy.gross@linaro.org>
To: Bjorn Andersson <bjorn.andersson@linaro.org>
Cc: Stephen Boyd <stephen.boyd@linaro.org>,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH 5/5] arm64: dts: qcom: Collapse usb support into one node
Date: Tue, 23 May 2017 20:27:36 -0500 [thread overview]
Message-ID: <20170524012736.GA19546@hector.attlocal.net> (raw)
In-Reply-To: <20170518190308.GP12920@tuxbook>
On Thu, May 18, 2017 at 12:03:08PM -0700, Bjorn Andersson wrote:
> On Thu 26 Jan 16:47 PST 2017, Stephen Boyd wrote:
>
> > We currently have three device nodes for the same USB hardware
> > block, as evident by the reuse of the same reg address multiple
> > times. Now that the chipidea driver fully supports OTG with the
> > MSM wrapper we can collapse all these nodes into one USB device
> > node, reflecting the true nature of the hardware.
> >
> > Signed-off-by: Stephen Boyd <stephen.boyd@linaro.org>
>
> Acked-by: Bjorn Andersson <bjorn.andersson@linaro.org>
>
> This still applies and with some defconfig updates seems to make USB
> work again (thoroughly tested though). @Andy, would you mind picking
> this up.
Yeah I'll queue this up.
Regards,
Andy
prev parent reply other threads:[~2017-05-24 1:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-27 0:47 [PATCH 0/5] Updated qcom dts for new USB driver Stephen Boyd
2017-01-27 0:47 ` [PATCH 1/5] ARM: dts: qcom: Remove s4/5vs1,2 from RPM pm8941 control Stephen Boyd
2017-05-24 19:18 ` Bjorn Andersson
2017-01-27 0:47 ` [PATCH 2/5] ARM: dts: qcom: add charger otg regulator Stephen Boyd
2017-01-27 0:47 ` [PATCH 3/5] ARM: dts: qcom-msm8974: Add HS usb node and OTG detection mechanisms Stephen Boyd
2017-01-27 0:47 ` [PATCH 4/5] ARM: dts: qcom-apq8064: Collapse usb support into one node Stephen Boyd
2017-02-28 23:50 ` John Stultz
2017-01-27 0:47 ` [PATCH 5/5] arm64: dts: qcom: " Stephen Boyd
2017-05-18 19:03 ` Bjorn Andersson
2017-05-24 1:27 ` Andy Gross [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=20170524012736.GA19546@hector.attlocal.net \
--to=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stephen.boyd@linaro.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