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 Received: from bombadil.infradead.org (bombadil.infradead.org [198.137.202.133]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.lore.kernel.org (Postfix) with ESMTPS id 28BDCC3DA70 for ; Tue, 30 Jul 2024 19:11:23 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender:List-Subscribe:List-Help :List-Post:List-Archive:List-Unsubscribe:List-Id:In-Reply-To:Content-Type: MIME-Version:References:Message-ID:Subject:Cc:To:From:Date:Reply-To: Content-Transfer-Encoding:Content-ID:Content-Description:Resent-Date: Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID:List-Owner; bh=LZMZvRv7z8xqfeM2an7PKrVt8vHjAtd1rN561eLDxMk=; b=nDHutl910Z+MbAOXiTvZJ5ZRWM /JfwmBpQmoUXYj7Ffh7mmn5gsYqFKp1c18/KNwvzXaW2xwoDfFRzPYXJgkQx6/m55iMs9f7BhlcaO g5fsn9ytskH6R9qrRWU8CLoEm3K2YQgMY8mievNAnQG2KPqYCIVxDyVxqoxMA+vdyr84VQWHAb3RC evmZ3MWln8Ue0pVQdBVy5sLRPr6i4lZhKGnpdCv13S+/rGp85xbKckwwGNjDgsVHydK9hswrt5CFA MRVakJAZRd47tzcDGafgBTvVkhhNr+a6O7OGPBqi3SD/yyHWzzpvZ6sECT8tT7gSvbVDl1sOzNc8L 25jee5Ig==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1sYsFc-0000000GEiT-438r; Tue, 30 Jul 2024 19:11:12 +0000 Received: from sin.source.kernel.org ([2604:1380:40e1:4800::1]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1sYsFA-0000000GEbF-2gRY for linux-arm-kernel@lists.infradead.org; Tue, 30 Jul 2024 19:10:46 +0000 Received: from smtp.kernel.org (transwarp.subspace.kernel.org [100.75.92.58]) by sin.source.kernel.org (Postfix) with ESMTP id 6D0EECE1178; Tue, 30 Jul 2024 19:10:42 +0000 (UTC) Received: by smtp.kernel.org (Postfix) with ESMTPSA id 4CB6AC32782; Tue, 30 Jul 2024 19:10:40 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1722366640; bh=ZA62L/1AWmpvq2gPcEA68cAp/TI3YINGoR9uR6ivx68=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=tymP8zIvoylkYnhSwX3x/jkHNeWAVLplfFzyEYfGvKgbRKe9H1/FJ8LysRKuhnCH2 vSKeGmTqn33j48lbZAX5uCbqCkm0m2RGsAqy5v79dmEPGniCarzxhFvRZAaVZth/O6 3v8HN7jgxcfk/MUuvRJzhRpbjkSkL/v4Xm3JzW7VyfmM6hwGNg/diyTXDmj+cAbpMb oQ/hzUYlrqAnGOtDy7ZutQIvctBcm23XOb1F5eBlQ4Qliow2kVpqu5Iat2cdr0yAXV UP59Vb/NaVQFYGwjyaAJFQxxz+Ws9xCQ7i6ny4nOv7DAn3IvuMqcYGEUTY7LJdgBV8 tX/U15lpvN9Yg== Date: Tue, 30 Jul 2024 13:10:39 -0600 From: Rob Herring To: Markus Schneider-Pargmann Cc: Chandrasekar Ramakrishnan , Marc Kleine-Budde , Vincent Mailhol , "David S . Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Krzysztof Kozlowski , Conor Dooley , Nishanth Menon , Vignesh Raghavendra , Tero Kristo , Martin =?iso-8859-1?Q?Hundeb=F8ll?= , Christophe JAILLET , Michal Kubiak , Vibhore Vardhan , Kevin Hilman , Dhruva Gole , Conor Dooley , linux-can@vger.kernel.org, netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-arm-kernel@lists.infradead.org Subject: Re: [PATCH v2 1/7] dt-bindings: can: m_can: Add wakeup properties Message-ID: <20240730191039.GA1959067-robh@kernel.org> References: <20240729074135.3850634-1-msp@baylibre.com> <20240729074135.3850634-2-msp@baylibre.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20240729074135.3850634-2-msp@baylibre.com> X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240730_121045_046033_B1607505 X-CRM114-Status: GOOD ( 21.69 ) X-BeenThere: linux-arm-kernel@lists.infradead.org X-Mailman-Version: 2.1.34 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org On Mon, Jul 29, 2024 at 09:41:29AM +0200, Markus Schneider-Pargmann wrote: > m_can can be a wakeup source on some devices. Especially on some of the > am62* SoCs pins, connected to m_can in the mcu, can be used to wakeup > the SoC. > > The wakeup-source property defines on which devices m_can can be used > for wakeup. > > The pins associated with m_can have to have a special configuration to > be able to wakeup the SoC. This configuration is described in the wakeup > pinctrl state while the default state describes the default > configuration. > > Signed-off-by: Markus Schneider-Pargmann > --- > .../bindings/net/can/bosch,m_can.yaml | 20 +++++++++++++++++++ > 1 file changed, 20 insertions(+) > > diff --git a/Documentation/devicetree/bindings/net/can/bosch,m_can.yaml b/Documentation/devicetree/bindings/net/can/bosch,m_can.yaml > index c4887522e8fe..ef63f6b8455d 100644 > --- a/Documentation/devicetree/bindings/net/can/bosch,m_can.yaml > +++ b/Documentation/devicetree/bindings/net/can/bosch,m_can.yaml > @@ -106,6 +106,22 @@ properties: > maximum: 32 > minItems: 1 > > + pinctrl-0: > + description: Default pinctrl state > + > + pinctrl-1: > + description: Wakeup pinctrl state > + > + pinctrl-names: > + description: > + When present should contain at least "default" describing the default pin > + states. The second state called "wakeup" describes the pins in their > + wakeup configuration required to exit sleep states. > + minItems: 1 > + items: > + - const: default > + - const: wakeup > + > power-domains: > description: > Power domain provider node and an args specifier containing > @@ -122,6 +138,10 @@ properties: > minItems: 1 > maxItems: 2 > > + wakeup-source: > + $ref: /schemas/types.yaml#/definitions/flag I thought we had a common schema defining the type, but we don't. I'm going to add it now. So just need: wakeup-source: true > + description: This device is capable to wakeup the SoC. > + > required: > - compatible > - reg > -- > 2.45.2 >