From: Adam Ford <aford173@gmail.com>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "open list:BLUETOOTH DRIVERS" <linux-bluetooth@vger.kernel.org>,
Johan Hedberg <johan.hedberg@gmail.com>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
Adam Ford <adam.ford@logicpd.com>,
Sebastian Reichel <sre@kernel.org>
Subject: Re: [PATCH] Revert "Bluetooth: hci_ll: set operational frequency earlier"
Date: Wed, 23 Oct 2019 07:38:43 -0500 [thread overview]
Message-ID: <CAHCN7xKAkYacV6qWuONVqRyJuODt2mNquTWAgEFb0NcjjqpnsA@mail.gmail.com> (raw)
In-Reply-To: <CAHCN7xKA9-K4uYU9oFW+A7ywc8TGixNa-yHJgL7uSTbyXnisTQ@mail.gmail.com>
On Thu, Oct 17, 2019 at 12:57 PM Adam Ford <aford173@gmail.com> wrote:
>
> On Wed, Oct 16, 2019 at 1:36 PM Marcel Holtmann <marcel@holtmann.org> wrote:
> >
> > Hi Adam,
> >
> > > As nice as it would be to update firmware faster, that patch broke
> > > at least two different boards, an OMAP4+WL1285 based Motorola Droid
> > > 4, as reported by Sebasian Reichel and the Logic PD i.MX6Q +
> > > WL1837MOD.
> > >
> > > This reverts commit a2e02f38eff84f199c8e32359eb213f81f270047.
> > >
> > > Signed-off-by: Adam Ford <aford173@gmail.com>
> >
> > patch has been applied to bluetooth-next tree.
>
> Any change this can get pushed upstream to stable? (including 5.4?)
>
Marcel, I have confirmed this revert also fixes a regression on my
omap36xx based device using a wl1283 Bluetooth. At this point, I
believe we've identified at least 3 devices with regressions that this
revert fixes.
adam
> adam
> >
> > Regards
> >
> > Marcel
> >
next prev parent reply other threads:[~2019-10-23 12:38 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-02 11:46 [PATCH] Revert "Bluetooth: hci_ll: set operational frequency earlier" Adam Ford
2019-10-02 20:31 ` Sebastian Reichel
2019-10-16 16:19 ` Adam Ford
2019-10-16 18:36 ` Marcel Holtmann
2019-10-16 18:37 ` Adam Ford
2019-10-17 17:57 ` Adam Ford
2019-10-23 12:38 ` Adam Ford [this message]
2019-10-23 12:43 ` Marcel Holtmann
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=CAHCN7xKAkYacV6qWuONVqRyJuODt2mNquTWAgEFb0NcjjqpnsA@mail.gmail.com \
--to=aford173@gmail.com \
--cc=adam.ford@logicpd.com \
--cc=johan.hedberg@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel@holtmann.org \
--cc=sre@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).