Received: by 2002:a05:6358:d09b:b0:dc:cd0c:909e with SMTP id jc27csp1002864rwb; Wed, 7 Dec 2022 07:32:33 -0800 (PST) X-Google-Smtp-Source: AA0mqf4AKBtRcZFHPPt43qjlVyNN8DtWg57ZIljgvzWYXJhR4yu30yWgUXh6oZh/+4mhd+hMzZB5 X-Received: by 2002:a63:3756:0:b0:478:d3a9:697 with SMTP id g22-20020a633756000000b00478d3a90697mr9353675pgn.244.1670427153385; Wed, 07 Dec 2022 07:32:33 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1670427153; cv=none; d=google.com; s=arc-20160816; b=N0f9MRBODK94iVAKDPo1b3WFTvSKjWv5Euctg+sbQNwME50ENzC6ZvoMf8bjg8+4K8 7gfcrbveZXP9BoVLVIUyauVQJSupIQTlyAhPiqVG11JNts9e2JZwMW7X13idAeTflKci owqM/zE21TeYBeD0hr/+CivgtNUe0rj3NN/bFJ2w9ig3iTHcheRWMsYAqEbfdV95Vz4v 3FkpRNfvCtRiu5ovW/A3Hz79ChQPjFCbH5iN9GoIfXFnQ/uF38Own2BokS4KFBcE/ByK 5sOHseEnnFNsdWdNKG6i9NB2EOuU6STjp8ftYfLPtQp2wh3Qhx1NuTy8nV3hxexzZjtF tAlA== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-transfer-encoding :content-disposition:mime-version:references:message-id:subject:cc :to:from:date:dkim-signature; bh=zj38BmnGOye72rpiBgZnGVHn0M0x17AYI3xiFJfGamY=; b=tYyzXcX28KukKc5IW1ZYPyur84oeoIdJ6YBcPCh/Dp1kxork2IU0XWJZ9UFAKM4ZFq Fy62Jf7n5svI+/bE1rIVQG6qX1o37XbinkJgfVAdSovI58Pn215kNIjghZaLYuXABk9A 78I1M6OTcvStG2qo+8GTK1AKBlsBuSfVivOq5F9xn0V5baFUXNcWeZOyNSg8INO0oP66 vRyjZqaYdw54OfuBQ2Qm9yyvQd/q4s3iKX7xCz8P+uFkn6T8+R91QVbCG7SfPpPXK5uH mp0qr9E6sSZhw6YEHrDqM4bUuCipO3xqOy5gZBPI4wSVHoS4znX81YKHQiJ5iF5uBKX9 U+ug== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b=MDyre4p9; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=lunn.ch Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id e6-20020a170902ef4600b00189ccadd447si11632642plx.101.2022.12.07.07.32.23; Wed, 07 Dec 2022 07:32:33 -0800 (PST) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20; Authentication-Results: mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b=MDyre4p9; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=lunn.ch Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229755AbiLGP2d (ORCPT + 77 others); Wed, 7 Dec 2022 10:28:33 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37622 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229677AbiLGP2c (ORCPT ); Wed, 7 Dec 2022 10:28:32 -0500 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 4128C442DE for ; Wed, 7 Dec 2022 07:28:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Transfer-Encoding:Content-Disposition: Content-Type:MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:From: Sender:Reply-To:Subject:Date:Message-ID:To:Cc:MIME-Version:Content-Type: Content-Transfer-Encoding:Content-ID:Content-Description:Content-Disposition: In-Reply-To:References; bh=zj38BmnGOye72rpiBgZnGVHn0M0x17AYI3xiFJfGamY=; b=MD yre4p9nlS6VFm88/M8cPU1gOy1YXjfBRqWchbz3CCvi7RrMj8hkRNuUPAiYKRc/euU/RV/151R8Nb bJntvRsGagibx2zMo5zJTUkq4dSc1wnV+XE/4TleHSPgZTBnun43Vczgel+3iv8glVXR/RG3bnVDh mRG5YOb+E/d8rro=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1p2wL9-004fNs-43; Wed, 07 Dec 2022 16:28:07 +0100 Date: Wed, 7 Dec 2022 16:28:07 +0100 From: Andrew Lunn To: Jonathan =?iso-8859-1?Q?Neusch=E4fer?= Cc: linux-arm-kernel@lists.infradead.org, Robert Jarzmik , Haojian Zhuang , Daniel Mack , linux-kernel@vger.kernel.org Subject: Re: PXA25x: GPIO driver fails probe due to resource conflict with pinctrl driver Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS autolearn=ham autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Dec 07, 2022 at 12:25:53PM +0100, Jonathan Neusch?fer wrote: > Hello, > > I am currently trying to bring up Linux 6.1-rcX on a PXA255 board, using a > devicetree. One problem I encountered is that the PXA GPIO driver fails to > probe because it uses the same MMIO register range as the pinctrl driver: > > [ 0.666169] pxa25x-pinctrl 40e00054.pinctrl: initialized pxa2xx pinctrl driver > [ 0.694407] pxa-gpio 40e00000.gpio: can't request region for resource [mem 0x40e00000-0x40e0ffff] > [ 0.695050] pxa-gpio: probe of 40e00000.gpio failed with error -16 > > Before I try to fix this myself: Is GPIO on PXA25x currently expected to > work and when has it last been seen working? > > What would be a good way to fix this? How are the registers arranged? Is 0x40e00000-0x40e0ffff simply too large, and making it smaller would fix the issue? Or are the registers interleaved? It is possible to request a region in a non-exclusive manor. Or is it more than interleaving, individual registers need to be shared between the two drivers? If so, you have the locking issues you mentioned. Andrew