[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHCN7xJCxXVUJoEu4h=vBc3v=VpvXd9WnOEM5GNoCrBDeUp6aA@mail.gmail.com>
Date: Thu, 17 Dec 2020 06:16:25 -0600
From: Adam Ford <aford173@...il.com>
To: Geert Uytterhoeven <geert@...ux-m68k.org>
Cc: Linux-Renesas <linux-renesas-soc@...r.kernel.org>,
Adam Ford-BE <aford@...conembedded.com>,
Magnus Damm <magnus.damm@...il.com>,
Rob Herring <robh+dt@...nel.org>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@...r.kernel.org>,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>
Subject: Re: [PATCH 02/18] arm64: dts: renesas: beacon kit: Fix choppy
Bluetooth Audio
On Thu, Dec 17, 2020 at 4:41 AM Geert Uytterhoeven <geert@...ux-m68k.org> wrote:
>
> On Sun, Dec 13, 2020 at 7:38 PM Adam Ford <aford173@...il.com> wrote:
> > The Bluetooth chip is capable of operating at 4Mbps, but the
> > max-speed setting was on the UART node instead of the Bluetooth
> > node, so the chip didn't operate at the correct speed resulting
> > in choppy audio. Fix this by setting the max-speed in the proper
> > node.
> >
> > Fixes: a1d8a344f1ca ("arm64: dts: renesas: Introduce r8a774a1-beacon-rzg2m-kit")
> > Signed-off-by: Adam Ford <aford173@...il.com>
>
> Reviewed-by: Geert Uytterhoeven <geert+renesas@...der.be>
> i.e. will queue in renesas-devel for v5.12.
Since various other patches in the series need a V2, should this be
included in the V2 as no-change, or should I skip this and others that
have been queued? If/when they appear in your branch, I can rebase
the series against that branch and just submit V2's on what's missing.
I want to do whatever creates less work for you.
adam
>
> Gr{oetje,eeting}s,
>
> Geert
>
> --
> Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert@...ux-m68k.org
>
> In personal conversations with technical people, I call myself a hacker. But
> when I'm talking to journalists I just say "programmer" or something like that.
> -- Linus Torvalds
Powered by blists - more mailing lists