All of lore.kernel.org
 help / color / mirror / Atom feed
* docked sysfs attribute always 0
@ 2017-03-14 19:26 Kevin Locke
  2017-03-14 20:42 ` Rafael J. Wysocki
  0 siblings, 1 reply; 3+ messages in thread
From: Kevin Locke @ 2017-03-14 19:26 UTC (permalink / raw)
  To: linux-acpi; +Cc: Pali Rohár

On my Lenovo ThinkPad T430 (2342-CTO) with kernel 4.10.1 (and
presumably earlier) the "docked" sysfs file always contains 0 for all
dock devices (ata_bay and battery_bay), even when devices are present,
both at boot and after hotplug.  I could not find a documented API for
this file, but from the code and use in widely-available dock
scripts[1] I presume that this behavior is incorrect.  I found a
similar issue reported by Pali Rohár[2] a few years ago which doesn't
appear to have been resolved.

Assuming this behavior is a bug, should I open an issue in Bugzilla to
track it?  I'm not familiar with the mailing-list vs Bugzilla
etiquette, but didn't find an issue for the previous report.

If there's anything else I can do to help debug, let me know.

Thanks,
Kevin

P.S.  Please CC me in replies as I am not subscribed to linux-acpi.

1.  http://www.thinkwiki.org/wiki/How_to_hotswap_Ultrabay_devices#Script_for_Ultrabay_eject
2.  https://marc.info/?t=139880262200003&r=1&w=2

-- 
Kevin Locke  |  kevin@kevinlocke.name    | XMPP: kevin@kevinlocke.name
             |  https://kevinlocke.name  | IRC:   kevinoid on freenode

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: docked sysfs attribute always 0
  2017-03-14 19:26 docked sysfs attribute always 0 Kevin Locke
@ 2017-03-14 20:42 ` Rafael J. Wysocki
  2017-03-14 22:11   ` Kevin Locke
  0 siblings, 1 reply; 3+ messages in thread
From: Rafael J. Wysocki @ 2017-03-14 20:42 UTC (permalink / raw)
  To: Kevin Locke, ACPI Devel Maling List, Pali Rohár

On Tue, Mar 14, 2017 at 8:26 PM, Kevin Locke <kevin@kevinlocke.name> wrote:
> On my Lenovo ThinkPad T430 (2342-CTO) with kernel 4.10.1 (and
> presumably earlier) the "docked" sysfs file always contains 0 for all
> dock devices (ata_bay and battery_bay), even when devices are present,
> both at boot and after hotplug.  I could not find a documented API for
> this file, but from the code and use in widely-available dock
> scripts[1] I presume that this behavior is incorrect.  I found a
> similar issue reported by Pali Rohár[2] a few years ago which doesn't
> appear to have been resolved.
>
> Assuming this behavior is a bug, should I open an issue in Bugzilla to
> track it?

Yes, won't hurt.

Please add rjw@rjwysocki.net to the CC list.

Thanks,
Rafael

^ permalink raw reply	[flat|nested] 3+ messages in thread

* Re: docked sysfs attribute always 0
  2017-03-14 20:42 ` Rafael J. Wysocki
@ 2017-03-14 22:11   ` Kevin Locke
  0 siblings, 0 replies; 3+ messages in thread
From: Kevin Locke @ 2017-03-14 22:11 UTC (permalink / raw)
  To: Rafael J. Wysocki; +Cc: ACPI Devel Maling List, Pali Rohár

On Tue, 2017-03-14 at 21:42 +0100, Rafael J. Wysocki wrote:
> On Tue, Mar 14, 2017 at 8:26 PM, Kevin Locke <kevin@kevinlocke.name> wrote:
>> On my Lenovo ThinkPad T430 (2342-CTO) with kernel 4.10.1 (and
>> presumably earlier) the "docked" sysfs file always contains 0 for all
>> dock devices (ata_bay and battery_bay), even when devices are present,
>> both at boot and after hotplug. [...]
>>
>> Assuming this behavior is a bug, should I open an issue in Bugzilla to
>> track it?
> 
> Yes, won't hurt.
> 
> Please add rjw@rjwysocki.net to the CC list.

Done.  I created https://bugzilla.kernel.org/show_bug.cgi?id=194885

-- 
Thanks,      |  kevin@kevinlocke.name    | XMPP: kevin@kevinlocke.name
Kevin        |  https://kevinlocke.name  | IRC:   kevinoid on freenode

^ permalink raw reply	[flat|nested] 3+ messages in thread

end of thread, other threads:[~2017-03-14 22:11 UTC | newest]

Thread overview: 3+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2017-03-14 19:26 docked sysfs attribute always 0 Kevin Locke
2017-03-14 20:42 ` Rafael J. Wysocki
2017-03-14 22:11   ` Kevin Locke

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.