linux-bluetooth.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: David Summers <beagleboard@davidjohnsummers.uk>
To: Marcel Holtmann <marcel@holtmann.org>
Cc: "open list:BLUETOOTH DRIVERS" <linux-bluetooth@vger.kernel.org>,
	Stefan Wahren <stefan.wahren@i2se.com>
Subject: Re: drivers/bluetooth/Kconfig BT_HCIUART_RTL depends on ACPI
Date: Mon, 18 Feb 2019 20:05:08 +0000	[thread overview]
Message-ID: <54432239-eb3c-45d0-a1a3-a7e5bd0d584d@davidjohnsummers.uk> (raw)
In-Reply-To: <07109476-C017-4DC2-98A7-2EE5B53C4AB3@holtmann.org>

On 18/02/2019 10:48, Marcel Holtmann wrote:
> Hi David,
>
>> On Arch Linux Arm, have a couple of people helping with the Tinker Board Patches - think we are close to something that may get passed.
>>
>> Now testing it far more, and a snag, drivers/bluetooth/Kconfig contains:
>>
>> config BT_HCIUART_RTL
>>      bool "Realtek protocol support"
>>      depends on BT_HCIUART
>>      depends on BT_HCIUART_SERDEV
>>      depends on GPIOLIB
>>      depends on ACPI
>>      select BT_HCIUART_3WIRE
>>      select BT_RTL
>>
>> But why does it depend on ACPI? I haven't found a way of setting that in 4.20, used to be in Power Management IIRC - but can't find now.
>>
>> find . -name Kconfig -type f -exec grep "select ACPI" '{}' \;
>>
>> Doesn't find anything to select ACPI …
> initially we only supported Realtek chips that are described via ACPI. For DT based ones you need to extend this. The Broadcom ones uses this line:
>
> depends on (!ACPI || SERIAL_DEV_CTRL_TTYPORT)
>
> Maybe this works here as well.
>
> Regards
>
> Marcel
>
Thanks Marcel,

Happy we have some else on ArchLinux ARM, Stefan Wahren, who has showed 
an interest in getting these things working. He has (very recently) had 
a go at and update, available here:

https://gist.github.com/lategoodbye/79bac99d4f1158a719a48ea3c45eb7f1

Any we have asked someone with a ASUS Tinker Board (S) to test. Stefan changes are good, because he has set up so it uses device tree - which is what we need on ARM. However he has said this was just a hack, so even if it works I expect he'll make more updates.

Hopefully though he'll be able to send a PATCH  in when he is ready.

Regards,

David


      reply	other threads:[~2019-02-18 20:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-04 20:36 drivers/bluetooth/Kconfig BT_HCIUART_RTL depends on ACPI David Summers
2019-02-18 10:48 ` Marcel Holtmann
2019-02-18 20:05   ` David Summers [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=54432239-eb3c-45d0-a1a3-a7e5bd0d584d@davidjohnsummers.uk \
    --to=beagleboard@davidjohnsummers.uk \
    --cc=linux-bluetooth@vger.kernel.org \
    --cc=marcel@holtmann.org \
    --cc=stefan.wahren@i2se.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;
as well as URLs for NNTP newsgroup(s).