Received: by 2002:a05:6358:16cc:b0:ea:6187:17c9 with SMTP id r12csp6222943rwl; Mon, 9 Jan 2023 05:54:20 -0800 (PST) X-Google-Smtp-Source: AMrXdXvwcplKHslS/f24OEjGSmF10Z7/kCDdtu0c6jFkSwYGhhQs7h/Eo87RPysPH5q6rfjJY1eN X-Received: by 2002:a17:90a:f309:b0:225:c112:c871 with SMTP id ca9-20020a17090af30900b00225c112c871mr64580296pjb.12.1673272460060; Mon, 09 Jan 2023 05:54:20 -0800 (PST) ARC-Seal: i=1; a=rsa-sha256; t=1673272460; cv=none; d=google.com; s=arc-20160816; b=EZf+PIGkgdRAQUXqCj3MsNZVYVRilvyRHpoI4JiISrCNoK7TAMmhK6Ha2bhDOMEmUj N1A2u0+vcPxOwqjNTtkm4Os6wiqRRNg8D1zQaCQaVcosTjyBXYO1wN2OJ0Tvbw/mibWx vHNH4aBTo9bLTmDnIDxwQR4rhJX8sX8pJzeoTLjLNKSkekuRTp8qkk1RtcDRC3Emghpc FYpRpS1yQaXWvUZMPgc34u7jRPzO0UHf1v7lUVXXR3jQ9XIRGydiXRfxWqXdi/IHmtBc 4fVHYlE08w2lFbRHJeHSPBrIsHinva0duUJmRu9Xtr2gH0Oo6yqnJzrBMyvAeWogxTWn 60/Q== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:in-reply-to:content-disposition:mime-version :references:message-id:subject:cc:to:from:date:dkim-signature; bh=qK6lV7QSTv9+pKbnrqwgqCq711Cf+sulr6SnpBvZui8=; b=HUXCO/+o9DXp6SoWCFqE1JB/wMwIVL5wxy+sqU6GPvGF+vfk6jZfujeLvMiNfQ4W3C XKx6jBk/Q2INWXCwcLjigu2AkIRX3m1iuF7Hs1SJ+Zz/qj4AnW7pWmOF+ZEART6UkUYv VdCdoNjnkIaOfPbySnCnk89rPXYQlc5pR2UVDbjOyHvjGErxBeYSQxrlgL7WFsfLTvkg 5WE+LwxN2JbiWRTQWKH2Yer4v4NJb/KlXN1T7ZZrwAAv8/kLI1PQxyWQluUNuNQeAh3+ znH3wRTLHsof4A4uqB6nmIRQRFUArje66Ua6QffgaB/uq9RfAfWWFhf3ieiEta0Kg72Z ysNw== ARC-Authentication-Results: i=1; mx.google.com; dkim=pass header.i=@lunn.ch header.s=20171124 header.b=Zx8K6ZeH; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=lunn.ch Return-Path: Received: from out1.vger.email (out1.vger.email. [2620:137:e000::1:20]) by mx.google.com with ESMTP id me18-20020a17090b17d200b00212deed484esi10146353pjb.132.2023.01.09.05.54.13; Mon, 09 Jan 2023 05:54:20 -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=pass header.i=@lunn.ch header.s=20171124 header.b=Zx8K6ZeH; 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; dmarc=pass (p=NONE sp=NONE dis=NONE) header.from=lunn.ch Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S237236AbjAINli (ORCPT + 54 others); Mon, 9 Jan 2023 08:41:38 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:53086 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S236276AbjAINlD (ORCPT ); Mon, 9 Jan 2023 08:41:03 -0500 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E88E93B91D; Mon, 9 Jan 2023 05:40:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=qK6lV7QSTv9+pKbnrqwgqCq711Cf+sulr6SnpBvZui8=; b=Zx8K6ZeHDbrkxr9ADUvZf+K0M4 GHLjqH5GaZW/Cnd3V6ObqhzDQ40z2BrJ3Rx7fGDAcq4oVBzAAq2IddwHX+7W4WX1MVg2/uxud6Jzg xMYB7gt8Tm0/7zeFvvJB1PEGVAWos7RQYvgzYaaIE+3xlEF96dJxYhGTYSNp5h78YmhI=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1pEsNm-001ZTL-Jf; Mon, 09 Jan 2023 14:40:10 +0100 Date: Mon, 9 Jan 2023 14:40:10 +0100 From: Andrew Lunn To: Michael Walle Cc: "David S . Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Rob Herring , Krzysztof Kozlowski , Xu Liang , Heiner Kallweit , Russell King , netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH net-next v3 3/4] net: phy: allow a phy to opt-out of interrupt handling Message-ID: References: <20230109123013.3094144-1-michael@walle.cc> <20230109123013.3094144-4-michael@walle.cc> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20230109123013.3094144-4-michael@walle.cc> X-Spam-Status: No, score=-2.1 required=5.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,SPF_HELO_PASS,SPF_PASS autolearn=ham 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 On Mon, Jan 09, 2023 at 01:30:12PM +0100, Michael Walle wrote: > Until now, it is not possible for a PHY driver to disable interrupts > during runtime. If a driver offers the .config_intr() as well as the > .handle_interrupt() ops, it is eligible for interrupt handling. > Introduce a new flag for the dev_flags property of struct phy_device, which > can be set by PHY driver to skip interrupt setup and fall back to polling > mode. > > At the moment, this is used for the MaxLinear PHY which has broken > interrupt handling and there is a need to disable interrupts in some > cases. > > Signed-off-by: Michael Walle Reviewed-by: Andrew Lunn Andrew