From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
Received: from vger.kernel.org (vger.kernel.org [23.128.96.18])
	by smtp.lore.kernel.org (Postfix) with ESMTP id 62A99C7EE23
	for <linux-kernel@archiver.kernel.org>; Mon,  5 Jun 2023 15:40:35 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S234936AbjFEPkd (ORCPT <rfc822;linux-kernel@archiver.kernel.org>);
        Mon, 5 Jun 2023 11:40:33 -0400
Received: from lindbergh.monkeyblade.net ([23.128.96.19]:43526 "EHLO
        lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S233890AbjFEPkW (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Mon, 5 Jun 2023 11:40:22 -0400
Received: from madras.collabora.co.uk (madras.collabora.co.uk [IPv6:2a00:1098:0:82:1000:25:2eeb:e5ab])
        by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 968F9130;
        Mon,  5 Jun 2023 08:40:13 -0700 (PDT)
Received: from arisu.mtl.collabora.ca (mtl.collabora.ca [66.171.169.34])
        (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
         key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256)
        (No client certificate requested)
        (Authenticated sender: detlev)
        by madras.collabora.co.uk (Postfix) with ESMTPSA id AA0EE660036A;
        Mon,  5 Jun 2023 16:40:10 +0100 (BST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=collabora.com;
        s=mail; t=1685979612;
        bh=GZl6ZhnAnG6jIOD1vjYTq8i9dEDF+bhtGx3LOe6W+Ig=;
        h=From:To:Cc:Subject:Date:From;
        b=OP6jCf1A4MiKSEjBCv4IlmWs4/fnvnKlEkWD25RfUnm/z9zLKiX6tNXclcoXhI3iE
         tDLBCCd5Q3EtlLWz40vBpznWg4QDsYmqblZxAbNnt7pUI/Ayd1q7gEYo+e96X1OMyH
         YsnGE3TRRxevmjIwvXcP764f/faXLUov1z4EmSitCGW6GVOlgFcsufB2U8sxCGcZF5
         dVfOYix7Va4lCkbobfXeg9CDg9zVIW81wS/cGJ3J7B1XRe+k4088Hke7PZczpJdQeW
         oElIltkn0u5ZxVN0p3QzjVfhP9kKwMt9w7SsPxN1VAnNGJG0vVy/uezDgwvTsBkqKT
         KEDWRdKeu36Gg==
From:   Detlev Casanova <detlev.casanova@collabora.com>
To:     linux-kernel@vger.kernel.org
Cc:     Andrew Lunn <andrew@lunn.ch>,
        Heiner Kallweit <hkallweit1@gmail.com>,
        Russell King <linux@armlinux.org.uk>,
        "David S . Miller" <davem@davemloft.net>,
        Eric Dumazet <edumazet@google.com>,
        Jakub Kicinski <kuba@kernel.org>,
        Paolo Abeni <pabeni@redhat.com>,
        Rob Herring <robh+dt@kernel.org>,
        Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
        Conor Dooley <conor+dt@kernel.org>,
        Florian Fainelli <f.fainelli@gmail.com>,
        netdev@vger.kernel.org, devicetree@vger.kernel.org
Subject: [PATCH v4 0/3] net: phy: realtek: Support external PHY clock
Date:   Mon,  5 Jun 2023 11:40:07 -0400
Message-Id: <20230605154010.49611-1-detlev.casanova@collabora.com>
X-Mailer: git-send-email 2.39.3
MIME-Version: 1.0
Content-Transfer-Encoding: 8bit
Precedence: bulk
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Some PHYs can use an external clock that must be enabled before
communicating with them.

Changes since v3:
 * Do not call genphy_suspend if WoL is enabled.
Changes since v2:
 * Reword documentation commit message
Changes since v1:
 * Remove the clock name as it is not guaranteed to be identical across
   different PHYs
 * Disable/Enable the clock when suspending/resuming