[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20080310163744.5f6a04b8.akpm@linux-foundation.org>
Date: Mon, 10 Mar 2008 16:37:44 -0700
From: Andrew Morton <akpm@...ux-foundation.org>
To: "Rafael J. Wysocki" <rjw@...k.pl>
Cc: Andres Salomon <dilinger@...ued.net>, adaplas@...il.com,
linux-kernel@...r.kernel.org,
linux-fbdev-devel@...ts.sourceforge.net, info-linux@...de.amd.com,
jordan.crouse@....com, samuel.thibault@...-lyon.org,
Pavel Machek <pavel@....cz>
Subject: Re: [PATCH 6/6] PM/FB/gxfb: add config option that allows disabling
of VT switch during suspend
On Mon, 10 Mar 2008 23:28:18 +0100 "Rafael J. Wysocki" <rjw@...k.pl> wrote:
> > > > If so, that means extra #ifdef's sprinkled throughout the code. Note
> > > > that most framebuffer drivers won't be supporting this, and those that
> > > > do will almost certainly always want vt switching turned off..
> > > >
> > >
> > > I don't think you need any ifdefs or config options at all, do you? Just
> > > add a new module parameter to this driver and some little interface into
> > > the PM core which allows the driver to set no_vt_switch?
> > >
> >
> > That's a possibility, but doesn't adding hooks into PM core for two
> > drivers (lxfb and gxfb) seems like overkill? I also don't really see
> > anyone needing to switch back and forth between VT_SWITCH and
> > NO_VT_SWITCH other than to work around possible bugs in the register
> > save/restore code..
>
> FWIW, I prefer the original .config option idea.
Please explain your reasoning?
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists