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 603FAC43334 for ; Wed, 22 Jun 2022 14:20:14 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1358202AbiFVOUN (ORCPT ); Wed, 22 Jun 2022 10:20:13 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:44782 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1358175AbiFVOUL (ORCPT ); Wed, 22 Jun 2022 10:20:11 -0400 Received: from mga07.intel.com (mga07.intel.com [134.134.136.100]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id D009B5FB6; Wed, 22 Jun 2022 07:20:10 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=intel.com; i=@intel.com; q=dns/txt; s=Intel; t=1655907610; x=1687443610; h=date:from:to:cc:subject:message-id:references: mime-version:in-reply-to; bh=FXE8o8UOWuK9nf2Bhh8e/wPro8z+x8Ye/C+F7s9tcSA=; b=mBVZF5WJ8pfZYE1mUUrE6BpQ0086cxrsoLEVMR9k2evSljpavn7REb5T z1v+Jnd0Go3z8sKSdW9YdrejUXclshYZMRuzZO5LuZPOO/L9urYVi7LZc wox3Joq+3VAuvCvQ5EM5wCvYd1tXofNH8UEO426s6g204RHxrG6pqJHRr nVHsDAaEuOywVTFTPnAv/d1D2/CcDxDgEMy87xEp3EXIGh3TPikFGM5Cu BaFI7LC+Hdn+l/4ixreldOJKO9VC5veYxjY2Hu/CvWBwRpZQ3rp8nTeZZ FF4d5GZWHvAMXXbqKmiLHBRoD+FgvtLf4bLDtFX7MUIzqvE3fPQoaLl2c w==; X-IronPort-AV: E=McAfee;i="6400,9594,10385"; a="344418822" X-IronPort-AV: E=Sophos;i="5.92,212,1650956400"; d="scan'208";a="344418822" Received: from fmsmga001.fm.intel.com ([10.253.24.23]) by orsmga105.jf.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Jun 2022 07:20:10 -0700 X-IronPort-AV: E=Sophos;i="5.92,212,1650956400"; d="scan'208";a="730366946" Received: from smile.fi.intel.com ([10.237.72.54]) by fmsmga001-auth.fm.intel.com with ESMTP/TLS/ECDHE-RSA-AES256-GCM-SHA384; 22 Jun 2022 07:20:05 -0700 Received: from andy by smile.fi.intel.com with local (Exim 4.95) (envelope-from ) id 1o41D7-000sN3-B2; Wed, 22 Jun 2022 17:20:01 +0300 Date: Wed, 22 Jun 2022 17:20:01 +0300 From: Andy Shevchenko To: Andrew Lunn 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: Organization: Intel Finland Oy - BIC 0357606-4 - Westendinkatu 7, 02160 Espoo Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Wed, Jun 22, 2022 at 01:22:15PM +0200, Andrew Lunn wrote: > > > 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. I also can review it. Marcin, would it be hard for you to prepare a formal proposal for ACPI specification? -- With Best Regards, Andy Shevchenko