Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
From:   Dhruva Gole <d-gole@ti.com>
To:     Tony Lindgren <tony@atomide.com>,
        Linus Walleij <linus.walleij@linaro.org>,
        Conor Dooley <conor+dt@kernel.org>
CC:     <linux-gpio@vger.kernel.org>, <devicetree@vger.kernel.org>,
        <linux-kernel@vger.kernel.org>,
        <linux-arm-kernel@lists.infradead.org>,
        <linux-omap@vger.kernel.org>, Dhruva Gole <d-gole@ti.com>,
        Nishanth Menon <nm@ti.com>,
        Vignesh Raghavendra <vigneshr@ti.com>,
        Conor Dooley <conor.dooley@microchip.com>,
        Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
        Rob Herring <robh+dt@kernel.org>,
        Haojian Zhuang <haojian.zhuang@linaro.org>
Subject: [PATCH 0/2] pinctrl-single: introduce am654-padconf compatible
Date:   Tue, 8 Aug 2023 15:52:06 +0530
Message-ID: <20230808102207.130177-1-d-gole@ti.com>
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Content-Type: text/plain
Precedence: bulk

The K3 family of SOCs use certain bits of the padconfig registers like
WKUP_EVT and WKUP_EN to enable daisychain wakeups.

For example, these bits are described in the AM654 TRM [0] under
"Table 5-517. Description Of The Pad Configuration Register Bits"

This series adds the DT binding changes for adding the compatible and
also the driver changes which make use of this compatible.

NOTE: Some K3 SoCs may have these bits marked as reserved which means
that they don't support IO daisychain. Such SOCs are not expected to use
this compatible.

The general expected usage is when the device is in a suspended state like Deep
Sleep or Suspend to RAM, and any IO activity on configured pads can
trigger a wakeup.

Link to complete series:
https://lore.kernel.org/all/20230808102207.130177-1-d-gole@ti.com

Base commit:
71cd4fc492ec (tag: next-20230808, linux-next/master) Add linux-next specific files for 20230808

depends on:
https://lore.kernel.org/r/20230721082654.27036-1-tony@atomide.com

which has been picked up by Linus Walleij in his tree here:
https://git.kernel.org/pub/scm/linux/kernel/git/linusw/linux-pinctrl.git/commit/?h=devel&id=677a62482bd6e584f83d0342e78735e3cd449ba4

However, it hasn't reflected in -next yet so specifying the depends on
above.

[0] https://www.ti.com/lit/pdf/spruid7

Cc: Nishanth Menon <nm@ti.com>
Cc: Vignesh Raghavendra <vigneshr@ti.com>
Cc: Tony Lindgren <tony@atomide.com>
Cc: Conor Dooley <conor.dooley@microchip.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
Cc: Rob Herring <robh+dt@kernel.org>
Cc: Haojian Zhuang <haojian.zhuang@linaro.org>

Dhruva Gole (1):
  dt-bindings: pinctrl: pinctrl-single: add ti,am654-padconf compatible

Tony Lindgren (1):
  pinctrl: single: Add compatible for ti,am654-padconf

 .../devicetree/bindings/pinctrl/pinctrl-single.yaml        | 1 +
 drivers/pinctrl/pinctrl-single.c                           | 7 +++++++
 2 files changed, 8 insertions(+)

-- 
2.34.1