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=-3.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SIGNED_OFF_BY, 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 7FCAFC43331 for ; Fri, 27 Mar 2020 10:44:39 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 4673420675 for ; Fri, 27 Mar 2020 10:44:39 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="g6zO4fwl" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726284AbgC0Koi (ORCPT ); Fri, 27 Mar 2020 06:44:38 -0400 Received: from mail-lf1-f66.google.com ([209.85.167.66]:37298 "EHLO mail-lf1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726165AbgC0Koi (ORCPT ); Fri, 27 Mar 2020 06:44:38 -0400 Received: by mail-lf1-f66.google.com with SMTP id j11so7439010lfg.4 for ; Fri, 27 Mar 2020 03:44:37 -0700 (PDT) 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=FtlB69zsXQ3jZC3Ou4ODecutdMyciF2dIlXSJMt4Mfg=; b=g6zO4fwl4il+1ngGF+DwBd1vdVdf7kaSs5lwCr+GzM1DLm2kDPzSp0moLsXpg7coL0 d8SpMq8pvZZGpYmcWO4qlED2aKQO2pYleVNFzi8/je6zi6l2968WMcYlGHR8k3SzsnMc emO1/ar+R2eVf0+co9Ady4ysnQn2nreGIXOPH/Q6bsVJ2z2+UeLauhB52ob/x/Z6JHtO Wb6+4/rxfLNFQUaGqD7ZUv+cKm6pE0J1rQ2Xmpc1q356r+nW6oXEqaBvg05CK8Wu+MJS kZTLa46dy6Co5v207HMmgVStBaNiMmhemnZ0R8Xib3M+WaWMWXW+klGjJGrEbK1unoEV H6Ag== 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=FtlB69zsXQ3jZC3Ou4ODecutdMyciF2dIlXSJMt4Mfg=; b=epsmb2btl4ItijHFm3tsw4YotfF7SLyt1mt+GScp62DjDiSDy14qaaeU52RiMotFn4 OJUJFJq5BDSnXLned0Fd/luhDFZmAKOxBrcC7ceDgQhKniI+lsZltrGFiQpX14kDJP21 gthOtt7QpeEdh20GPDFcyH8mK/XfS57oeNniJSGFoGMdXBZfQ8ksOgJa2kSjLMCIXbfm QQeK3O3Iqnb3br8EpbVVU+2rH2gUUNbQiyTUP5FPA3aGyt11yxc7FhOhwIyCvHACxxOa OgYl2GkTJIjlHTxsmS9aGoS9bR+0nOhAfr7Y0yRhDNAjh3gkg7bQ67IfsCsX2xai+3XJ EHEA== X-Gm-Message-State: AGi0PuZTgwWCUz56xfMBJZEoXwa7VjZXQO5R+X01pV5daZsrdjXA4cNC HVuHN7ZnqOkcnPHCDASV1639CJ9XNyqbasmcq1yKbw== X-Google-Smtp-Source: APiQypLg4J2wxtQtpU6V+oVRQ2MpdJ8cSTbdUaBYm7lcPMJnY84ukdy6OsUxN/Xk1eIyvSI4nSkEv3qVaOSGuyWOS80= X-Received: by 2002:a05:6512:6c4:: with SMTP id u4mr2047706lff.89.1585305876327; Fri, 27 Mar 2020 03:44:36 -0700 (PDT) MIME-Version: 1.0 References: <20200319122737.3063291-1-thierry.reding@gmail.com> <20200319122737.3063291-8-thierry.reding@gmail.com> In-Reply-To: <20200319122737.3063291-8-thierry.reding@gmail.com> From: Linus Walleij Date: Fri, 27 Mar 2020 11:44:25 +0100 Message-ID: Subject: Re: [PATCH 7/9] pinctrl: tegra: Do not add default pin range on Tegra194 To: Thierry Reding Cc: Bartosz Golaszewski , Jon Hunter , Vidya Sagar , "open list:GPIO SUBSYSTEM" , linux-tegra@vger.kernel.org Content-Type: text/plain; charset="UTF-8" Sender: linux-gpio-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-gpio@vger.kernel.org On Thu, Mar 19, 2020 at 1:28 PM Thierry Reding wrote: > From: Thierry Reding > > On Tegra194, almost all of the pin control programming happens in early > boot firmware, so there is no use in having a pin range defined for all > the pins. > > Signed-off-by: Thierry Reding Patch applied! Yours, Linus Walleij