Received: by 2002:a05:6a10:22f:0:0:0:0 with SMTP id 15csp64867pxk; Thu, 10 Sep 2020 23:58:12 -0700 (PDT) X-Google-Smtp-Source: ABdhPJw5NhvyX2Vly3Gg8KS+U1n3snkxd9fN9L+nu2J/usK4FyMpC3q52tP6JQCGePHXuw85makB X-Received: by 2002:a17:906:bb06:: with SMTP id jz6mr719221ejb.248.1599807491823; Thu, 10 Sep 2020 23:58:11 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1599807491; cv=none; d=google.com; s=arc-20160816; b=J68wrleKnyuvQr7xdBv7Mo3h396HQObKQBmwy2K7FBZyPwD8zE3XiMEJ3nHy1fSzNw s3PFZyEY9vRmJV3HmpfpaK1HOkUoxoVY1WJn84BfDJ1IIfeDqmua+H1dY1rmn5dr2TT7 +6fpqoJCZTJwm5x+4uZNb5yzgo/Ks7mJwPTxRklAkji40LWNaJrnBWsLpMBFKspXcwi2 jUgQBokxC7zr0n+c/B7SEnYJOd2GlCLW6/NTZSIzWbdFOlapPp798Yyp1NYcUIMy2WxT 8OFKWOVlO2DmSuC37PXTD+o4dh4AJ3CAbDXf6Y8/wXQ46SxXEZcfM42z4tKGvF5l2lKX EUZw== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:cc:to:subject:message-id:date:from :in-reply-to:references:mime-version:dkim-signature; bh=0DRuxms1QaBkVUnjSgsQBvgmkJXEs7XbDQ+uXnkZqSk=; b=QU5xu5oKuNCxVbVDvgXaiuXQFjVxBThIrYWTYmPyWsgZ8E3vMSOjq/05z6/Whthq1q W3G2scLnFKR4Vm0xkgVbaH+b07ieZiv/mpkwdNTAW4zrg0Ofb6oOnRfRnLDtbPpPRH5R GXnkvhv2c12jlQgV2/3d3d1AFhacRlualSEHfX7siWgX9nC5TvlbrbS3OMlUfKIcc9wc K17UxAGc81skAETQsHlbWn1hJDsd5kgGIL3+0fF9donkcSvA6WjZxtOtB0qfFKUm43Wq /9ey4iYJ7diAfCa1fw4h9JaB98hKg4Zc2D0OTMYghcRp090pZc2j6lh6sJv4WlLYzZBT 0NeQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=JiQ0HGMp; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id i12si643194ejk.740.2020.09.10.23.57.49; Thu, 10 Sep 2020 23:58:11 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; dkim=pass header.i=@kernel.org header.s=default header.b=JiQ0HGMp; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1725648AbgIKGy5 (ORCPT + 99 others); Fri, 11 Sep 2020 02:54:57 -0400 Received: from mail.kernel.org ([198.145.29.99]:48234 "EHLO mail.kernel.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725497AbgIKGy4 (ORCPT ); Fri, 11 Sep 2020 02:54:56 -0400 Received: from mail-ej1-f50.google.com (mail-ej1-f50.google.com [209.85.218.50]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPSA id F097322205; Fri, 11 Sep 2020 06:54:54 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=default; t=1599807295; bh=LYU8Tb5GMA6mmuFbZxVtsFi/egUHKAmHaWZZIbnXOvo=; h=References:In-Reply-To:From:Date:Subject:To:Cc:From; b=JiQ0HGMpnHYgpuekKtUf+8YvvWXHzJEvW2KhxPV1s5oG+08DzzajE6E5TXHZ0XXAn GD28lSc5mGYQpc+tH2JXNbqpTqYfAtLUFNTrchaT69hRx45fzt/oWcj542xAqWz2U6 +nsbHt0tt1JmvAU8oVP2XU3yOLPlFIHlOTX7QtZ4= Received: by mail-ej1-f50.google.com with SMTP id lo4so12302677ejb.8; Thu, 10 Sep 2020 23:54:54 -0700 (PDT) X-Gm-Message-State: AOAM530ef8wsbEoFpHReTp79IIScPGu6EQLEncwTcsZxS/pDIEa6CS0Z mzijpHa4C0NWr7Us4tyYhHx1zE8FFHOUhTuLvAs= X-Received: by 2002:a17:906:4046:: with SMTP id y6mr730092ejj.148.1599807293350; Thu, 10 Sep 2020 23:54:53 -0700 (PDT) MIME-Version: 1.0 References: <20200910175733.11046-1-krzk@kernel.org> <20200910175733.11046-2-krzk@kernel.org> <20200910182814.veviax3n377undkv@akan> In-Reply-To: From: Krzysztof Kozlowski Date: Fri, 11 Sep 2020 08:54:40 +0200 X-Gmail-Original-Message-ID: Message-ID: Subject: Re: [PATCH v2 01/15] dt-bindings: gpio: convert bindings for NXP PCA953x family to dtschema To: Geert Uytterhoeven Cc: Nishanth Menon , Linus Walleij , Bartosz Golaszewski , Rob Herring , =?UTF-8?Q?Beno=C3=AEt_Cousson?= , Tony Lindgren , Russell King , Jason Cooper , Andrew Lunn , Gregory Clement , Sebastian Hesselbarth , Joel Stanley , Andrew Jeffery , Shawn Guo , Sascha Hauer , Pengutronix Kernel Team , NXP Linux Team , Matthias Brugger , Geert Uytterhoeven , Magnus Damm , Tero Kristo , Michal Simek , Guenter Roeck , "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , "linux-kernel@vger.kernel.org" , "open list:TI ETHERNET SWITCH DRIVER (CPSW)" , Linux ARM , linux-aspeed@lists.ozlabs.org, linux-mediatek@lists.infradead.org, Linux-Renesas Content-Type: text/plain; charset="UTF-8" Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 11 Sep 2020 at 08:42, Geert Uytterhoeven wrote: > > Hi Krzysztof, > > On Thu, Sep 10, 2020 at 8:54 PM Krzysztof Kozlowski wrote: > > On Thu, 10 Sep 2020 at 20:28, Nishanth Menon wrote: > > > On 19:57-20200910, Krzysztof Kozlowski wrote: > > > [...] > > > > + wakeup-source: > > > > + $ref: /schemas/types.yaml#/definitions/flag > > > > + > > > > +patternProperties: > > > > + "^(hog-[0-9]+|.+-hog(-[0-9]+)?)$": > > > > > > I wonder if "hog" is too generic and might clash with "something-hog" in > > > the future? > > > > This pattern is already used in > > Documentation/devicetree/bindings/gpio/fsl-imx-gpio.yaml. It will > > match only children and so far it did not find any other nodes in ARM > > and ARM64 dts. I don't expect clashes. Also the question is then - if > > one adds a child of GPIO expander named "foobar-hog" and it is not a > > GPIO hog, then what is it? > > Perhaps you didn't find any other nodes as children of pca953x > controllers? There shouldn't be.. unless one makes some i2c-gpio controller under such GPIO expander. But now it wouldn't be instantiated as expander is not a bus. > There are other hog nodes in other types of GPIO controllers. Typically > they're named after the purpose, e.g. "wifi-disable", "i2c3_mux_oe_n", > "pcie_sata_switch", "lcd0_mux". > > IMHO it's a hog if it contains a "gpio-hog" property, regardless of node > naming. Yes. The question is then whether to expect the "hog" in name. Just like we expect for all other device nodes to represent the class. Best regards, Krzysztof