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 X-Spam-Level: X-Spam-Status: No, score=-5.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI, SPF_HELO_NONE,SPF_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 392AEC433E0 for ; Fri, 12 Feb 2021 08:27:04 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 027E064E57 for ; Fri, 12 Feb 2021 08:27:03 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S229965AbhBLI1D (ORCPT ); Fri, 12 Feb 2021 03:27:03 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:45020 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229608AbhBLI1C (ORCPT ); Fri, 12 Feb 2021 03:27:02 -0500 Received: from mail-lj1-x22e.google.com (mail-lj1-x22e.google.com [IPv6:2a00:1450:4864:20::22e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 84C31C061574 for ; Fri, 12 Feb 2021 00:26:21 -0800 (PST) Received: by mail-lj1-x22e.google.com with SMTP id u4so10587485ljh.6 for ; Fri, 12 Feb 2021 00:26:21 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=t1ZkuB2+BZl7gZWvol4UUD/+B0R05rMTkvXfoQW6qLQ=; b=e5JRkx8lhBunhzO9peGsC0U3O5Tjj7YO2LQ7itbrLjCECEZdYZSfO6VrlwWTnTDJEM QPXM2Tw79Ii+TsaaFOnpOTt0/mGl8qJMJW4vFLQBmCjNoA4gcf4NTxIF0bACJme2fGSG NXwPxYw83hbDq6UJZ0RwEFqe0vzgP3wnC17aq8EuROgYpWX2qzUHTsQX2Og0sCKRY2iM zNWKZ/VXGFWjzEAsHyzhD4PiTeF0BEoxwEhv4qAOPudzHiHTuCqxejCP9RDiBdjJXAv+ eKvXO5QrOILU86mlWpT3YGKkgkAiaYRa1tZR92VGzcgNPNgxVad5U9F1/7jTeLkxzjnt 4OiQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=t1ZkuB2+BZl7gZWvol4UUD/+B0R05rMTkvXfoQW6qLQ=; b=jxmrWzcV6e/imbnLrnCXWsS7W4M6d9e77GIqaZOfz8tjadCE5Xttn6WhWWzYpDgno4 0Dr55V+vhXVLrravYvvE7oLZadhXqdwBo5wjnzrpp9706FfjD5iTxIPHpcjHsqJ8u3Ly s4mXOpLiy3Mkzo11rNsCCBjLyNbNxATTgmnvuU54JMeeGpia2ja69VBHuX2XweKYBZaG MgwIjECZrS+Jwg2abxyxLeZ5xwuCP8DrvhhzA7fj7xBrdx1ud2Y2tbSHFg0pDhFQz2JL jS4EpF1csjSeV0RqNKUFMalR01FHfHy1b9H0mPAvkmgYCB/+G9acEK7CnWWPb5eACrgt 4Uqw== X-Gm-Message-State: AOAM530kuSSyYx8Fs+43WZ4d8TaYPXoh5rAIzDb3Hn8A5z6KX4/UJadO qu/gsObm8VMeR3ITLvz50FiVKzB75e9JF54ggpNkTEfBAHOiAA== X-Google-Smtp-Source: ABdhPJxp0b2VxPCWon81vj38O3h55ZYX6ktoTsbasWZrHOTZ/YMHR0KolMG3ny2T8eGLQT0xD02R6tB3IqfRNHadkxU= X-Received: by 2002:a05:651c:32a:: with SMTP id b10mr1071370ljp.438.1613118380081; Fri, 12 Feb 2021 00:26:20 -0800 (PST) MIME-Version: 1.0 References: <20210130082128.3778939-1-michael@amarulasolutions.com> In-Reply-To: From: Linus Walleij Date: Fri, 12 Feb 2021 09:26:09 +0100 Message-ID: Subject: Re: [PATCH] pinctrl: Support pin that does not support configuration option To: Michael Nazzareno Trimarchi Cc: Fabio Estevam , Dong Aisheng , "open list:GPIO SUBSYSTEM" , linux-kernel , Sascha Hauer , Angelo Compagnucci Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Mon, Feb 1, 2021 at 12:54 PM Michael Nazzareno Trimarchi wrote: > On Mon, Feb 1, 2021 at 12:47 PM Fabio Estevam wrote: > > > > Hi Michael, > > > > On Sat, Jan 30, 2021 at 5:21 AM Michael Trimarchi > > wrote: > > > > > > Some of the iMX25 pins have not an associated configuration register so > > > when they are configured the standard way through the device tree the > > > kernel complains with: > > > > > > imx25-pinctrl 43fac000.iomuxc: Pin(MX25_PAD_EXT_ARMCLK) does not support > > > config function > > > > Could you please share your device tree that causes this warning? > > > > Shouldn't you pass 0x80000000 in the devicetree for this pad then? > > > > 0x80000000 means that the kernel should not touch the PAD_CTL register > > and use the default configuration from the bootloader/POR. > > arch/arm/boot/dts/imx25-lisa.dts: > MX25_PAD_EXT_ARMCLK__GPIO_3_15 0x80000000 > > The problem that exists pad that can be muxed but not configured Did you reach any conclusion on this? I need Fabio's consent to apply the patch, but it seems maybe the DTS should be changed instead? Yours, Linus Walleij