From mboxrd@z Thu Jan 1 00:00:00 1970 From: Brian Norris Subject: Re: [PATCH v2 1/3] Bluetooth: btusb: add QCA6174A compatible properties Date: Tue, 26 Mar 2019 11:45:57 -0700 Message-ID: References: <20190222225345.69084-1-briannorris@chromium.org> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Return-path: In-Reply-To: Sender: linux-kernel-owner@vger.kernel.org To: Marcel Holtmann Cc: Heiko Stuebner , Johan Hedberg , Rob Herring , Enric Balletbo i Serra , Douglas Anderson , devicetree , linux-arm-kernel , "open list:ARM/Rockchip SoC..." , Linux Bluetooth mailing list , Linux Kernel , Matthias Kaehlcke , Rajat Jain , Robin Murphy List-Id: devicetree@vger.kernel.org On Wed, Feb 27, 2019 at 1:34 PM Brian Norris wrote: > On Tue, Feb 26, 2019 at 11:53 PM Marcel Holtmann wrote: > > all 3 patches have been applied to bluetooth-next tree. > > Thanks! I failed to repeat my comment from v1: > > """ > This patch is also required to make this stable, but since it's not > really tied to the device tree, and it's an existing bug, I sent it > separately: > > https://lore.kernel.org/patchwork/patch/1044896/ > Subject: Bluetooth: btusb: request wake pin with NOAUTOEN > """ > > Can you take this one too? Otherwise Scarlet will be less stable > (possible interrupt storm at boot). Ping? RK3399/Scarlet is currently in bad shape on v5.1-rc2, since it doesn't have the interrupt storm fix. I'll ping on that patch directly too. Brian