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 C9D96C4829A for ; Tue, 13 Feb 2024 08:56:55 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lists.infradead.org; s=bombadil.20210309; h=Sender: Content-Transfer-Encoding:Content-Type:List-Subscribe:List-Help:List-Post: List-Archive:List-Unsubscribe:List-Id:In-Reply-To:MIME-Version:References: Message-ID:Subject:Cc:To:From:Date:Reply-To:Content-ID:Content-Description: Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc:Resent-Message-ID: List-Owner; bh=wfL2j9vKcijDwL3iTSmbU5rMNlZf7gBonGD5ZaLSM18=; b=wVTGjGN7SSpL45 d0y2lpgrB9yc4ABoCIX4uPHsXP5u0tsE4340PLvZN7dtABsevwHDwsb9xrtbiLTq7hF38xhCE/yWo gMFAVJ4iw7C0OsIRN4TYGSYdYV/YijhVFp2xvDePM/8U4dvB89vJp7TlXbqYHKkvjIbm0JIXSXNts 7mVDOaJ5kvCcim7MrK2ZrpkO18RLe244EkATxN7UMoMP3GBfnJANKjEpzMYJ/Cl0jFs8sBsBYrn8y 6C6JVNSEljueiiDxcrt3kWkbOSp1TkB3HCUeM+kSaP95moRb9FhSFPYvSU+3izfP97Y3akvxIgXUU Yszy5fglBYVvKYuS0cBQ==; Received: from localhost ([::1] helo=bombadil.infradead.org) by bombadil.infradead.org with esmtp (Exim 4.97.1 #2 (Red Hat Linux)) id 1rZoam-00000008Vym-1HOb; Tue, 13 Feb 2024 08:56:40 +0000 Received: from mail5.25mail.st ([74.50.62.9]) by bombadil.infradead.org with esmtps (Exim 4.97.1 #2 (Red Hat Linux)) id 1rZoai-00000008VyG-3klj for linux-arm-kernel@lists.infradead.org; Tue, 13 Feb 2024 08:56:38 +0000 Received: from localhost (91-158-86-216.elisa-laajakaista.fi [91.158.86.216]) by mail5.25mail.st (Postfix) with ESMTPSA id 58E6460505; Tue, 13 Feb 2024 08:56:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=atomide.com; s=25mailst; t=1707814594; bh=TakGXTNQRkMesSg/PE7LknQ/w52dBfFxSThPEQtqpMA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=txFjgBz+ooekDORkXwPGPXsIBcfGMK6WAYu9qDKUzYqsf3Bik9UggUyQDoyZFNJro J2MqFZ91fnGD55iABTa41PpaQYW8tianqk8rg+3heNWTEMKp9Dpft+mbxno6ndnbVj WgcFEseKO/q1cGqCsU8AFWjmUllRr/lVtwuxzUPDcfGMUqo7pLoxNk2lyIwsxOuTac O4zsAUFLymEbYiHrza/3hRJ1Hmu/wyl7mK5XLb9euWcv1NBokEPhEVBmTdkip/FCWv fn0lyz9uYc8AiTHHYnUpklrLN4XWLzyeOSuTdJQDRxVdi8W6+ESbBdyAN66OA6wLgF AnMiRDPS7wpkQ== Date: Tue, 13 Feb 2024 10:56:19 +0200 From: Tony Lindgren To: "Raghavendra, Vignesh" , Markus Schneider-Pargmann Cc: Nishanth Menon , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Dhruva Gole Subject: Re: [PATCH] arm64: dts: ti: k3-am62-wakeup: Configure ti-sysc for wkup_uart0 Message-ID: <20240213085619.GF52537@atomide.com> References: <20230912111215.18415-1-tony@atomide.com> <170368552643.1332094.7883858507182654481.b4-ty@ti.com> MIME-Version: 1.0 Content-Disposition: inline In-Reply-To: X-CRM114-Version: 20100106-BlameMichelson ( TRE 0.8.0 (BSD) ) MR-646709E3 X-CRM114-CacheID: sfid-20240213_005637_013702_FCBA28C9 X-CRM114-Status: GOOD ( 15.88 ) 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: , Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "linux-arm-kernel" Errors-To: linux-arm-kernel-bounces+linux-arm-kernel=archiver.kernel.org@lists.infradead.org * Raghavendra, Vignesh [231227 15:22]: > > > On 12/27/2023 7:29 PM, Vignesh Raghavendra wrote: > > > > On Tue, 12 Sep 2023 14:12:15 +0300, Tony Lindgren wrote: > >> The devices in the wkup domain are capable of waking up the system from > >> suspend. We can configure the wkup domain devices in a generic way using > >> the ti-sysc interconnect target module driver like we have done with the > >> earlier TI SoCs. > >> > >> As ti-sysc manages the SYSCONFIG related registers independent of the > >> child hardware device, the wake-up configuration is also set even if > >> wkup_uart0 is reserved by sysfw. > >> > >> [...] > > > > Applied, thanks! > > > > [1/1] arm64: dts: ti: k3-am62-wakeup: Configure ti-sysc for wkup_uart0 > > commit: 86224524b52a8efba26f920736d08c8bfdd22d87 > > > > > Please ignore above. I meant to pick v4. Sorry for the noise! So we need to add ti,no-reset-on-init as noted by Markus. As I'm not seeing this in Linux next, I'll send out v5 patch. If you need an incremental fix I can do that too naturally. Regards, Tony _______________________________________________ linux-arm-kernel mailing list linux-arm-kernel@lists.infradead.org http://lists.infradead.org/mailman/listinfo/linux-arm-kernel From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from mail5.25mail.st (mail5.25mail.st [74.50.62.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id E1A43175AC for ; Tue, 13 Feb 2024 08:56:34 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=74.50.62.9 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707814596; cv=none; b=Fe1ZQ2UIROAuBuinzlZiYzNYAEpfDfzr+lHxzCILN9pOPxuKhs0IvMlJGyf0fYQXAsa58FJJZcUhNM6g1GBKaI5HBfQSh1/SSm/Um9Iviynb4/03p5LcOtH59Q3xPMXE063FXLZOfoV24+qz3kHRPlgGUw3e8zLpQ45ndlU8gMs= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1707814596; c=relaxed/simple; bh=TakGXTNQRkMesSg/PE7LknQ/w52dBfFxSThPEQtqpMA=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=flnUI0MhzLxpKSTGlbTr+LzbTIPOEjtu0zPPimfhxx3Kas2DxFfaiIQnkmiWkrih2TkWXKQGzvXauw817nyrxnadVZIcj6fI8G9RCmR3Xwr6+muf7jEtqqWP9ivk8aS966AzxaRmdQhzKBR8cA8y+CfIvsJmts5ZC/zN5hepn5w= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=atomide.com; spf=fail smtp.mailfrom=atomide.com; dkim=pass (2048-bit key) header.d=atomide.com header.i=@atomide.com header.b=txFjgBz+; arc=none smtp.client-ip=74.50.62.9 Authentication-Results: smtp.subspace.kernel.org; dmarc=none (p=none dis=none) header.from=atomide.com Authentication-Results: smtp.subspace.kernel.org; spf=fail smtp.mailfrom=atomide.com Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=atomide.com header.i=@atomide.com header.b="txFjgBz+" Received: from localhost (91-158-86-216.elisa-laajakaista.fi [91.158.86.216]) by mail5.25mail.st (Postfix) with ESMTPSA id 58E6460505; Tue, 13 Feb 2024 08:56:21 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=atomide.com; s=25mailst; t=1707814594; bh=TakGXTNQRkMesSg/PE7LknQ/w52dBfFxSThPEQtqpMA=; h=Date:From:To:Cc:Subject:References:In-Reply-To:From; b=txFjgBz+ooekDORkXwPGPXsIBcfGMK6WAYu9qDKUzYqsf3Bik9UggUyQDoyZFNJro J2MqFZ91fnGD55iABTa41PpaQYW8tianqk8rg+3heNWTEMKp9Dpft+mbxno6ndnbVj WgcFEseKO/q1cGqCsU8AFWjmUllRr/lVtwuxzUPDcfGMUqo7pLoxNk2lyIwsxOuTac O4zsAUFLymEbYiHrza/3hRJ1Hmu/wyl7mK5XLb9euWcv1NBokEPhEVBmTdkip/FCWv fn0lyz9uYc8AiTHHYnUpklrLN4XWLzyeOSuTdJQDRxVdi8W6+ESbBdyAN66OA6wLgF AnMiRDPS7wpkQ== Date: Tue, 13 Feb 2024 10:56:19 +0200 From: Tony Lindgren To: "Raghavendra, Vignesh" , Markus Schneider-Pargmann Cc: Nishanth Menon , devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, Dhruva Gole Subject: Re: [PATCH] arm64: dts: ti: k3-am62-wakeup: Configure ti-sysc for wkup_uart0 Message-ID: <20240213085619.GF52537@atomide.com> References: <20230912111215.18415-1-tony@atomide.com> <170368552643.1332094.7883858507182654481.b4-ty@ti.com> Precedence: bulk X-Mailing-List: devicetree@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: * Raghavendra, Vignesh [231227 15:22]: > > > On 12/27/2023 7:29 PM, Vignesh Raghavendra wrote: > > > > On Tue, 12 Sep 2023 14:12:15 +0300, Tony Lindgren wrote: > >> The devices in the wkup domain are capable of waking up the system from > >> suspend. We can configure the wkup domain devices in a generic way using > >> the ti-sysc interconnect target module driver like we have done with the > >> earlier TI SoCs. > >> > >> As ti-sysc manages the SYSCONFIG related registers independent of the > >> child hardware device, the wake-up configuration is also set even if > >> wkup_uart0 is reserved by sysfw. > >> > >> [...] > > > > Applied, thanks! > > > > [1/1] arm64: dts: ti: k3-am62-wakeup: Configure ti-sysc for wkup_uart0 > > commit: 86224524b52a8efba26f920736d08c8bfdd22d87 > > > > > Please ignore above. I meant to pick v4. Sorry for the noise! So we need to add ti,no-reset-on-init as noted by Markus. As I'm not seeing this in Linux next, I'll send out v5 patch. If you need an incremental fix I can do that too naturally. Regards, Tony