From: Paul Menzel <pmenzel@molgen.mpg.de>
To: Luiz Augusto von Dentz <luiz.dentz@gmail.com>
Cc: Tedd An <tedd.an@intel.com>,
linux-bluetooth@vger.kernel.org,
Tedd Ho-Jeong An <hj.tedd.an@gmail.com>
Subject: Re: [RFC PATCH] Bluetooth: btintel: Fix broken LED quirk for legacy ROM device
Date: Sat, 18 Dec 2021 11:20:44 +0100 [thread overview]
Message-ID: <82abfb3e-2e70-736f-95dc-b3cb88b952bb@molgen.mpg.de> (raw)
In-Reply-To: <CABBYNZJSF6CEU+oJHeKtU5Z-pqL5rn_pO9CxaDwbuWeATBk-QA@mail.gmail.com>
Dear Luiz, dear Tedd,
Am 17.12.21 um 20:27 schrieb Luiz Augusto von Dentz:
> On Fri, Dec 17, 2021 at 7:33 AM Paul Menzel <pmenzel@molgen.mpg.de> wrote:
>> Am 16.12.21 um 19:38 schrieb An, Tedd:
>>
>>> On Thu, 2021-12-16 at 08:52 +0100, Paul Menzel wrote:
>>
>>>> Am 16.12.21 um 04:34 schrieb Tedd Ho-Jeong An:
>>>>> From: Tedd Ho-Jeong An <tedd.an@intel.com>
>>>>>
>>>>> This patch fix the broken LED quirk for Intel legacy ROM devices.
>>>>
>>>> fix*es*
>>>>
>>>> Excuse my ignorance, but what are Intel legacy ROM devices? Maybe also
>>>> mention the IDs 0x0a2a and 0x0aa7 in the commit message?
>>>>
>>>>> Legacy device sends the SW RFKILL while shutting down the device (like
>>>>> HCI interface down) to turn off the LED by putting the device in assert.
>>>>>
>>>>> Once the SW RFKILL is on, it needs the HCI_Reset to exit from the SW
>>>>> RFKILL state. This patch checks the quirk and send the HCI_Reset before
>>>>
>>>> send*s*
>>>>
>>>>> sending the HCI_Intel_Read_Version command.
>>>>
>>>> Is that document in some datasheet/specification? If so, please mention it.
>>>>
>>>> Also, in the commit message summary you write “Fix”. If it fixes an old
>>>> commit, please add a Fixes: tag.
>>>>
>>>>> Signed-off-by: Tedd Ho-Jeong An <tedd.an@intel.com>
>>>>> ---
>>>>> drivers/bluetooth/btintel.c | 13 ++++++-------
>>>>> drivers/bluetooth/btusb.c | 10 ++++++++--
>>>>> 2 files changed, 14 insertions(+), 9 deletions(-)
>>>>
>>>> I have a Dell Latitude E7250 with the 8087:0a2a. How can I test this?
>>>
>>> Apply this patch on top of the bluetooth-next (or current mainline)
>>> The BT interface should be available after reboot.
>>
>> On the laptop, I do not have any problems with missing BT interface
>> after reboot with Linux 5.16-rc5. Are not all devices affected?
>
> If the problem is fixed for you please confirm it by replying with a
> Tested-by line.
Sorry, there seems to be a misunderstanding. I do not know what the
problem is in the first place. On the Dell Latitude E7250 with Linux
5.16-rc5 the Bluetooth interface shows up after a warm reboot just fine.
Kind regards,
Paul
prev parent reply other threads:[~2021-12-18 10:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-16 3:34 [RFC PATCH] Bluetooth: btintel: Fix broken LED quirk for legacy ROM device Tedd Ho-Jeong An
2021-12-16 7:52 ` Paul Menzel
2021-12-16 18:38 ` An, Tedd
2021-12-17 11:39 ` Paul Menzel
2021-12-17 19:27 ` Luiz Augusto von Dentz
2021-12-18 10:20 ` Paul Menzel [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=82abfb3e-2e70-736f-95dc-b3cb88b952bb@molgen.mpg.de \
--to=pmenzel@molgen.mpg.de \
--cc=hj.tedd.an@gmail.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=luiz.dentz@gmail.com \
--cc=tedd.an@intel.com \
/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