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=-0.8 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS 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 65F79C4332B for ; Fri, 20 Mar 2020 19:38:02 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 35EF120777 for ; Fri, 20 Mar 2020 19:38:02 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=linaro.org header.i=@linaro.org header.b="H29ke979" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726958AbgCTTiB (ORCPT ); Fri, 20 Mar 2020 15:38:01 -0400 Received: from mail-lj1-f196.google.com ([209.85.208.196]:42705 "EHLO mail-lj1-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726666AbgCTTiB (ORCPT ); Fri, 20 Mar 2020 15:38:01 -0400 Received: by mail-lj1-f196.google.com with SMTP id q19so7689825ljp.9 for ; Fri, 20 Mar 2020 12:38:00 -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=ojBDNVVg2fruS6vU66MRKq2HphKitUxDIf4Wi5OElFk=; b=H29ke979CtIKPWckEzUsuYpeXcJn0yGKplWCTRwGM38fgiEfzXjeBDHupe4dl10PrI CN0AFHW/1Z5WOi+UnkdWwHAYQzubLXn73uFsjOo36z6T4W1EMTPZf/hi9xOaVdG8H82J qX8uoyevm/RinEbzHtxs0LF1rPpi44bxfB3bi2dC5uzMnYkDKnyZ4zYV9f3lJWNA3SJV N97KMy84ehMTl3BFk9mt9XnN6L4sIiOAHJ42Ym0gTFtLtDcxWsbRK9F72+TnHlCnh543 CKbJ8KOBio9nCiPiewrxFtweoctesYfXHk4KxA0CHTWZVYUKfcOE7zhnA0WSTgE56alC KkTQ== 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=ojBDNVVg2fruS6vU66MRKq2HphKitUxDIf4Wi5OElFk=; b=f+G7djEuldbm+gWkyPt9EDhE6OszaIlDHu1z7/70MBXjmbr5fwbV+hQ441EtOqb25Z yHsBJkw33XJFzV6YAYdgwnyxpo88lvgz+u0UZFlVQxJWHBBKPmhZrpi8lWcs8L2pnsBB 3R2Lf5HepLQOdsJ8QRc/u3FrP87Fyvu/ygbTJitGNL3ryq8HDrEpVYxHlHEyA4xEzc/p ubEeq5TmRuet92oqhVOB/LppCpJeJnNjmL7Ixcsv6nkRf03dPu+WxGKq55V1ENsaIowp Vz9RXC/1JpGRRL4Pd274XDylqC/sd8CdbcfmYdQPsoyL7MLDGAvt660mjU4uSinYZ5t1 B9Qw== X-Gm-Message-State: ANhLgQ0sekuMJ3BSd8BeCOqqIheNdULkwp6QR8W8RvJICvzcVl3AEFm0 9j9ia57x+JMsmJFCgiXzZyG1OmOHCmgQS10XuRYU0w== X-Google-Smtp-Source: ADFU+vuS/9xB6+q0ZbkIaydrAFCWP+otW9O2k853/zfcdsFkYFBJ+y+LfbWH+y3RZhI4HpxkzNuRYB/RfAI/RH68lyk= X-Received: by 2002:a2e:9a90:: with SMTP id p16mr6558605lji.277.1584733079409; Fri, 20 Mar 2020 12:37:59 -0700 (PDT) MIME-Version: 1.0 References: <20200319122737.3063291-1-thierry.reding@gmail.com> In-Reply-To: <20200319122737.3063291-1-thierry.reding@gmail.com> From: Linus Walleij Date: Fri, 20 Mar 2020 20:37:48 +0100 Message-ID: Subject: Re: [PATCH 0/9] pinctrl: tegra: Support SFIO/GPIO programming 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:27 PM Thierry Reding wrote: > This series of patches establishes the mapping of these two pins to > their GPIO equivalents and implements the code necessary to switch > between SFIO and GPIO modes when the kernel requests or releases the > GPIOs, respectively. Is it possible to apply the gpio and pinctrl patches to each tree separately? Yours, Linus Walleij