[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20140319234455.GB19187@drone.musicnaut.iki.fi>
Date: Thu, 20 Mar 2014 01:44:55 +0200
From: Aaro Koskinen <aaro.koskinen@....fi>
To: Ralf Baechle <ralf@...ux-mips.org>
Cc: Raghu Gandham <Raghu.Gandham@...tec.com>,
Dmitry Torokhov <dmitry.torokhov@...il.com>,
"linux-input@...r.kernel.org" <linux-input@...r.kernel.org>,
"linux-mips@...ux-mips.org" <linux-mips@...ux-mips.org>,
"linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
Thomas Bogendoerfer <tsbogend@...ha.franken.de>
Subject: Re: [PATCH] Input: i8042-io - Exclude mips platforms when
allocating/deallocating IO regions.
Hi,
On Wed, Mar 19, 2014 at 09:49:31PM +0100, Ralf Baechle wrote:
> I think the patch (http://patchwork.linux-mips.org/patch/6419/) should be
> applied. The argumentation for reserving ports in the platform code are
> the same as on x86 - touch the registers and bad things may happen. This
> is because a fair number of older MIPS platforms were based on x86 chipsets
> or at least are using very similar designs.
If you drop the request_region() from the driver, it will try to probe
anyway regardless what the platform code codes. So bad things could happen,
no?
Currently we can prevent i8042 driver from probing I/O space on PCI-less
Octeons (for example), because we define empty I/O space so request_region()
by driver will fail. So we can actually prevent bad things from happening.
I would call this good design, not an accident.
Maybe I'm missing something? Anyway, I don't have strong feelings whether
this patch is applied or not. My computers will keep on working on either
case.
A.
--
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