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, 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 55667C2BA19 for ; Sat, 11 Apr 2020 22:35:03 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id 0D3A920769 for ; Sat, 11 Apr 2020 22:35:03 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=baylibre-com.20150623.gappssmtp.com header.i=@baylibre-com.20150623.gappssmtp.com header.b="JpZPZ5IJ" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726822AbgDKWfA (ORCPT ); Sat, 11 Apr 2020 18:35:00 -0400 Received: from mail-wm1-f65.google.com ([209.85.128.65]:38254 "EHLO mail-wm1-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726167AbgDKWe7 (ORCPT ); Sat, 11 Apr 2020 18:34:59 -0400 Received: by mail-wm1-f65.google.com with SMTP id f20so6263613wmh.3 for ; Sat, 11 Apr 2020 15:34:58 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=baylibre-com.20150623.gappssmtp.com; s=20150623; h=references:user-agent:from:to:cc:subject:in-reply-to:date :message-id:mime-version; bh=XTdhg+Xlf5WPZXZz0XSsY6zvLdLYzEpOReg3X3kD96s=; b=JpZPZ5IJaM6K9R8SqSPXG0qjQfqrwlkbzbZZRg+FRlF+C+xU5GZNWXJIuJjaMVjvsH WOmjPIa1UTU0gYkdITU0E91PWY2iqfSD3OCc0sRJOH53X6dgyk/nnS+ubn5oMIkBP4Ef wjRUmkDWldZPFhHGJw++v2MKpYpolwfx3SDEL75DY9Sg9zCmG8ITuKyvcWyDOo6w+TbB uEOIm9N59Kp5eueUtfhc/c085zbWjQP9uLYQeqM7tBG6cULZx5EE56zjVVROlWNxzjNt X54RVEx/HGh3owKuNAoLOU0ihXq7+DyCkriblVSHtjjS1RD8Uev1Eyz6FLns7U34cZcI vEZg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:references:user-agent:from:to:cc:subject :in-reply-to:date:message-id:mime-version; bh=XTdhg+Xlf5WPZXZz0XSsY6zvLdLYzEpOReg3X3kD96s=; b=nUebI/Q4YG7yomvborjbxuROPBC3k+4wMH7NcWQOTs8Trve3ajSUA1Qov+QrsX5Te3 XCMm4tIjP08bMAxQjfexvjvvI9Krwg4l4MTrCdvZZnt8B908elnO1emAe34vzLSkApVf 2zVLUTg9y95EzjnTINpO0lzDhhnc5kTG/rJeEX7Zk7+c+4Xhm+KxqeXrBVVmZBZKtEjh 64HeTbYetY252M+eorK6qgk8d0UYogUJD9Iujragk7FjIIOoxYeOiCNGi2Y/Yf7A+I0o 7tLHHyRwI8+JeeAG3uzGZFywUIYNo2mXrm73auO+fLmkiyiF12Bsi3tr4XG+Z/It4Tib SiRA== X-Gm-Message-State: AGi0Pub4YJBe6w7tOgt37kerI3tuApqieUf4hJnzC1xPZ3Wn5R3nTVbN WzoseKmC0a6E37uV+5Kcxrl9wA== X-Google-Smtp-Source: APiQypLX5XnwJtkOI7FJ21vIuZMoYF8VfN0lscJ3iVpl8y6O/opkC8sIkWHHFQs0s3CaoWUAM16DZQ== X-Received: by 2002:a1c:7308:: with SMTP id d8mr12144840wmb.31.1586644498242; Sat, 11 Apr 2020 15:34:58 -0700 (PDT) Received: from localhost (cag06-3-82-243-161-21.fbx.proxad.net. [82.243.161.21]) by smtp.gmail.com with ESMTPSA id s24sm7127097wmj.28.2020.04.11.15.34.57 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Sat, 11 Apr 2020 15:34:57 -0700 (PDT) References: <20200411170356.1578031-1-martin.blumenstingl@googlemail.com> <20200411170356.1578031-3-martin.blumenstingl@googlemail.com> <1jlfn2szqp.fsf@starbuckisacylon.baylibre.com> User-agent: mu4e 1.3.3; emacs 26.3 From: Jerome Brunet To: Martin Blumenstingl Cc: linus.walleij@linaro.org, linux-gpio@vger.kernel.org, linux-amlogic@lists.infradead.org, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH RFC v1 2/2] pinctrl: meson: wire up the gpio_chip's set_config callback In-reply-to: Date: Sun, 12 Apr 2020 00:34:56 +0200 Message-ID: <1jk12ltzvz.fsf@starbuckisacylon.baylibre.com> MIME-Version: 1.0 Content-Type: text/plain Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Sat 11 Apr 2020 at 22:53, Martin Blumenstingl wrote: > >> There is an example of that in meson-gx-libretech-pc.dtsi with the phy >> irq pin. > I'm still hoping that pinctrl-meson will gain interrupt support one > day, then the driver will (hopefully) take care of that :-) I don't see why it should. If the meson gpio driver was able to provide an irq related to gpio, I don't think it should do more than that. In most case the gpio will be an input, yes, but nothing says it must. > > > Martin