From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1755660AbcBVUxP (ORCPT ); Mon, 22 Feb 2016 15:53:15 -0500 Received: from gproxy9-pub.mail.unifiedlayer.com ([69.89.20.122]:54413 "HELO gproxy9-pub.mail.unifiedlayer.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1755512AbcBVUxN (ORCPT ); Mon, 22 Feb 2016 15:53:13 -0500 X-Authority-Analysis: v=2.1 cv=GOWbTI9K c=1 sm=1 tr=0 a=9W6Fsu4pMcyimqnCr1W0/w==:117 a=9W6Fsu4pMcyimqnCr1W0/w==:17 a=L9H7d07YOLsA:10 a=9cW_t1CCXrUA:10 a=s5jvgZ67dGcA:10 a=IkcTkHD0fZMA:10 a=GhZ5P8ky69gA:10 a=AYXDDH2dM-MA:10 a=jFJIQSaiL_oA:10 a=1qif6Q7Wo1rkBEPv1bEA:9 a=QEXdDO2ut3YA:10 Subject: Re: [PATCH] kernel/resource.c: fix muxed resource handling in __request_region() To: Alan Cox , Linus Torvalds References: <20150909220140.GD9892@kw.sim.vm.gnt> <1441836918-24159-1-git-send-email-simon.guinot@sequanux.org> <20160219221056.23487da2@x2> <56C7A459.1090801@virtuousgeek.org> <15300c0ce08.2710.f266623ac48c822f02e65082a71b2734@virtuousgeek.org> <1456148952.24303.273.camel@linux.intel.com> Cc: Vincent Pelletier , Simon Guinot , Giel van Schijndel , linux-gpio@vger.kernel.org, Linux Kernel Mailing List , Vincent Donnefort , Yoann Sculo From: Jesse Barnes Message-ID: <56CB7391.30203@virtuousgeek.org> Date: Mon, 22 Feb 2016 12:46:09 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.2.0 MIME-Version: 1.0 In-Reply-To: <1456148952.24303.273.camel@linux.intel.com> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Identified-User: {10642:box514.bluehost.com:virtuous:virtuousgeek.org} {sentby:smtp auth 98.207.216.137 authed with jbarnes@virtuousgeek.org} Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 02/22/2016 05:49 AM, Alan Cox wrote: >> we have some good alternatives in the form of bus and platform >> drivers that >> can manage the appropriate serialization and keep things from >> stomping >> on one another. > > It's not used much, especially nowdays. The use case is basically multi > I/O chips on the ISA/LPC bus with magic shared config register ports. > > We have sufficiently few of those we could give muxed the boot and > special case them if preferred. Ah that's right, now I remember the context. So where should we go from here then? Just leave the ugly fix in or hack on old stuff and hope not to break it? Jesse