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 5ECBAECAAD7 for ; Fri, 26 Aug 2022 13:50:08 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1344354AbiHZNuG (ORCPT ); Fri, 26 Aug 2022 09:50:06 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:49496 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1343588AbiHZNuD (ORCPT ); Fri, 26 Aug 2022 09:50:03 -0400 Received: from mail-ej1-x62d.google.com (mail-ej1-x62d.google.com [IPv6:2a00:1450:4864:20::62d]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D697043E4F for ; Fri, 26 Aug 2022 06:50:01 -0700 (PDT) Received: by mail-ej1-x62d.google.com with SMTP id fy31so2866465ejc.6 for ; Fri, 26 Aug 2022 06:50:01 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:from:to:cc; bh=TG9FgVqi16LcRZPucuD11y6AVi0ILI4JGPeRwHluIjU=; b=qQFNTe2hotOb/o+XOeHSkNh888Wv+A2OI6RACKCB02wfnqsHW4VhBNwljxGBpS1Gpz QzwBobxjyttdHvpFMxSzwTBJc6nskaYQKhjy4qp15F+GO7fOxdPofwo2tjIQ/Bj2zzaG 4bzrfDgnRkWXqar/grl2RqNi04r//6jMafKhgvFkRcCBPeXGG7Z/MHTYd2Hh9b1keAM8 BKfTjHKdE1PyvDKSZ2FB3yQybF5oPbm+wPQSHqlwWe2QPLP1V9/fE/6kxZDdJglbNaIW v4oYyDH2Y6dmnvQt9URauX0Qoi/3u2ppiL2irvaLRYH8RwSMqq9nWojbqd4l7Fb6wlGs XTaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=cc:to:subject:message-id:date:from:in-reply-to:references :mime-version:x-gm-message-state:from:to:cc; bh=TG9FgVqi16LcRZPucuD11y6AVi0ILI4JGPeRwHluIjU=; b=WxuDtzHcOGcz2ReDCTwYA95uIdP9w1JsENUbTF5RKzh2IdHHio/4nMzqEmOXC96D1D J0OmKeqNsofYMJvnqQaUGcq9pPy2hADgdXFFCZxUV+pph6wFC8heLbesuN8qS5VeoiuF zfTttVB63w9wP6uL+KQHaWJyDEszo9UG4eW3XG3l6oEEmmbvgvXBtwfzq/vkeSTaHrn4 divbxGVKBnlNXFUwUidNvV/Lko/F17mh6H4zBWuB0X/kS21OoywGGp2AsBDdWsVCmh/P bHTm/UA9EVJ/i/2A5uh8P40RTIgxDcixsS9vNgY3p2sFXhukzqZCwFv1jdKzDI6atKkx gZbA== X-Gm-Message-State: ACgBeo1MFyIrPh/WrA1TwTcqS5b+MMwt8ftVCOTFz7RtdtUxSMHT/7mO 8lvD061G17tIJkaaW3YFThkJlDJeruFDybNyAwZpvg== X-Google-Smtp-Source: AA6agR5u0kMHIqr2Sykv6xwyKqyIoWq4UaK5pcx+HYQdU9jyokivM4Cu/SHtZ0DUaUkVm8ttZKbzeve9caR+0zBdJbY= X-Received: by 2002:a17:907:72cf:b0:73d:d007:e249 with SMTP id du15-20020a17090772cf00b0073dd007e249mr5333295ejc.500.1661521800345; Fri, 26 Aug 2022 06:50:00 -0700 (PDT) MIME-Version: 1.0 References: <87f2ff4c-3426-201c-df86-2d06d3587a20@csgroup.eu> In-Reply-To: <87f2ff4c-3426-201c-df86-2d06d3587a20@csgroup.eu> From: Linus Walleij Date: Fri, 26 Aug 2022 15:49:49 +0200 Message-ID: Subject: Re: [PATCH] gpio: Allow user to customise maximum number of GPIOs To: Christophe Leroy Cc: Arnd Bergmann , Alexandre Courbot , Alexandre Courbot , Bartosz Golaszewski , Jonathan Corbet , Russell King , Thomas Gleixner , Ingo Molnar , Borislav Petkov , Dave Hansen , "maintainer:X86 ARCHITECTURE (32-BIT AND 64-BIT)" , "H. Peter Anvin" , "open list:GPIO SUBSYSTEM" , "open list:DOCUMENTATION" , open list , "moderated list:ARM PORT" , "open list:GENERIC INCLUDE/ASM HEADER FILES" Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Thu, Aug 25, 2022 at 4:00 PM Christophe Leroy wrote: > > Christophe? Will you take a stab at it? > > Which patch should I write ? One that removes CONFIG_ARCH_HAS_NR_GPIO entirely, then allocate bases for new GPIO chips from 0 and upward instead. And then see what happens. Yours, Linus Walleij