[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160223213835.50e42ca5@lxorguk.ukuu.org.uk>
Date: Tue, 23 Feb 2016 21:38:35 +0000
From: One Thousand Gnomes <gnomes@...rguk.ukuu.org.uk>
To: Jesse Barnes <jbarnes@...tuousgeek.org>
Cc: Simon Guinot <simon.guinot@...uanux.org>,
Alan Cox <alan@...ux.intel.com>,
Linus Torvalds <torvalds@...ux-foundation.org>,
Vincent Pelletier <plr.vincent@...il.com>,
Giel van Schijndel <me@...tis.eu>,
linux-gpio@...r.kernel.org,
Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
Vincent Donnefort <vdonnefort@...il.com>,
Yoann Sculo <yoann@...lo.fr>,
Linus Walleij <linus.walleij@...aro.org>
Subject: Re: [PATCH] kernel/resource.c: fix muxed resource handling in
__request_region()
> > IORESOURCE_MUXED is a convenient way to deal with that. For some code
> > examples you can look at the superio_* functions in the IT87 drivers:
> > gpio/gpio-it87.c, hwmon/it87.c and watchdog/it87_wdt.c.
> >
> > I am not aware of any other users for IORESOURCE_MUXED.
> >
> > Let me know how you want to go and if you need my help.
>
> I'd be happy if you proposed a patch. It would also be nice if we could
> somehow more formally limit the MUXED usage to these super I/O devices,
> just so other users don't get into trouble thinking it's more general
> than it is.
Today I think the problem wouldn't exist. We'd tell the authors of the
drivers to create an mfd or similar to manage the resources and load the
appropriate extra goodies.
Alan
Powered by blists - more mailing lists