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 C31D532C85; Mon, 28 Apr 2025 14:08:33 +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=1745849315; cv=none; b=Rhnd1HXowxDDHh8VZOlHlzWQnwCuJT7XExnnA4f4ifBRIAOEvA8ZYdGS0FTYEyj/Ido1EbJ6RmSbjppoUIDR3dO1Px2nYSvwZZfIFG2Nj9QrKBQLUq8tb7tqa4fJjR8vJgjNkSOFlOs45CH6n0H9ySGhLVHS2FWDdg20dNplFQg= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1745849315; c=relaxed/simple; bh=N82UuaGkcXSgDvbJ/SYZp0qqmioxEerlUofG5QQN/bY=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=VN3Gceo61DJQBQRjxEekz6U3OAt3CeRSfrORhW9WDduvZ/b4anl4c9matqEvTxxDE9LW1soo+Rt/KB3zjWGjThWLiGDLX8QakLlxvmh4yhx2/kMnzeBFpKovSeugV4rENC7bXW991Bg4DZA6248Q36DweE8E1VCcJqmnycdXXEk= 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=skb4qs5G; 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="skb4qs5G" 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=aIpoS0ND3fqgX9y156pe5+DTr/v2sx0BpH1llI6WOd0=; b=skb4qs5GVkbEEle4HYIM/yPAtD 2wnqyHXOICSwi0UCqYjBEO3Mr2FyKKapL7KS1cf8RfobEAdNTs1diMML0dUhuOKZ+PkYas6k8h4eV gvAG3s8P1cP6asKazO8WG/M0XtoSyIOok25LS48Gp/bGqPv/+keIUJJJ2TYaOR/1TirI=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1u9P9W-00AqR4-GB; Mon, 28 Apr 2025 16:08:10 +0200 Date: Mon, 28 Apr 2025 16:08:10 +0200 From: Andrew Lunn To: Matthias Schiffer Cc: "Russell King (Oracle)" , "David S. Miller" , Eric Dumazet , Jakub Kicinski , Paolo Abeni , Rob Herring , Krzysztof Kozlowski , Conor Dooley , Andy Whitcroft , Dwaipayan Ray , Lukas Bulwahn , Joe Perches , Jonathan Corbet , Nishanth Menon , Vignesh Raghavendra , Siddharth Vadapalli , Roger Quadros , Tero Kristo , linux-doc@vger.kernel.org, linux-kernel@vger.kernel.org, netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org, linux@ew.tq-group.com Subject: Re: [PATCH net-next 1/4] dt-bindings: net: ethernet-controller: update descriptions of RGMII modes Message-ID: <9b9fc5d0-e973-4f4f-8dd5-d3896bf29093@lunn.ch> References: <218a27ae2b2ef2db53fdb3573b58229659db65f9.1744710099.git.matthias.schiffer@ew.tq-group.com> 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: > > However, with the yaml stuff, if that is basically becoming "DT > > specification" then it needs to be clearly defined what each value > > actually means for the system, and not this vague airy-fairy thing > > we have now. > I agree with Russell that it seems preferable to make it unambiguous whether > delays are added on the MAC or PHY side, in particular for fine-tuning. If > anything is left to the implementation, we should make the range of acceptable > driver behavior very clear in the documentation. I think we should try the "Informative" route first, see what the DT Maintainers think when we describe in detail how Linux interprets these values. I don't think a whole new set of properties will solve anything. I would say the core of the problem is that there are multiple ways of getting a working system, many of which don't fit the DT binding. But DT developers don't care about that, they are just happy when it works. Adding a different set of properties won't change that. Andrew