public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
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 15:15:56 -0700	[thread overview]
Message-ID: <20090602151556.5df9167c.akpm@linux-foundation.org> (raw)
In-Reply-To: <200906021830.53531.linux@rainbow-software.org>

On Tue, 2 Jun 2009 18:30:50 +0200
Ondrej Zary <linux@rainbow-software.org> wrote:

> > > +static int floppy_resume(struct platform_device *dev)
> > > +{
> > > +	int i;
> > > +
> > > +	for (i = 0; i < N_FDC; i++)
> > > +		if (FDCS->address != -1)
> > > +			user_reset_fdc(-1, FD_RESET_ALWAYS, 0);
> > > +
> > > +	return 0;
> > > +}
> >
> > hm, how does this work?
> >
> > FDCS is a revolting should-not-exist macro which assumes the presence
> > of a local variable called `fdc'.
> 
> The driver is complete mess - there is also a global static fdc variable.
> So it worked because I have only one floppy controller.
> 
> > So I think the loop control variable here should be called `fdc', not `i'.
> 
> See the v2 patch below. Tested and works too.

OK.

> >
> > It's pretty amazing that something like this still exists in a core
> > driver.  Someone please save us!
> 
> 
> 
> 
> Based on Ingo Molnar's patch from 2006, this makes the floppy work after
> resume from hibernation, at least on my machine.
> 

That's a very skimpy changelog.  The lack of any useful reference to
the referred-to Ingopatch doesn't aid things..

> --- linux-2.6.29.4-orig/drivers/block/floppy.c	2009-05-30 14:38:29.000000000 +0200
> +++ linux/drivers/block/floppy.c	2009-06-02 17:32:56.000000000 +0200
> @@ -4148,6 +4148,24 @@
>  {
>  }
>  
> +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?

Thanks.


  reply	other threads:[~2009-06-02 22:16 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 [this message]
2009-06-03  6:13       ` Ondrej Zary
2009-06-03  6:25         ` Andrew Morton

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=20090602151556.5df9167c.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