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 C9DBB21660A; Thu, 9 Jan 2025 14:16:22 +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=1736432184; cv=none; b=X5oapuKhmIAqwV6TkPs1cjaWPTXlQCxfy3tLRxJ8Gi86AgEuX02dFM42TQ09LNLFKQYk9rj4WkvhNEgVzt6QDnNGp8PrXB67IW/3F2C5qtnS4v+wQNkDZAb7nkVBvOENwYL9O+597ktw6I2NaGJtPv/BlVGDF1akyLUbLo0c6MU= ARC-Message-Signature:i=1; a=rsa-sha256; d=subspace.kernel.org; s=arc-20240116; t=1736432184; c=relaxed/simple; bh=IZ0acXhT0YMIXDW/44pyB4O/k30FmTzei1H7JU0mxac=; h=Date:From:To:Cc:Subject:Message-ID:References:MIME-Version: Content-Type:Content-Disposition:In-Reply-To; b=dktDtKmsxdn/2L8EWxWO6yDvgtDEjQSHjVS6YHAl8kvaXgDh/CjliPBTno5Q8EZzIXDR/5HKvmqKCmOXkJBJJ16MCFngJWDtIyxa1bqxRCnR5SmPnrfPSIl4e9MWjl7y+w2g7LYU3HGrmI/1ZFj3J2XIkLXY74D5lhKaAbTW47s= 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=WoCyI9/2; 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="WoCyI9/2" 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=9JESPOQS4EHqjM5dyI36/1mlgYqQI2J+aklQe3TUDMk=; b=WoCyI9/2gjr2asx5Kgb+1GDr4r Dt2N92ECfFohKn8OS+gWxGtDgABQvRW/ny4oM9Zb4F3OFIEQalk0n9goY6oGMLbgHo/79I4JxZ+oE pSYFobCNiqfq1O3KXlieCm/8EgVSlebNa8KeFVCvrVLP8+609r1papRROmM0oRNHhR2M=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1tVtKP-002uXi-Fv; Thu, 09 Jan 2025 15:16:05 +0100 Date: Thu, 9 Jan 2025 15:16:05 +0100 From: Andrew Lunn To: Basharath Hussain Khaja Cc: danishanwar@ti.com, rogerq@kernel.org, andrew+netdev@lunn.ch, davem@davemloft.net, edumazet@google.com, kuba@kernel.org, pabeni@redhat.com, robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org, nm@ti.com, ssantosh@kernel.org, tony@atomide.com, richardcochran@gmail.com, parvathi@couthit.com, schnelle@linux.ibm.com, rdunlap@infradead.org, diogo.ivo@siemens.com, m-karicheri2@ti.com, horms@kernel.org, jacob.e.keller@intel.com, m-malladi@ti.com, javier.carrasco.cruz@gmail.com, afd@ti.com, s-anna@ti.com, linux-arm-kernel@lists.infradead.org, netdev@vger.kernel.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, linux-omap@vger.kernel.org, pratheesh@ti.com, prajith@ti.com, vigneshr@ti.com, praneeth@ti.com, srk@ti.com, rogerq@ti.com, krishna@couthit.com, pmohan@couthit.com, mohan@couthit.com Subject: Re: [RFC PATCH 01/10] dt-bindings: net: ti: Adds device tree binding for DUAL-EMAC mode support on PRU-ICSS2 for AM57xx SOCs Message-ID: <4a8fb859-e173-42bf-8d9b-8d6423f45a9b@lunn.ch> References: <20250109105600.41297-1-basharath@couthit.com> <20250109105600.41297-2-basharath@couthit.com> Precedence: bulk X-Mailing-List: linux-omap@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: <20250109105600.41297-2-basharath@couthit.com> On Thu, Jan 09, 2025 at 04:25:51PM +0530, Basharath Hussain Khaja wrote: > From: Parvathi Pudi > > Documentation update for the newly added "pruss2_eth" device tree > node and its dependencies along with compatibility for PRU-ICSS > Industrial Ethernet Peripheral (IEP), PRU-ICSS Enhanced Capture > (eCAP) peripheral and using YAML binding document for AM57xx SoCs. If i was to do a side by side diff with the ICSSG, how much would be the same? Does it make sense to refactor this into a yaml file for all the common properties, and then yaml files for all the specific properties? Andrew