From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 4CD3CECAAD3 for ; Wed, 14 Sep 2022 13:03:13 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229815AbiINNDL (ORCPT ); Wed, 14 Sep 2022 09:03:11 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:36032 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229714AbiINNDK (ORCPT ); Wed, 14 Sep 2022 09:03:10 -0400 Received: from mga17.intel.com (mga17.intel.com [192.55.52.151]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 01E2D6051C; Wed, 14 Sep 2022 06:03:08 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1663160589; x=1694696589; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=G3nunHZw0HXOmsMTYrHCL5+tpvupI1xxfdIlN7QmvpA=; b=NclA4GOAqf5IuV9ARazQllWaZd6E/CtojvPWu/+mT0bAQ6ztpjJ+Hc5c P6e24wgjIFGACF2a9iggD1HA8WForMbBEtKclz2iUORfCQf+vg09+4zM8 Q1xncSSzQpO5J5HSf0OWtO5SgsuRg3cr0Z2Hr1YPPVhG3qPbY3wWMq0vl YmVatzY3kGNceHNTpiSgqdOzEHEN6h21Y/wN8IymC2cWlQQ4WNBGcaXiu G1B5QFFI6Kf5isUvreRZZBQH7dcpIqexA1y90/0LfC4NkTZpo7vMSw+Lf JXgQvD9tVZimTvBUE58kyghA1BNcdx4YwhEFhfQOk+oTPw+FCOxMz9dG9 A==; X-IronPort-AV: E=McAfee;i="6500,9779,10470"; a="278808403" X-IronPort-AV: E=Sophos;i="5.93,315,1654585200"; d="scan'208";a="278808403" Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga107.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Sep 2022 06:03:08 -0700 X-IronPort-AV: E=Sophos;i="5.93,315,1654585200"; d="scan'208";a="616856582" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga002-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Sep 2022 06:03:02 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1oYS2c-002DBl-1B; Wed, 14 Sep 2022 16:02:58 +0300 Date: Wed, 14 Sep 2022 16:02:58 +0300 From: Andy Shevchenko To: Linus Walleij Cc: Arnd Bergmann , Bartosz Golaszewski , Christophe Leroy , Geert Uytterhoeven , Keerthy , Russell King , Jonathan Corbet , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , "H. Peter Anvin" , Catalin Marinas , Will Deacon , Davide Ciminaghi , Linux Kernel Mailing List , "open list:GPIO SUBSYSTEM" , Linux ARM , Linux-Arch , linux-doc , x86@kernel.org Subject: Re: [PATCH v2 0/9] gpio: Get rid of ARCH_NR_GPIOS (v2) Message-ID: References: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: linux-arch@vger.kernel.org On Wed, Sep 14, 2022 at 02:38:53PM +0200, Linus Walleij wrote: > On Wed, Sep 7, 2022 at 12:15 PM Arnd Bergmann wrote: > > > >> drivers/gpio/gpio-sta2x11.c | 411 ----------------------- > (...) > > sta2x11 is an x86 driver, so not my area, but I think it would be > > best to kill off the entire platform rather than just its gpio > > driver, since everything needs to work together and it's clearly > > not functional at the moment. > > > > $ git grep -l STA2X11 > > Documentation/admin-guide/media/pci-cardlist.rst > > arch/x86/Kconfig > > arch/x86/include/asm/sta2x11.h > > arch/x86/pci/Makefile > > arch/x86/pci/sta2x11-fixup.c > > drivers/ata/ahci.c > > drivers/gpio/Kconfig > > drivers/gpio/Makefile > > drivers/gpio/gpio-sta2x11.c > > drivers/i2c/busses/Kconfig > > drivers/media/pci/Makefile > > drivers/media/pci/sta2x11/Kconfig > > drivers/media/pci/sta2x11/Makefile > > drivers/media/pci/sta2x11/sta2x11_vip.c > > drivers/media/pci/sta2x11/sta2x11_vip.h > > drivers/mfd/Kconfig > > drivers/mfd/Makefile > > drivers/mfd/sta2x11-mfd.c > > include/linux/mfd/sta2x11-mfd.h > > > > Removing the other sta2x11 bits (mfd, media, x86) should > > probably be done through the respective tree, but it would > > be good not to forget those. > > Andy is pretty much default x86 platform device maintainer, maybe > he can ACK or brief us on what he knows about the status of > STA2x11? Actually I have no idea about STA2x11, but in some thread I have noticed that there were people who know more on the topic and they told that removal is the right thing to do. Not sure how it should be done practically (driver-by-driver or altogether), Acked-by: Andy Shevchenko for either of the variants if it helps. -- With Best Regards, Andy Shevchenko From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 67951ECAAD8 for ; Wed, 14 Sep 2022 13:04:45 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=coHzuIkZoMlPqLRSdvr0yMgpbmG5Rppe5P/G5aNLqx0=; b=U7sYg2LENlCgp0 ooKNXi2jqfgXtC98+p55YokWO4s2FGmnMXjjRhx9vYGfCRf7D7c3nnTcfCHUgz2owBg72YR2/nSxw 0fOzwjwRRGlE4Dyzc/iMXxe/x/wXggNgGUdOEhkcTaJJz2OlKbnQW1VGzrYZoWPgie3/ux7+L26eO jyuE6ZrM2yvcMVhS1n+WHNT7KwSnNOuChx8fztHmxWeQWX7qAmqM2DNjeXqyC35jgR2XrZU2E4fMS 4kTATVwUhN4nIf1JOhY8M5iMRRvnqwp8L+lJNrHupA6Fi7X4WCPp5FQ/vYRPmrdjxAMWiN0F3t/9p qqC0be4/jwnoiDYxym9A==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.94.2 #2 (Red Hat Linux)) id 1oYS39-000Oi4-7p; Wed, 14 Sep 2022 13:03:31 +0000 Received: from mga14.intel.com ([192.55.52.115]) by bombadil.infradead.org with esmtps (Exim 4.94.2 #2 (Red Hat Linux)) id 1oYS35-000Od3-GU for linux-arm-kernel@lists.infradead.org; Wed, 14 Sep 2022 13:03:28 +0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1663160607; x=1694696607; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=G3nunHZw0HXOmsMTYrHCL5+tpvupI1xxfdIlN7QmvpA=; b=OvYVjACpO0NsaoyftSHsVbff8XmcJTP80QDNYVtVbzhpFtK8sqOgVVrr yrqaIgx/GKC9UhQFc1poTkRFrOuODdXvGkUbcXNnRlYaHVCZMax9tcJPY 9qLhKVvL8tCuAXZKP/Laf43mZ5jMztWC56j5+S7pK6e9jtyp6ywRhal1K k+J6l1AEWqhL+ML4U1VOGXFU27TfvD83P1ATNO9GwsdybwGutFSxWxYvq 10S7RxLnxIORHwYkX6X00C9BJgfX+bs+Q426neL/Ck4+oF3O5qJkSY1qA iC3LdpkJvw6k1ErxmyxNgU0270tjSOQ5l1S0U8Ic8wecqLWi2fxPs10YX A==; X-IronPort-AV: E=McAfee;i="6500,9779,10470"; a="298421279" X-IronPort-AV: E=Sophos;i="5.93,315,1654585200"; d="scan'208";a="298421279" Received: from orsmga002.jf.intel.com ([10.7.209.21]) by fmsmga103.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Sep 2022 06:03:08 -0700 X-IronPort-AV: E=Sophos;i="5.93,315,1654585200"; d="scan'208";a="616856582" Received: from smile.fi.intel.com ([10.237.72.54]) by orsmga002-auth.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 14 Sep 2022 06:03:02 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.96) (envelope-from ) id 1oYS2c-002DBl-1B; Wed, 14 Sep 2022 16:02:58 +0300 Date: Wed, 14 Sep 2022 16:02:58 +0300 From: Andy Shevchenko To: Linus Walleij Cc: Arnd Bergmann , Bartosz Golaszewski , Christophe Leroy , Geert Uytterhoeven , Keerthy , Russell King , Jonathan Corbet , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , "H. Peter Anvin" , Catalin Marinas , Will Deacon , Davide Ciminaghi , Linux Kernel Mailing List , "open list:GPIO SUBSYSTEM" , Linux ARM , Linux-Arch , linux-doc , x86@kernel.org Subject: Re: [PATCH v2 0/9] gpio: Get rid of ARCH_NR_GPIOS (v2) Message-ID: References: MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20220914_060327_597270_FB3F8F50 X-CRM114-Status: GOOD ( 23.84 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Wed, Sep 14, 2022 at 02:38:53PM +0200, Linus Walleij wrote: > On Wed, Sep 7, 2022 at 12:15 PM Arnd Bergmann wrote: > > > >> drivers/gpio/gpio-sta2x11.c | 411 ----------------------- > (...) > > sta2x11 is an x86 driver, so not my area, but I think it would be > > best to kill off the entire platform rather than just its gpio > > driver, since everything needs to work together and it's clearly > > not functional at the moment. > > > > $ git grep -l STA2X11 > > Documentation/admin-guide/media/pci-cardlist.rst > > arch/x86/Kconfig > > arch/x86/include/asm/sta2x11.h > > arch/x86/pci/Makefile > > arch/x86/pci/sta2x11-fixup.c > > drivers/ata/ahci.c > > drivers/gpio/Kconfig > > drivers/gpio/Makefile > > drivers/gpio/gpio-sta2x11.c > > drivers/i2c/busses/Kconfig > > drivers/media/pci/Makefile > > drivers/media/pci/sta2x11/Kconfig > > drivers/media/pci/sta2x11/Makefile > > drivers/media/pci/sta2x11/sta2x11_vip.c > > drivers/media/pci/sta2x11/sta2x11_vip.h > > drivers/mfd/Kconfig > > drivers/mfd/Makefile > > drivers/mfd/sta2x11-mfd.c > > include/linux/mfd/sta2x11-mfd.h > > > > Removing the other sta2x11 bits (mfd, media, x86) should > > probably be done through the respective tree, but it would > > be good not to forget those. > > Andy is pretty much default x86 platform device maintainer, maybe > he can ACK or brief us on what he knows about the status of > STA2x11? Actually I have no idea about STA2x11, but in some thread I have noticed that there were people who know more on the topic and they told that removal is the right thing to do. Not sure how it should be done practically (driver-by-driver or altogether), Acked-by: Andy Shevchenko for either of the variants if it helps. -- With Best Regards, Andy Shevchenko _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel