From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Jeffrey Hugo <jeffrey.l.hugo@gmail.com>
Cc: agross@kernel.org, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [RFC PATCH 0/4] Enable msm8998 bluetooth
Date: Fri, 18 Oct 2019 10:05:32 -0700 [thread overview]
Message-ID: <20191018170532.GC4500@tuxbook-pro> (raw)
In-Reply-To: <20191017221843.8130-1-jeffrey.l.hugo@gmail.com>
On Thu 17 Oct 15:18 PDT 2019, Jeffrey Hugo wrote:
> This series enables bluetooth on the msm8998 platforms. However,
> without fixes under discussion [1] and [2], the init process will fail,
> leaving bluetooth non-functional. Perhaps it is best to wait until the
> dependencies meet acceptance before taking this series.
>
> [1] - https://lkml.org/lkml/2019/10/17/599
> [2] - https://lkml.org/lkml/2019/10/17/975
Since the two patches has been applied, by respective maintainer, I've
applied the series.
Thanks,
Bjorn
>
> Jeffrey Hugo (4):
> arm64: dts: qcom: msm8998: Add blsp1 BAM
> arm64: dts: qcom: msm8998: Add blsp1_uart3
> arm64: dts: qcom: msm8998-mtp: Enable bluetooth
> arm64: dts: qcom: msm8998-clamshell: Enable bluetooth
>
> .../boot/dts/qcom/msm8998-clamshell.dtsi | 17 ++++++++++++
> arch/arm64/boot/dts/qcom/msm8998-mtp.dtsi | 14 ++++++++++
> arch/arm64/boot/dts/qcom/msm8998-pins.dtsi | 13 +++++++++
> arch/arm64/boot/dts/qcom/msm8998.dtsi | 27 +++++++++++++++++++
> 4 files changed, 71 insertions(+)
>
> --
> 2.17.1
>
prev parent reply other threads:[~2019-10-18 17:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-17 22:18 [RFC PATCH 0/4] Enable msm8998 bluetooth Jeffrey Hugo
2019-10-17 22:18 ` [RFC PATCH 1/4] arm64: dts: qcom: msm8998: Add blsp1 BAM Jeffrey Hugo
2019-10-17 22:18 ` [RFC PATCH 2/4] arm64: dts: qcom: msm8998: Add blsp1_uart3 Jeffrey Hugo
2019-10-17 22:18 ` [RFC PATCH 3/4] arm64: dts: qcom: msm8998-mtp: Enable bluetooth Jeffrey Hugo
2019-10-17 22:18 ` [RFC PATCH 4/4] arm64: dts: qcom: msm8998-clamshell: " Jeffrey Hugo
2019-10-18 17:05 ` 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=20191018170532.GC4500@tuxbook-pro \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=jeffrey.l.hugo@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@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