From: Chris Morgan <macroalpha82@gmail.com>
To: devicetree@vger.kernel.org
Cc: linux-rockchip@lists.infradead.org, netdev@vger.kernel.org,
anarsoul@gmail.com, alistair@alistair23.me, heiko@sntech.de,
conor+dt@kernel.org, krzysztof.kozlowski+dt@linaro.org,
robh+dt@kernel.org, pabeni@redhat.com, kuba@kernel.org,
edumazet@google.com, davem@davemloft.net,
Chris Morgan <macromorgan@hotmail.com>
Subject: [PATCH 0/2] Correct fallback compatible for rtl8821cs bluetooth
Date: Mon, 8 May 2023 11:08:09 -0500 [thread overview]
Message-ID: <20230508160811.3568213-1-macroalpha82@gmail.com> (raw)
From: Chris Morgan <macromorgan@hotmail.com>
The realtek 8821cs bluetooth module is functionally very similar to the
8822cs and 8723bs modules, however unlike the 8822 module it seems to
struggle when power management features are enabled. By switching the
fallback string from realtek,rtl8822cs-bt to realtek,rtl8723bs-bt we
can instruct the driver to not enable advanced power management
features that cause the issues.
Chris Morgan (2):
dt-bindings: net: realtek-bluetooth: Fix RTL8821CS binding
arm64: dts: rockchip: Fix compatible for Bluetooth
Documentation/devicetree/bindings/net/realtek-bluetooth.yaml | 2 +-
arch/arm64/boot/dts/rockchip/rk3566-anbernic-rgxx3.dtsi | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
--
2.34.1
next reply other threads:[~2023-05-08 16:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-08 16:08 Chris Morgan [this message]
2023-05-08 16:08 ` [PATCH 1/2] dt-bindings: net: realtek-bluetooth: Fix RTL8821CS binding Chris Morgan
2023-05-08 16:34 ` Krzysztof Kozlowski
2023-05-13 16:45 ` Heiko Stuebner
2023-06-07 19:03 ` Rob Herring
2023-05-08 16:08 ` [PATCH 2/2] arm64: dts: rockchip: Fix compatible for Bluetooth Chris Morgan
2023-06-08 8:48 ` (subset) [PATCH 0/2] Correct fallback compatible for rtl8821cs bluetooth Heiko Stuebner
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=20230508160811.3568213-1-macroalpha82@gmail.com \
--to=macroalpha82@gmail.com \
--cc=alistair@alistair23.me \
--cc=anarsoul@gmail.com \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=heiko@sntech.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=kuba@kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=macromorgan@hotmail.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=robh+dt@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;
as well as URLs for NNTP newsgroup(s).