All of lore.kernel.org
 help / color / mirror / Atom feed
From: Larry Finger <Larry.Finger@lwfinger.net>
To: Bastien Nocera <hadess@hadess.net>
Cc: linux-wireless@vger.kernel.org
Subject: Re: Realtek GPIO chipset, for Baytrail?
Date: Tue, 09 Sep 2014 15:24:30 -0500	[thread overview]
Message-ID: <540F61FE.2050404@lwfinger.net> (raw)
In-Reply-To: <1410292835.4077.21.camel@hadess.net>

On 09/09/2014 03:00 PM, Bastien Nocera wrote:
> On Tue, 2014-09-09 at 14:27 -0500, Larry Finger wrote:
>> On 09/09/2014 04:56 AM, Bastien Nocera wrote:
>>> Hey,
>>>
>>> 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?
>>
>> Bastien,
>>
>>   From the previous response, it seems unlikely that GPIO is used to control the
>> device. That is what I expected. Working at that primitive level would be
>> extremely difficult timing.
>
> Right.
>
>> I assume that you have checked both 'lspci' and 'lsusb' for any mention of the
>> wireless device.
>
> No mentions at all in there.
>
>>   I am not aware of a similar utility to scan an SDIO bus, but
>> perhaps someone on this list will know.
>
> They would show up under /sys/bus/sdio/devices/ and there's nothing in
> there except the SD card reader.
>
>>   In addition, a full listing of 'lspci
>> -nnv' will give a clue regarding what adapters are on the device.
>
> Here it is, I doubt that's much help.
>
> 00:00.0 Host bridge [0600]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series SoC Transaction Register [8086:0f00] (rev 0d)
>          Subsystem: Intel Corporation Device [8086:0f31]
>          Flags: bus master, fast devsel, latency 0
>          Kernel driver in use: iosf_mbi_pci
>          Kernel modules: iosf_mbi
>
> 00:02.0 VGA compatible controller [0300]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31] (rev 0d) (prog-if 00 [VGA controller])
>          Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Graphics & Display [8086:0f31]
>          Flags: bus master, fast devsel, latency 0, IRQ 106
>          Memory at a0000000 (32-bit, non-prefetchable) [size=4M]
>          Memory at 80000000 (32-bit, prefetchable) [size=512M]
>          I/O ports at 1000 [size=8]
>          Expansion ROM at <unassigned> [disabled]
>          Capabilities: <access denied>
>          Kernel driver in use: i915
>          Kernel modules: i915
>
> 00:14.0 USB controller [0c03]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series USB xHCI [8086:0f35] (rev 0d) (prog-if 30 [XHCI])
>          Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series USB xHCI [8086:0f35]
>          Flags: bus master, medium devsel, latency 0, IRQ 104
>          Memory at a0800000 (64-bit, non-prefetchable) [size=64K]
>          Capabilities: <access denied>
>          Kernel driver in use: xhci_hcd
>
> 00:1a.0 Encryption controller [1080]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine [8086:0f18] (rev 0d)
>          Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Trusted Execution Engine [8086:0f18]
>          Flags: bus master, fast devsel, latency 0, IRQ 107
>          Memory at a0700000 (32-bit, non-prefetchable) [size=1M]
>          Memory at a0600000 (32-bit, non-prefetchable) [size=1M]
>          Capabilities: <access denied>
>          Kernel driver in use: mei_txe
>          Kernel modules: mei_txe
>
> 00:1f.0 ISA bridge [0601]: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit [8086:0f1c] (rev 0d)
>          Subsystem: Intel Corporation Atom Processor Z36xxx/Z37xxx Series Power Control Unit [8086:0f1c]
>          Flags: bus master, medium devsel, latency 0
>          Capabilities: <access denied>
>          Kernel driver in use: pmc_atom
>          Kernel modules: lpc_ich
>
>
>> If the device were used with SDIO, then it would be known as the RTL8723AS. I
>> could not find that chip, but there is an RTL8723BS with a 32-bit driver for
>> Windows 8.1.
>
> That sounds like it could be that one then. This is the only info I
> have, the (very generic) driver set for Windows (which seems to have
> support for every variant) and the DSDT:
> https://bugzilla.kernel.org/attachment.cgi?id=149331
>
> The Bluetooth device has a firmware named "rtl8723b_config.bin"
>
>> What specific Baytrail tablet do you have?
>
> The Onda v975w. It came with Windows 8.1 32-bit.
>
> I guess that the device is probably a PCI one, but the enumeration is
> done through ACPI instead of "normal" PCI.

In 
http://www.onda-tablet.com/onda-v975w-quad-core-win-8-tablet-9-7-inch-retina-screen-ram-2gb-wifi-32gb.html, 
someone is specifically looking for an RTL8723BS driver.

I will see if my contact at Realtek knows who has worked on drivers for this 
device, and if it would be possible to use rtl8723be if we were to supply an 
SDIO frontend.

If I were to find code, do you have the possibility to build drivers for the device?

Larry



  reply	other threads:[~2014-09-09 20:24 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 [this message]
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
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=540F61FE.2050404@lwfinger.net \
    --to=larry.finger@lwfinger.net \
    --cc=hadess@hadess.net \
    --cc=linux-wireless@vger.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 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.