From: Tony Mobily <merc@mobily.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Greg Kroah-Hartman <gregkh@suse.de>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: Putting the sdhci to sleep safely [with attachments]
Date: Tue, 26 Dec 2006 10:05:51 +0900 [thread overview]
Message-ID: <4590756F.1090603@mobily.com> (raw)
In-Reply-To: <20061225211432.GA2460@elf.ucw.cz>
Hi,
> (Please always cc: linux-kernel@ with such stuff).
Gosh, alright. I am gonna embarrass myself here, but I guess this is
part of the game...! :-D
>> I am the Editor In Chief of Free Software Magazine
>> (http://www.freesoftwaremagazine.com)
>> I am in a bit of a mission: I would like to see the module sdhci put my
>> card reader to sleep without getting the system highly
>> unstable. This is
>
> Well, suspend works for me, and my machine seems to have sdhci:
>
> 0000:15:00.2 0805: Ricoh Co Ltd R5C822 SD/SDIO/MMC/MS/MSPro Host
> Adapter (rev 18)
Alright, that's what I have as well...
0a:01.1 Generic system peripheral [0805]: Ricoh Co Ltd R5C822
SD/SDIO/MMC/MS/MSPro Host Adapter (rev 19)
>> Pierre Ossman, the maintainer of the sdhci module, wrote to me:
>>
>> "Anyway, as far as I know, this isn't a bug in the driver, so there is
>> not very much I can do. The problem is somewhere in the PCI interaction,
>> but I've sent numerous mail to the kernel PCI hackers, but have yet to
>> receive a single reply."
>
> I've certainly not seen such a mail.
OK. I guess there was a bit of a communication problem here. I am more
than happy to
> Can you get info what is wrong
> with that, and cc lkml, me and greg?
Sure thing!
>> So, here I am... please find attache my lspci and the log of what
>> happens when the computer is put to sleep.
>>
>> I would also be happy to organise a bounty for this bug to be fixed.
>
> :-). Just hunt it yourself. It is probably easier than organizing a bounty.
OK. I had a look at the code, and I foind it depressing. Not because it
was bad, but because it reminded me of how hopeless I am!
I can do my best to get you guys to communicate, *and* to get some
testing done - I am more than happy to spend as long as it takes
testing, compiling patches, and putting my laptop to sleep over and over
and over again. But coding... nope. Not on *this* code...
> Ouch... you failed to mention what kernel you are using?
I told you I'd embarrass myself...
Linux merc-laptop 2.6.19-7-generic #2 SMP Mon Dec 4 16:46:19 UTC 2006
i686 GNU/Linux
I am trying to gather some information - will report back to you ASAP.
Merc.
next prev parent reply other threads:[~2006-12-26 1:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <458FA64E.7070501@mobily.com>
2006-12-25 21:14 ` Pavel Machek
2006-12-26 1:05 ` Tony Mobily [this message]
2006-12-26 14:42 ` Pavel Machek
2006-12-26 14:45 ` Tony Mobily
2006-12-26 14:49 ` Pavel Machek
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=4590756F.1090603@mobily.com \
--to=merc@mobily.com \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
/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®