On 05/08/2012 04:52 AM, Lan Tianyu wrote:
> Hi all:
>
> Following is the usb port descriptor in the DSDT of Thinkpad T410.
> The port is attached with bluetooth on the board.
> Name (_UPC, Package (0x04) { 0xFF, 0xFF, 0x00, 0x00 })
_UPC 1st byte says "connectable"
_UPC 2nd byte says "proprietary connector"
Name (_PLD, Buffer (0x10)
> { /* 0000 */ 0x81, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00,
> /* 0008 */ 0x30, 0x1C, 0x00, 0x00, 0x00, 0x00, 0x00, 0x00
> }) }
> _PLD buffer show the device internal port. Bit 64 – User Visible:
> Set if the device connection point can be seen by the user without
> disassembly.
According to the decoding from Bob Moore,
bit 64 is not set, and thus this I/F is NOT user visible.
Are we decoding this correctly?
81 6:0 = 1 (revision)
7 = 1 (ignore color)
00 15:8 (color red = 0)
00 23:16 (color green = 0)
00 31:24 (color blue = 0)
00 47:32 (width = 0)
00
00 63:48 (Height = 0)
00
30 64 (user visible = 0)
65 (dock = 0)
66 (lid = 0)
67:69 (Panel = b110 = 6 = unknown)
71:70 (vertical = 0 = upper)
1c 73:72 (horizontal = b00 = 0 = left)
77:74 (shape = b0111 = 7 = unknown)
00
00
00
00
00
00
-Len
>
> 于2012年05月08日 星期二 10时58分17秒,Matthew Garrett写到:
>> On Mon, May 07, 2012 at 09:57:44AM -0700, Greg KH wrote:
>>> On Mon, May 07, 2012 at 09:38:15AM +0800, Lan Tianyu wrote:
>>>> This depends on the bios. From my opinion, the bluetooth is device
>>>> on the
>>>> motherboard so it belongs to hard-wired type.
>>>
>>> That's nice, but it's not what is happening in lots of different laptops
>>> out there today.
>>>
>>> Oliver is right, how does this handle bluetooth USB controllers that are
>>> turned on/off from magic function-key presses?
>>
>> I /believe/ that such devices will be indicated as fixed rather than
>> removable. The variable indicates the physical state rather than the
>> logical one - fixed doesn't mean that a device will never go away, it
>> means that a user can't physically unplug it.
>>
>
>
>
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
