From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=ZcOb=ZP=vger.kernel.org=netdev-owner@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.6 required=3.0 tests=DKIMWL_WL_HIGH,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,
	USER_AGENT_SANE_1 autolearn=no autolearn_force=no version=3.4.0
Received: from mail.kernel.org (mail.kernel.org [198.145.29.99])
	by smtp.lore.kernel.org (Postfix) with ESMTP id D3F38C432C0
	for <netdev@archiver.kernel.org>; Sat, 23 Nov 2019 21:00:09 +0000 (UTC)
Received: from vger.kernel.org (vger.kernel.org [209.132.180.67])
	by mail.kernel.org (Postfix) with ESMTP id 9ECD020679
	for <netdev@archiver.kernel.org>; Sat, 23 Nov 2019 21:00:09 +0000 (UTC)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=kernel.org;
	s=default; t=1574542809;
	bh=YYyYAAPakfDTbqU4rv89BoY++e3BhB4wn/UbQhVOcT0=;
	h=Date:From:To:Cc:Subject:References:In-Reply-To:List-ID:From;
	b=WcSq4kTL7W87Lh+CAc9VC/g8t9jnLyGk/HX6Ryuymv79mPEPuBitLzlIrkv6GsA8j
	 suo/p0uVudDNAipQ3R9ResB++TgcTtxuCxgcJJCfnPILIP9aJoPqyu4tnD53d0sciM
	 5dqTvOu/yTiksCGfQTsN9S++MYInXDZ4VfaUdWYE=
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1726751AbfKWVAI (ORCPT <rfc822;netdev@archiver.kernel.org>);
        Sat, 23 Nov 2019 16:00:08 -0500
Received: from mail.stusta.mhn.de ([141.84.69.5]:52966 "EHLO
        mail.stusta.mhn.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1726638AbfKWVAI (ORCPT
        <rfc822;netdev@vger.kernel.org>); Sat, 23 Nov 2019 16:00:08 -0500
Received: from [127.0.0.1] (localhost [127.0.0.1])
        by mail.stusta.mhn.de (Postfix) with ESMTPSA id 47L5KJ451wz4R;
        Sat, 23 Nov 2019 22:00:04 +0100 (CET)
Date:   Sat, 23 Nov 2019 23:00:01 +0200
From:   Adrian Bunk <bunk@kernel.org>
To:     Dan Murphy <dmurphy@ti.com>
Cc:     Andrew Lunn <andrew@lunn.ch>,
        Florian Fainelli <f.fainelli@gmail.com>,
        Heiner Kallweit <hkallweit1@gmail.com>, netdev@vger.kernel.org
Subject: Re: dp83867: Why does ti,fifo-depth set only TX, and why is it
 mandatory?
Message-ID: <20191123210001.GA20458@localhost>
References: <20191114162431.GA21979@localhost>
 <190bd4d3-4bbd-3684-da31-2335b7c34c2a@ti.com>
 <20191114194715.GA29047@localhost>
 <d20a0c5a-507c-dd75-0951-e0733daf4a6e@ti.com>
 <08b61f8c-bd7b-7ea7-2e47-50ddb540d67f@ti.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
In-Reply-To: <08b61f8c-bd7b-7ea7-2e47-50ddb540d67f@ti.com>
User-Agent: Mutt/1.10.1 (2018-07-13)
Sender: netdev-owner@vger.kernel.org
Precedence: bulk
List-ID: <netdev.vger.kernel.org>
X-Mailing-List: netdev@vger.kernel.org

On Thu, Nov 21, 2019 at 02:24:01PM -0600, Dan Murphy wrote:
> Adrian

Hi Dan,

>...
> OK the HW team said that FIFO depth is no longer a mandatory field to be
> written for either RGMII or SGMII.
> 
> So my suggestion here is that we deprecate, but support in the driver, the
> ti-fifo-depth, and add the already documented
> 
> rx-fifo-depth and tx-fifo-depth as optional DT entries.
> 
> So I can change the driver and DT docs and test the RGMII device as above as
> long as we are in agreement

sounds good to me.

> Dan

Thanks
Adrian