From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from smtp.kernel.org (aws-us-west-2-korg-mail-1.web.codeaurora.org [10.30.226.201]) (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 DED8334B68C for ; Tue, 23 Dec 2025 17:45:06 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=10.30.226.201 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766511908; cv=none; b=O+c0P9pxeKfC+HJWeQ6Yo2pxTUFfzIATh3U6ahEb4SEgxAYSvFprAazdkMpUGMUYPvWTOMTr2pjZQITboj3kBQNgx3TkhiLBnd9adIdP3rbQczqW25P637KM5/7tdWK/45rXzA4Wq76K+UYgkbiZ7xs5c26H4OPQvIZmJBL2VDE= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1766511908; c=relaxed/simple; bh=DBvS/TnM8rlvgOk+j5YopCLdGl98ROmovzKsRKXjxxw=; h=From:To:Cc:In-Reply-To:References:Subject:Message-Id:Date: MIME-Version:Content-Type; b=cpHiKGbVGI5bNoCy8mJFZJ2BOLTqTALJSWC1bnB1tu91EXHxoOfQo851hlm/V6W6kO9JnyOSR1R+4CqguGKiYoghmgs/zX/XpK96ZG9bHCv16xE+X7M8O07O2zROoPF8L56LNz7Y/8b64tr+mq9Q0f3kQnSVSJ+LVWFAKE6USII= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b=BVmPK5fd; arc=none smtp.client-ip=10.30.226.201 Authentication-Results: smtp.subspace.kernel.org; dkim=pass (2048-bit key) header.d=kernel.org header.i=@kernel.org header.b="BVmPK5fd" Received: by smtp.kernel.org (Postfix) with ESMTPSA id B1C89C113D0; Tue, 23 Dec 2025 17:45:03 +0000 (UTC) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org; s=k20201202; t=1766511906; bh=DBvS/TnM8rlvgOk+j5YopCLdGl98ROmovzKsRKXjxxw=; h=From:To:Cc:In-Reply-To:References:Subject:Date:From; b=BVmPK5fdWVg5zT7kek6b2sX/5PMca/nsBRoqQV1Ktl/HfHNuGwk0QL+oaRH7bwqPL QBd2PLLuXh0QKxcbLgCGHgYt6X5A8dxgB6TFuWq3aXORHYuec7KgtbOJc2AizqoKVj /ZIPzyjTFoSB2yoWQTaKBJKKkk1ujQRCEmKhaNzmlu0wVCa7lKUrY3LDSOOWQQ5fp5 3X/7lFWlxfx+f/o+HtPut4S3uo9YxnWAUUnUgk1Uq0k5OnbMBEbCJjXyVOze5OhjJx 2FfTcMCC91dvBLBc8cZDvSuoKK/vQ8qUqwHkfa14St4Fc/XTWobn2mOwEIQn7EBjU0 WbJqj4230ErWg== From: Vinod Koul To: Kishon Vijay Abraham I , "Thomas Richard (TI.com)" Cc: Thomas Petazzoni , Gregory CLEMENT , Udit Kumar , Prasanth Mantena , Abhash Kumar , linux-phy@lists.infradead.org, linux-kernel@vger.kernel.org, Neil Armstrong In-Reply-To: <20251216-phy-cadence-torrent-resume-restore-refclk-parent-v3-1-8a7ed84b47e3@bootlin.com> References: <20251216-phy-cadence-torrent-resume-restore-refclk-parent-v3-1-8a7ed84b47e3@bootlin.com> Subject: Re: [PATCH v3] phy: cadence-torrent: restore parent clock for refclk during resume Message-Id: <176651190335.759340.106751944361885303.b4-ty@kernel.org> Date: Tue, 23 Dec 2025 23:15:03 +0530 Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: 7bit X-Mailer: b4 0.13.0 On Tue, 16 Dec 2025 15:24:25 +0100, Thomas Richard (TI.com) wrote: > While suspend and resume, parent clock config for refclk was getting lost. > So save and restore it in suspend and resume operations. > > Applied, thanks! [1/1] phy: cadence-torrent: restore parent clock for refclk during resume commit: 434e1a0ee145d0389b192252be4c993f86cf1134 Best regards, -- ~Vinod