From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from vps0.lunn.ch (vps0.lunn.ch [156.67.10.101]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by smtp.subspace.kernel.org (Postfix) with ESMTPS id C84B38F72; Thu, 28 Mar 2024 12:32:19 +0000 (UTC) Authentication-Results: smtp.subspace.kernel.org; arc=none smtp.client-ip=156.67.10.101 ARC-Seal:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1711629141; cv=none; b=Rk2CEuo1x5Ssv6Vk+2+C66NHbRBGLVv1K5F/SzAmiImmQPV7qCvUZivxkloRhBERgMYzUjAoC22XR5xnAytIR5HXr/ZMFliL8j5tAckoo0BKBFls/3ZJ15wXpVHL9siRXP+EJv96tRmx9pFiSXggoHIZi7NSldmyq9jarE11h74= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1711629141; c=relaxed/simple; bh=h3qsImq/RyQ/HpoR7a4GRGMkNu968dAdOACxo5Fz8kQ=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=CJLI3Dv2/CSLzhhSG/4Ti3y706R5py+dw3g1y0mmy2kRVjgzA9Sg2IPSUxvJSB0rUappl7Z1Ak8Sw4Yfczev8Lajy0Oh5hfZiozdxqHq8nNHTlnKZCM1DJ2rbK3fMthlFZQsjPpQdTCJNtNkC/5Xu0A934qVQ91kp7QpNXyzCBM= ARC-Authentication-Results:i=1; smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch; spf=pass smtp.mailfrom=lunn.ch; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b=zg0hIRXJ; arc=none smtp.client-ip=156.67.10.101 Authentication-Results: smtp.subspace.kernel.org; dmarc=pass (p=none dis=none) header.from=lunn.ch Authentication-Results: smtp.subspace.kernel.org; spf=pass smtp.mailfrom=lunn.ch Authentication-Results: smtp.subspace.kernel.org; dkim=pass (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b="zg0hIRXJ" 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=00mLxt6VUg7/Q0nlQk3tLro0aY2aIMV8pnt3fdjOkbw=; b=zg0hIRXJWJgd5O4iVzZhz6lsa5 8FZz0So/Kac9eFAN2Hw082FsCIB21nTcpks+hGRXqpLzQXbCf2Uvjyi3u78ozt7DS0egNTHPXVpTB TcQIr9+jzlAwnOKuv+2B2N12VJd6miojib+johTWNzWgTLKjaAfWRUmrw2xHMwhBYS3k=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1rpovR-00BUoL-12; Thu, 28 Mar 2024 13:32:09 +0100 Date: Thu, 28 Mar 2024 13:32:09 +0100 From: Andrew Lunn To: Rob Herring Cc: Kory Maincent , devicetree@vger.kernel.org, Thomas Petazzoni , Dent Project , "Rafael J. Wysocki" , Jonathan Corbet , Rob Herring , Russell King , Conor Dooley , Jakub Kicinski , Frank Rowand , Krzysztof Kozlowski , Heiner Kallweit , Russ Weight , "David S. Miller" , Greg Kroah-Hartman , Oleksij Rempel , Paolo Abeni , Mark Brown , netdev@vger.kernel.org, linux-doc@vger.kernel.org, Eric Dumazet , Luis Chamberlain , linux-kernel@vger.kernel.org Subject: Re: [PATCH net-next v6 11/17] dt-bindings: net: pse-pd: Add another way of describing several PSE PIs Message-ID: <5230d786-44a8-45a0-ab0d-e1aa4ab6a836@lunn.ch> References: <20240326-feature_poe-v6-0-c1011b6ea1cb@bootlin.com> <20240326-feature_poe-v6-11-c1011b6ea1cb@bootlin.com> <171146756753.2253156.218733720090104400.robh@kernel.org> Precedence: bulk X-Mailing-List: linux-kernel@vger.kernel.org List-Id: List-Subscribe: List-Unsubscribe: MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <171146756753.2253156.218733720090104400.robh@kernel.org> On Tue, Mar 26, 2024 at 10:39:28AM -0500, Rob Herring wrote: > > On Tue, 26 Mar 2024 15:04:48 +0100, Kory Maincent wrote: > > From: Kory Maincent (Dent Project) > > > > PSE PI setup may encompass multiple PSE controllers or auxiliary circuits > > that collectively manage power delivery to one Ethernet port. > > Such configurations might support a range of PoE standards and require > > the capability to dynamically configure power delivery based on the > > operational mode (e.g., PoE2 versus PoE4) or specific requirements of > > connected devices. In these instances, a dedicated PSE PI node becomes > > essential for accurately documenting the system architecture. This node > > would serve to detail the interactions between different PSE controllers, > > the support for various PoE modes, and any additional logic required to > > coordinate power delivery across the network infrastructure. > > > > The old usage of "#pse-cells" is unsuficient as it carries only the PSE PI > > index information. > > > > Signed-off-by: Kory Maincent > > --- > My bot found errors running 'make DT_CHECKER_FLAGS=-m dt_binding_check' > on your patch (DT_CHECKER_FLAGS is new in v5.13): > > yamllint warnings/errors: > > dtschema/dtc warnings/errors: > > > doc reference errors (make refcheckdocs): > Warning: Documentation/devicetree/bindings/net/pse-pd/pse-controller.yaml references a file that doesn't exist: Documentation/networking/pse-pd/pse-pi.rst > Documentation/devicetree/bindings/net/pse-pd/pse-controller.yaml: Documentation/networking/pse-pd/pse-pi.rst Is this a false positive? Andrew