Received: by 2002:a05:6358:3188:b0:123:57c1:9b43 with SMTP id q8csp2422986rwd; Fri, 26 May 2023 06:29:04 -0700 (PDT) X-Google-Smtp-Source: ACHHUZ7y8b/dmmxYIWqtJpRzxjxwcn20ki94Mammm1yB25QCWGGqnY99cWTi7qgC+h3qbS2Vxjks X-Received: by 2002:a05:6a21:99a2:b0:10f:f672:6e86 with SMTP id ve34-20020a056a2199a200b0010ff6726e86mr452212pzb.16.1685107744146; Fri, 26 May 2023 06:29:04 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1685107744; cv=none; d=google.com; s=arc-20160816; b=Plezl6oCz56Voi9VtvQ0JCzVjrtzNe9co5ywRVTwFLzjLhJ/3wMcyYUmDFfNtpFYgV Kmdg9d9qtKo87OspuVMsW5I4weGQPTBO80Ggewai2UreLo18Cxpnn+BmvQOVw7VJ7bEw prj4jesb9uLCWgemKNK9hBrdgIu90hfWpzMqAK4aDOjIW7+bbazaiZgtWeHadUwRW2wa 04UDfGIlr5NTJ1n/0ngAtqMSVno/dj/+TlKWqSnGl+VcLkFZYPgDHnOj9/Xtn1Kv+5za afMNRwoDkOC882Ul96bjDYbYavs62+sq9AAKOn5Z9BPZFisaRLvxIIKMiIgf5RHhDG/4 vKSw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:cc:to:subject :message-id:date:from:in-reply-to:references:mime-version :dkim-signature; bh=T8WfNbYjQtdKqhbV501fe9vtrkDkYbanF3BpFOEvVck=; b=u6e+LjtHA5k2OjiMJIh9r2OJcVY49lcJi+XvIWLgd4X6W+kbu9CLSVVl7LqgsJrJRG QEvWFUBtkB70+dz4N4rDHorcvHYhYxXZVF5UrW0QHIASrjHNRECBgmamFYUIJDgzvyxA sV1j29oEIiD47xkrmru1037dm/zxNAUGTyK5I0yq3AULqx/EIuIHJqCRXTrca7Y3z0wF P5ue1ZO17+c1EA9lRgNIpl+/18SnMmWR8RqlLkueFJpVi2Eb/dqozIKZ2+lZqbOs8NHU UHxJOjiS7r28NjZWHCfe/XKDCJTfRaPiydhte97Wh9S6dJnEt6MUyDJrGRzrP2JEMneB RJvA== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@bgdev-pl.20221208.gappssmtp.com header.s=20221208 header.b=yqyG72qt; 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 Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id v135-20020a63618d000000b0053f25f2d32fsi3737544pgb.831.2023.05.26.06.28.50; Fri, 26 May 2023 06:29:04 -0700 (PDT) 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=@bgdev-pl.20221208.gappssmtp.com header.s=20221208 header.b=yqyG72qt; 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 Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S243557AbjEZNNA (ORCPT + 99 others); Fri, 26 May 2023 09:13:00 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53050 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S243549AbjEZNM6 (ORCPT ); Fri, 26 May 2023 09:12:58 -0400 Received: from mail-vs1-xe2f.google.com (mail-vs1-xe2f.google.com [IPv6:2607:f8b0:4864:20::e2f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 101CF19D for ; Fri, 26 May 2023 06:12:56 -0700 (PDT) Received: by mail-vs1-xe2f.google.com with SMTP id ada2fe7eead31-437df8c864bso174848137.1 for ; Fri, 26 May 2023 06:12:55 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=bgdev-pl.20221208.gappssmtp.com; s=20221208; t=1685106775; x=1687698775; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:from:to:cc:subject:date :message-id:reply-to; bh=T8WfNbYjQtdKqhbV501fe9vtrkDkYbanF3BpFOEvVck=; b=yqyG72qta2r79hHfhtKEsQGBuGunOd35hSHz3b0TCfsYaXQgZCOckNAVlNJDtbrYfi iz9PEu7wdR8yxVI34ERSDlsTQQ/b0VzVMUiai3M+FOhRGKQcNnwCkPsCZi2ArY7YHWZZ l4FiCmMvHZq15vh7o2fZWLASXG4TauDaD/ACnV5Pshwckf8j5l5K59DQXfTMbCsvUDUw L20+aSIKQ/FGUh30jFY/222nBmCER4n/Vtx2CDBnFfQn1b6fomH+LziDAay4hK9W/esn 1XVrUM8U8d2D+ffLeLJEvXa9vOvVBHCbmFUvF+8Jh3sOkjWia1MVsF37y99P3WXi2AT1 wLYw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1685106775; x=1687698775; h=content-transfer-encoding:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:x-gm-message-state:from:to:cc :subject:date:message-id:reply-to; bh=T8WfNbYjQtdKqhbV501fe9vtrkDkYbanF3BpFOEvVck=; b=Moi3RuFZVnM47EBynwIo/bVXgWjmbxbWquyxZWqpRFjSs7w9xT3wdOIBzjYI6d/2oy V9W2fgzjXezCiiRyTYx2I384dF7Nfs8P1RrUcfU/ExNJnMYtn3kEOG/uIZBT8tIDiEoi GVMtmc6e+xBTD4aipFvvkAFWNumOyzjkU2IbvjmRYRBnI1wOpBpnIsEXpFMst02jGxFP ubLE7NZlL0Htw6XL1KQXvT9b7NTvR/bJQVhX0VTaoymtmuDIT7jkiKOa2hi9ezkIXN7I skXH7SRGc/77ZZrgDa4gD69ePvDa+gWysdd42Dd1TkfD8UZOLHQkjiuztzIKgjRdBVtt kDog== X-Gm-Message-State: AC+VfDwuRs/27h00pwGfjnXnOUgiWb9+O021JjNxVXpaEixWBNxmwd8x jyn5BcZzvjuzMoLrBTD9eetv/jVhXuic4FbHLBkTvQ== X-Received: by 2002:a05:6102:3019:b0:439:e3c:8ef8 with SMTP id s25-20020a056102301900b004390e3c8ef8mr426513vsa.28.1685106775067; Fri, 26 May 2023 06:12:55 -0700 (PDT) MIME-Version: 1.0 References: <20230506085928.933737-1-haibo.chen@nxp.com> <20230506085928.933737-2-haibo.chen@nxp.com> In-Reply-To: <20230506085928.933737-2-haibo.chen@nxp.com> From: Bartosz Golaszewski Date: Fri, 26 May 2023 15:12:44 +0200 Message-ID: Subject: Re: [PATCH 2/2] gpio: mxc: switch to dynamic allocat GPIO base To: haibo.chen@nxp.com Cc: linus.walleij@linaro.org, linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org, linux-imx@nxp.com, christophe.leroy@csgroup.eu Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE,URIBL_BLOCKED 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 Sat, May 6, 2023 at 10:56=E2=80=AFAM wrote: > > From: Haibo Chen > > gpiolib want to get completely rid of static gpiobase allocation, > so switch to dynamic allocat GPIO base, also can avoid warning > message: > > [ 1.529974] gpio gpiochip0: Static allocation of GPIO base > is deprecated, use dynamic allocation. > > Signed-off-by: Haibo Chen > --- > drivers/gpio/gpio-mxc.c | 3 +-- > 1 file changed, 1 insertion(+), 2 deletions(-) > > diff --git a/drivers/gpio/gpio-mxc.c b/drivers/gpio/gpio-mxc.c > index 9d0cec4b82a3..abc129a88a62 100644 > --- a/drivers/gpio/gpio-mxc.c > +++ b/drivers/gpio/gpio-mxc.c > @@ -462,8 +462,7 @@ static int mxc_gpio_probe(struct platform_device *pde= v) > port->gc.request =3D gpiochip_generic_request; > port->gc.free =3D gpiochip_generic_free; > port->gc.to_irq =3D mxc_gpio_to_irq; > - port->gc.base =3D (pdev->id < 0) ? of_alias_get_id(np, "gpio") * = 32 : > - pdev->id * 32; > + port->gc.base =3D -1; > > err =3D devm_gpiochip_add_data(&pdev->dev, &port->gc, port); > if (err) > -- > 2.34.1 > This is not the first time we're seeing someone submit this fix[1]. Unfortunately it's been brought to our attention that this breaks existing user-space scripts that rely on fixed GPIO numbering in sysfs. Bart [1] https://lore.kernel.org/lkml/CACRpkdYV3mHNYvBg1nf+12Q2XZH_g4iTrA2YB1SVQ= =3DROriRRgg@mail.gmail.com/T/