public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Bjorn Andersson <andersson@kernel.org>
To: agross@kernel.org, mka@chromium.org, krzk+dt@kernel.org,
	Bjorn Andersson <andersson@kernel.org>,
	swboyd@chromium.org, robh+dt@kernel.org,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-msm@vger.kernel.org, dianders@chromium.org
Cc: krzysztof.kozlowski+dt@linaro.org, konrad.dybcio@somainline.org
Subject: Re: (subset) [PATCH v24 1/2] arm64: dts: qcom: sc7180-trogdor: Add nodes for onboard USB hub
Date: Wed, 14 Sep 2022 22:37:01 -0500	[thread overview]
Message-ID: <166321302062.788007.6887378147525965852.b4-ty@kernel.org> (raw)
In-Reply-To: <20220722093238.v24.1.I7a1a6448d50bdd38e6082204a9818c59cc7a9bfd@changeid>

On Fri, 22 Jul 2022 09:32:44 -0700, Matthias Kaehlcke wrote:
> Add nodes for the onboard USB hub on trogdor devices. Remove the
> 'always-on' property from the hub regulator, since the regulator
> is now managed by the onboard_usb_hub driver.
> 
> For anyone using trogdor-based devices on Linux, it should be
> noted that this requires "CONFIG_USB_ONBOARD_HUB=y".
> 
> [...]

Applied, thanks!

[1/2] arm64: dts: qcom: sc7180-trogdor: Add nodes for onboard USB hub
      commit: a73dd03bb2e0287497f8fe9e221c332369e05fca
[2/2] arm64: dts: qcom: sc7280-herobrine: Add nodes for onboard USB hub
      commit: dc94156c6694e0ecee32870df94ed8fae07327ca

Best regards,
-- 
Bjorn Andersson <andersson@kernel.org>

      parent reply	other threads:[~2022-09-15  3:38 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-22 16:32 [PATCH v24 1/2] arm64: dts: qcom: sc7180-trogdor: Add nodes for onboard USB hub Matthias Kaehlcke
2022-07-22 16:32 ` [PATCH v24 2/2] arm64: dts: qcom: sc7280-herobrine: " Matthias Kaehlcke
2022-08-18 21:31 ` [PATCH v24 1/2] arm64: dts: qcom: sc7180-trogdor: " Doug Anderson
2022-09-06 22:02   ` Doug Anderson
2022-09-14 20:49     ` Matthias Kaehlcke
2022-09-15  3:37 ` Bjorn Andersson [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=166321302062.788007.6887378147525965852.b4-ty@kernel.org \
    --to=andersson@kernel.org \
    --cc=agross@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dianders@chromium.org \
    --cc=konrad.dybcio@somainline.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mka@chromium.org \
    --cc=robh+dt@kernel.org \
    --cc=swboyd@chromium.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