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 vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 8FE61C433EF for ; Wed, 22 Jun 2022 11:23:17 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1357331AbiFVLXQ (ORCPT ); Wed, 22 Jun 2022 07:23:16 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:37508 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1357605AbiFVLW6 (ORCPT ); Wed, 22 Jun 2022 07:22:58 -0400 Received: from vps0.lunn.ch (vps0.lunn.ch [185.16.172.187]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id CC76D3A71C; Wed, 22 Jun 2022 04:22:21 -0700 (PDT) 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=I+IQpUdGRvzryPiMbgvBe30v5I8PKYgMnD6LyAtMq9s=; b=j1+GJak+LXgezTk5y6Op6Hz8Oc gCjGb6oeibd7Z+rMixmSzNt+EVlBH77RTjCj8p6uUUtjWrJ1ZN7JGNfgu+Jc/YW5zlQ0B+38D14JJ xnEUEQZ1SVVSqO38mOwulyJmIKpmB5vluJ/Gr5J6Cwj1Gx33tIgT4/BMrt1jyPeRl+CU=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1o3yR5-007qRc-VN; Wed, 22 Jun 2022 13:22:15 +0200 Date: Wed, 22 Jun 2022 13:22:15 +0200 From: Andrew Lunn To: Andy Shevchenko Cc: Marcin Wojtas , Linux Kernel Mailing List , ACPI Devel Maling List , netdev , "Rafael J. Wysocki" , Len Brown , vivien.didelot@gmail.com, Florian Fainelli , Vladimir Oltean , "David S. Miller" , Eric Dumazet , Jakub Kicinski , pabeni@redhat.com, Russell King - ARM Linux , Heiner Kallweit , Grzegorz Bernacki , Grzegorz Jaszczyk , Tomasz Nowicki , Samer El-Haj-Mahmoud , upstream@semihalf.com Subject: Re: [net-next: PATCH 09/12] Documentation: ACPI: DSD: introduce DSA description Message-ID: References: <20220620150225.1307946-1-mw@semihalf.com> <20220620150225.1307946-10-mw@semihalf.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org > > It's not device on MDIO bus, but the MDIO controller's register itself > > (this _CSR belongs to the parent, subnodes do not refer to it in any > > way). The child device requires only _ADR (or whatever else is needed > > for the case the DSA device is attached to SPI/I2C controllers). > > More and more the idea of standardizing the MDIOSerialBus() resource looks > plausible. The _ADR() usage is a bit grey area in ACPI specification. Maybe > someone can also make it descriptive, so Microsoft and others won't utilize > _ADR() in any level of weirdness. I don't know if it makes any difference, but there are two protocols spoken over MDIO, c22 and c45, specified in clause 22 and clause 45 of the 802.3 specification. In some conditions, you need to specify which protocol to speak to a device at a particular address. In DT we indicate this with the compatible string, when maybe it should really be considered as an extension of the address. If somebody does produce a draft for MDIOSerialBus() i'm happy to review it. Andrew