From: "Rafael J. Wysocki" <rjw@rjwysocki.net>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Shaohua Li <shaohua.li@intel.com>, Len Brown <lenb@kernel.org>,
linux-acpi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: bug: acpi ata_bay dock reminds undocked
Date: Tue, 29 Apr 2014 22:55:07 +0200 [thread overview]
Message-ID: <2146960.E8Lje2UBps@vostro.rjw.lan> (raw)
In-Reply-To: <201404292216.41256@pali>
[-- Attachment #1: Type: text/plain, Size: 1608 bytes --]
On Tuesday, April 29, 2014 10:16:41 PM Pali Rohár wrote:
> Hello,
Hi,
> I have problem with sysfs entry docked
>
> /sys/bus/platform/devices/dock.0/docked
>
> for my media bay DVD drive on notebook Dell Latitude E6440.
>
> After booting linux kernel docked is set to 1 (which is correct,
> DVD hw is inserted into sata dock). When I undock it via sysfs
> entry
>
> /sys/bus/platform/devices/dock.0/undock
>
> then kernel remove DVD device from system (no /dev/sr0 anymore)
> and docked sysfs entry is set to 0.
>
> When I press eject button on DVD drive, I hear some spin up and
> kernel detect DVD device again (also udev create /dev/sr0). But
> docked sysfs entry remains set to 0. It will never be set back to
> 1 - only after reboot.
>
> So this looks like bug somewhere and probably in linux acpi dock
> driver... Do you know to solve this problem? More applications
> checking docked sysfs entry for dock presence and returning 0
> will mislead them.
>
> Here is some info from sysfs about dock:
>
> $ grep "" /sys/bus/platform/devices/dock.0/*
> /sys/bus/platform/devices/dock.0/docked:0
> /sys/bus/platform/devices/dock.0/flags:32
> /sys/bus/platform/devices/dock.0/modalias:acpi:LNXIOBAY:
> /sys/bus/platform/devices/dock.0/type:ata_bay
> /sys/bus/platform/devices/dock.0/uevent:MODALIAS=acpi:LNXIOBAY:
>
> If you need some more info let me know. I would be happy to have
> working docked sysfs entry.
Which kernel version(s) have you tried?
--
I speak only for myself.
Rafael J. Wysocki, Intel Open Source Technology Center.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2014-04-29 20:38 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-29 20:16 Pali Rohár
2014-04-29 20:55 ` Rafael J. Wysocki [this message]
2014-04-29 21:00 ` Pali Rohár
2014-04-29 21:35 ` Rafael J. Wysocki
2014-04-30 9:24 ` Pali Rohár
2014-05-03 22:02 ` Pali Rohár
2014-05-11 15:49 ` Pali Rohár
2014-05-12 0:00 ` Rafael J. Wysocki
2014-05-12 5:48 ` Pali Rohár
2014-08-12 11:53 ` Pali Rohár
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=2146960.E8Lje2UBps@vostro.rjw.lan \
--to=rjw@rjwysocki.net \
--cc=lenb@kernel.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=shaohua.li@intel.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
all inboxes | Powered by JetHome®