Received: by 2002:a05:6a10:7420:0:0:0:0 with SMTP id hk32csp972826pxb; Wed, 16 Feb 2022 08:13:07 -0800 (PST) X-Google-Smtp-Source: ABdhPJxCM3pI8fmnUN0Usyt5C8yd4E8tuYnFAqCwdbS2SCUTD5oiNG6l3NwRJ6jiSGRCtRsIncjg X-Received: by 2002:a05:6808:168e:b0:2d3:a93f:317e with SMTP id bb14-20020a056808168e00b002d3a93f317emr1046119oib.57.1645027986518; Wed, 16 Feb 2022 08:13:06 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1645027986; cv=none; d=google.com; s=arc-20160816; b=U72LSkzG7sVxKOq4ushBrGmISpYmQmg8L0l7sWzgVGMORqO2870HdhrqvRVfWuRo8C +x1m41wPDM7zGMhYURe2NJXvFmMFu2rUwnufTwXrUTUQyXpk6ELfV9OeyAiwKYZjJxSM HvruMa0A2ZCLWldwdujBDfnNeYdCqAsTZt/JFLXAh5vwfA0OEIF2sUQzx0xwzZSuRPBp 1OjLnd4wSPC03yICUOsbJ2eRetTM4xi8WO2GYUctNdOR6ExwgjvPg/GqsJPtMAdECXnU D+hn7GMBo2zBS50WODUQerJ4AQaAXL4qWCVLQjYGpeYRqOfUZ5TtTC8aIgH3uRSJG8tt qSTg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:content-transfer-encoding:mime-version :message-id:date:subject:cc:to:from:dkim-signature; bh=cVf2ord3tIBpCLVkNiS9lYcPjPngvv8JI3RlnFJb+Go=; b=ir2fMk5Y0Q8nME3IjX8ZAfCIIWtOla1ahJcbucN6peaghGUFmB6mSf1bvEXHfJwnn+ /ED/82NVtrfK4quvvqFY0oc9fObZg6dcJbop+a3OjaZdS6MMsiX1Gc+HOjCrWiDpQn/M MjaYjkuItknkcJuwbBNxB69kPeX5It3Sn87JWLs11n4Eyx4Svz/IiCzrS/Tw5ndqSL73 H4KQgnCu2HfOt/oKm9ww+x45bZQv/hP7idA+qlzkXG58sbB05bsBmlVl2YWtAsJDi/6i FVk9aXuywA/sELtZLYiVRsbWHQZj7aX7rQx1cp0pC9T1+1ALAe4f1wtyeBTEupMAPMM8 YZWQ== ARC-Authentication-Results: i=1; mx.google.com; dkim=temperror (no key for signature) header.i=@pqrs.dk header.s=google header.b=PE6RmbQH; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id q8si1693673oag.386.2022.02.16.08.12.41; Wed, 16 Feb 2022 08:13:06 -0800 (PST) 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; Authentication-Results: mx.google.com; dkim=temperror (no key for signature) header.i=@pqrs.dk header.s=google header.b=PE6RmbQH; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235905AbiBPQDp (ORCPT + 99 others); Wed, 16 Feb 2022 11:03:45 -0500 Received: from mxb-00190b01.gslb.pphosted.com ([23.128.96.19]:49424 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S233934AbiBPQDp (ORCPT ); Wed, 16 Feb 2022 11:03:45 -0500 Received: from mail-ed1-x52f.google.com (mail-ed1-x52f.google.com [IPv6:2a00:1450:4864:20::52f]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id 6A6D82A82F1 for ; Wed, 16 Feb 2022 08:03:31 -0800 (PST) Received: by mail-ed1-x52f.google.com with SMTP id z22so4724878edd.1 for ; Wed, 16 Feb 2022 08:03:31 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=pqrs.dk; s=google; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=cVf2ord3tIBpCLVkNiS9lYcPjPngvv8JI3RlnFJb+Go=; b=PE6RmbQHihPPqU838vHjMI2B6KANIAA60vsGXlioK2c14r9HRRCnAyIAFtZcPc5M5v vHklsRGq8sBkmbnEEhewG5I4T5L58MIRA4wMr1VL0mB9B7b3IqCgZnjscGjYiy7Uyq1r sXWDpeBxgy1QWWO5+N4JWEMAXvchDPUmLepsE= X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=cVf2ord3tIBpCLVkNiS9lYcPjPngvv8JI3RlnFJb+Go=; b=b/ckmU5Sg+NXgqHW3wANDYZI5jP16eg9ipbxfp5POc4pKnWvqACU3oJHI0D2AodHL4 OaIfmlxawtGBL3nYl8CrKEAZ7TS9eAllwszz68nPr0rU6vBXmNCdKmefd3XU+FlfiWaz Uief9x2Z2VMolRi3s8Dst1rR1hV4QIrTvafFtdna24segZ07w8Uy+BNciO6VxgwEnn9y iLxqqqCgmWy4GHlN0ZdWjoYZAu+rmh6QB3WHA+3M7IPSi8utqETP/a10vIHcwUsQSpN3 0ifkzKpt8a+I+T6zYQNNBs/svvB0cPFJwlyg5xmnWEB3iUcUTdRHe+U6hg2wubygGVlp pdEw== X-Gm-Message-State: AOAM532pHPHQigmfT7wYZdCseXV7MGVDkkzZKifhh8D3qYvT1RikAdqC IWaIZwhM++eEgfHoe+O/jH8EFg== X-Received: by 2002:aa7:cac8:0:b0:410:cc6c:6512 with SMTP id l8-20020aa7cac8000000b00410cc6c6512mr3722719edt.408.1645027410012; Wed, 16 Feb 2022 08:03:30 -0800 (PST) Received: from capella.. ([193.89.194.60]) by smtp.gmail.com with ESMTPSA id j19sm48365ejm.111.2022.02.16.08.03.26 (version=TLS1_3 cipher=TLS_AES_256_GCM_SHA384 bits=256/256); Wed, 16 Feb 2022 08:03:28 -0800 (PST) From: =?UTF-8?q?Alvin=20=C5=A0ipraga?= To: Linus Walleij , Andrew Lunn , Vivien Didelot , Florian Fainelli , Vladimir Oltean , "David S. Miller" , Jakub Kicinski , Michael Rasmussen , =?UTF-8?q?Alvin=20=C5=A0ipraga?= Cc: Luiz Angelo Daros de Luca , =?UTF-8?q?Ar=C4=B1n=C3=A7=20=C3=9CNAL?= , netdev@vger.kernel.org, linux-kernel@vger.kernel.org Subject: [PATCH net-next 0/2] net: dsa: realtek: fix PHY register read corruption Date: Wed, 16 Feb 2022 17:04:58 +0100 Message-Id: <20220216160500.2341255-1-alvin@pqrs.dk> X-Mailer: git-send-email 2.35.0 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Spam-Status: No, score=-1.7 required=5.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,RCVD_IN_DNSWL_NONE,SPF_HELO_NONE,SPF_NONE, T_SCC_BODY_TEXT_LINE autolearn=no autolearn_force=no version=3.4.6 X-Spam-Checker-Version: SpamAssassin 3.4.6 (2021-04-09) on lindbergh.monkeyblade.net Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Alvin Šipraga These two patches fix the issue reported by Arınç where PHY register reads sometimes return garbage data. MAINTAINERS: Please can you help me with the targetting of these two patches? This bug is present ca. 5.16, when the SMI version of the rtl8365mb driver was introduced. But now in net-next we have the MDIO interface from Luiz, where the issue is also present. I am sending what I think is an ideal patch series, but should I split it up and send the SMI-related changes to net and the MDIO changes to net-next? If so, how would I go about splitting it while preventing merge conflicts and build errors? For now I am sending it to net-next so that the whole thing can be reviewed. If it's applied, I would gladly backport the fix to the stable tree for 5.16, but I am still confused about what to do for 5.17. Thanks for your help. Alvin Šipraga (2): net: dsa: realtek: allow subdrivers to externally lock regmap net: dsa: realtek: rtl8365mb: serialize indirect PHY register access drivers/net/dsa/realtek/realtek-mdio.c | 46 +++++++++++++++++++++- drivers/net/dsa/realtek/realtek-smi.c | 48 +++++++++++++++++++++-- drivers/net/dsa/realtek/realtek.h | 2 + drivers/net/dsa/realtek/rtl8365mb.c | 54 ++++++++++++++++---------- 4 files changed, 124 insertions(+), 26 deletions(-) -- 2.35.0