From: Andrew Morton <akpm@linux-foundation.org>
To: Ondrej Zary <linux@rainbow-software.org>
Cc: linux-kernel@vger.kernel.org, mingo@elte.hu, rjw@sisk.pl
Subject: Re: [PATCH] Fix floppy hibernation
Date: Tue, 2 Jun 2009 23:25:02 -0700 [thread overview]
Message-ID: <20090602232502.b05302d3.akpm@linux-foundation.org> (raw)
In-Reply-To: <200906030813.27625.linux@rainbow-software.org>
On Wed, 3 Jun 2009 08:13:26 +0200 Ondrej Zary <linux@rainbow-software.org> wrote:
> > > +static int floppy_resume(struct platform_device *dev)
> > > +{
> > > + int fdc;
> > > +
> > > + for (fdc = 0; fdc < N_FDC; fdc++)
> > > + if (FDCS->address != -1)
> > > + user_reset_fdc(-1, FD_RESET_ALWAYS, 0);
> > > +
> > > + return 0;
> > > +}
> >
> > The patch changes the driver so that it calls user_reset_fdc() for each
> > device at resume-time.
> >
> > Why? What effect does this have on the hardware and why does it fix
> > things?
>
> I don't know at all, it's complete guesswork. The first thing I tested was
> rmmod floppy && modprobe floppy after resume - it worked. Narrowing the
> initialization code down resulted in this patch.
lol, OK. I added this to the changelog:
This fix resets the floppy controller on resume. It was
experimentally determined to bring the controller back to life - we
don't really know why it works.
floppy_init() does the same thing at boot/modprobe time.
Let's see how it goes... If someone reports breakage then we can
always change the driver so that activation of your new code requires a
module parameter.
prev parent reply other threads:[~2009-06-03 6:25 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-30 16:04 [PATCH] Fix floppy hibernation Ondrej Zary
2009-06-01 11:43 ` Pavel Machek
2009-06-01 19:51 ` Ingo Molnar
2009-06-01 20:52 ` Rafael J. Wysocki
2009-06-01 23:12 ` Ingo Molnar
2009-06-01 23:45 ` Andrew Morton
2009-06-02 16:30 ` Ondrej Zary
2009-06-02 22:15 ` Andrew Morton
2009-06-03 6:13 ` Ondrej Zary
2009-06-03 6:25 ` Andrew Morton [this message]
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=20090602232502.b05302d3.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rainbow-software.org \
--cc=mingo@elte.hu \
--cc=rjw@sisk.pl \
/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