From: Loic Poulain <loic.poulain@intel.com>
To: Bastien Nocera <hadess@hadess.net>
Cc: Marcel Holtmann <marcel@holtmann.org>, linux-wireless@vger.kernel.org
Subject: Re: Realtek GPIO chipset, for Baytrail?
Date: Thu, 11 Sep 2014 17:41:50 +0200 [thread overview]
Message-ID: <5411C2BE.6090702@intel.com> (raw)
In-Reply-To: <F79C10A5-18F8-4165-BFC5-FDAD35BE46BE@holtmann.org>
Hi Bastien,
Your device is a child of 80860F0A (UART) which is driven by the 8250_dw
driver.
OBDA8723 is the BT part of the realtek 8723 WiFi/BT combo chip.
acpi_platform should create a platform device from the ACPI desc.
Then, you can add the OBDA8723 acpi id to the rfkill-gpio platform
driver (net/rfkill) which
seems to handle correctly the basic power management of this chip.
You need to use hciattach to attach the chip to the BT stack (with
H5/3-wire proto).
Regards,
Loic
On 11/09/2014 17:06, Marcel Holtmann wrote:
> Hi Bastien,
>
>> I have a tablet that seems to be using Realtek chips to do wireless
>> communications (hopefully, this time I won't be wrong[1]).
>>
>> The device, under the gpio class in /sys, shows with a modalias of
>> "acpi:OBDA8723:" (that's on "O", not "0"). This seems to correspond to a
>> Realtek chipset (Larry tells me it matches the PCI ID of 0bda:8723 for
>> the RTL8723AE chipset).
>>
>> It shows up under:
>> /sys/devices/platform/80860F0A:00/subsystem/devices
>>
>> Does anyone have details on how this chipset is actually hooked up? Can
>> a portion of the existing RTL8723AE driver code be reused?
> so after a little bit of digging, this seems to be the UART device for the Bluetooth chip. Can you try using 8250_dw.ko driver and see if it binds to it and you get a new serial port.
>
> If I am correct then you have to run H:5 UART transport protocol to enable Bluetooth for this device.
>
> Please double check that this ACPI tables really wrongly declare this as a Broadcom chip. This seems to be a firmware bug then. Unfortunately I think that for Broadcom you run H:4 UART transport protocol and for Realtek you have to run H:5 UART transport protocol. So no idea how to nicely differentiate these.
>
> Regards
>
> Marcel
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
--
Intel Open Source Technology Center
http://oss.intel.com/
next prev parent reply other threads:[~2014-09-11 15:40 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-09 9:56 Realtek GPIO chipset, for Baytrail? Bastien Nocera
2014-09-09 10:35 ` Arend van Spriel
2014-09-09 19:27 ` Larry Finger
2014-09-09 20:00 ` Bastien Nocera
2014-09-09 20:24 ` Larry Finger
2014-09-09 21:22 ` Bastien Nocera
2014-09-09 21:53 ` Larry Finger
2014-09-09 23:10 ` Marcel Holtmann
2014-09-10 8:46 ` Arend van Spriel
2014-09-10 9:50 ` Bastien Nocera
2014-09-10 10:21 ` Arend van Spriel
2014-09-10 11:25 ` Bastien Nocera
2014-09-10 13:45 ` Larry Finger
2014-09-11 17:34 ` Bastien Nocera
2014-09-10 14:53 ` Marcel Holtmann
2014-09-10 9:48 ` Bastien Nocera
2014-09-11 15:06 ` Marcel Holtmann
2014-09-11 15:41 ` Loic Poulain [this message]
2014-09-11 16:01 ` Bastien Nocera
2014-09-11 16:37 ` Marcel Holtmann
2014-09-11 16:42 ` Bastien Nocera
2014-09-11 17:06 ` Marcel Holtmann
2014-09-11 17:07 ` Bastien Nocera
2014-09-11 16:03 ` Bastien Nocera
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=5411C2BE.6090702@intel.com \
--to=loic.poulain@intel.com \
--cc=hadess@hadess.net \
--cc=linux-wireless@vger.kernel.org \
--cc=marcel@holtmann.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.