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 X-Spam-Level: X-Spam-Status: No, score=-3.8 required=3.0 tests=BAYES_00, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS 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 670A4C433DB for ; Tue, 12 Jan 2021 13:55:32 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 0D66422B30 for ; Tue, 12 Jan 2021 13:55:31 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1729029AbhALNzb (ORCPT ); Tue, 12 Jan 2021 08:55:31 -0500 Received: from vps0.lunn.ch ([185.16.172.187]:35666 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1725843AbhALNza (ORCPT ); Tue, 12 Jan 2021 08:55:30 -0500 Received: from andrew by vps0.lunn.ch with local (Exim 4.94) (envelope-from ) id 1kzK8B-000AKu-1G; Tue, 12 Jan 2021 14:54:43 +0100 Date: Tue, 12 Jan 2021 14:54:43 +0100 From: Andrew Lunn To: "ashiduka@fujitsu.com" Cc: "hkallweit1@gmail.com" , "linux@armlinux.org.uk" , "davem@davemloft.net" , "kuba@kernel.org" , "netdev@vger.kernel.org" , "torii.ken1@fujitsu.com" Subject: Re: [PATCH v2] net: phy: realtek: Add support for RTL9000AA/AN Message-ID: References: <20210110085221.5881-1-ashiduka@fujitsu.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org On Tue, Jan 12, 2021 at 05:14:21AM +0000, ashiduka@fujitsu.com wrote: > > For T1, it seems like Master is pretty important. Do you have > > information to be able to return the current Master/slave > > configuration, or allow it to be configured? See the nxp-tja11xx.c > > for an example. > > I think it's possible to return a Master/Slave configuration. Great. It would be good to add it. > By the way, do you need the cable test function as implemented in > nxp-tja11xx.c? We don't need it. But if you want to implement it, that would be great. Andrew