Received: by 2002:a25:2c96:0:0:0:0:0 with SMTP id s144csp735580ybs; Sun, 24 May 2020 20:08:40 -0700 (PDT) X-Google-Smtp-Source: ABdhPJz3awOEIBJEBFsk5U8BDrBPCQKxOrj4mB/jHr89+2m1mykJFqL0yLkx8NFm7BSCVR02w2XU X-Received: by 2002:a17:907:2701:: with SMTP id w1mr15692039ejk.317.1590376120107; Sun, 24 May 2020 20:08:40 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1590376120; cv=none; d=google.com; s=arc-20160816; b=BetJ3768wKd3ugIgMd5hi9x0K7EQQornVkNmpgnaPTJTXztlhw66Nsb297maVe/gUj 99CS7NmxwpdBtc1rxnayDUCpGPmA1qMf6UwmvFAJy52HtWR/9babk1NzxRbHquJgOeJZ mPjktzPkVVnJBjZ3439m4WwyPT+54/O6MaFls7/0UcjJZjVVvsR0mHG9v0At4azCsnTZ lJ8lW2yl3dVn1bPbw/OnC7KwL775wKO46glDWzNt0zYUvPB4ZwdfUhpJrfvdApU8Btk4 0xzOUm06MuOybbkUwq4ISkibt7vUjg/j4aU9q1aSsuhHf/hMy/wqVoaM6/6jJLgNlP+q jgtg== ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=arc-20160816; h=list-id:precedence:sender:content-transfer-encoding :content-language:in-reply-to:mime-version:user-agent:date :message-id:from:references:cc:to:subject; bh=BSYHpJLGhCpDujFmICyBzmk/HLz+ih5sAYGgY6OrtKg=; b=FnmHAkIhaW5JF/R5JeqogaGAAB1KwmOH8eXE5b5EOc0Z67xAuKTsc8rp7LRAuNFwkq PZkDw61N0XkdMNVlm1h2QI3H3kN/SYXUSf4mDTDQ6YCjA3F67VrkrWLDwrLYhJIVtGWm IMUPBrtGj6qCsC6tLcOkruEfFDpFNsjt+WERP+oxiAke788F4G6N1wvfIrvY8lvDfFZy Hbg1EdVrhIxuR2x60DiZui7cGx64dg1G/y6EuV1x8Rthi6a2HEnL0njt5+h7MnLr1Epy WGFkcS8GNQQT/7BMEZhrTZn4rSnnNuhfAgRDAWhqefkTCvCUOJG4RaSbmT/bhrrcVgq7 /8hQ== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [23.128.96.18]) by mx.google.com with ESMTP id a6si4686747edy.125.2020.05.24.20.08.18; Sun, 24 May 2020 20:08:40 -0700 (PDT) Received-SPF: pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) client-ip=23.128.96.18; Authentication-Results: mx.google.com; spf=pass (google.com: domain of linux-kernel-owner@vger.kernel.org designates 23.128.96.18 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S2388716AbgEYCq5 (ORCPT + 99 others); Sun, 24 May 2020 22:46:57 -0400 Received: from foss.arm.com ([217.140.110.172]:35100 "EHLO foss.arm.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S2388136AbgEYCq4 (ORCPT ); Sun, 24 May 2020 22:46:56 -0400 Received: from usa-sjc-imap-foss1.foss.arm.com (unknown [10.121.207.14]) by usa-sjc-mx-foss1.foss.arm.com (Postfix) with ESMTP id 16EB531B; Sun, 24 May 2020 19:46:56 -0700 (PDT) Received: from [192.168.122.166] (unknown [172.31.20.19]) by usa-sjc-imap-foss1.foss.arm.com (Postfix) with ESMTPSA id B46FD3F305; Sun, 24 May 2020 19:46:55 -0700 (PDT) Subject: Re: [RFC 01/11] net: phy: Don't report success if devices weren't found To: Russell King - ARM Linux admin Cc: netdev@vger.kernel.org, davem@davemloft.net, andrew@lunn.ch, f.fainelli@gmail.com, hkallweit1@gmail.com, madalin.bucur@oss.nxp.com, calvin.johnson@oss.nxp.com, linux-kernel@vger.kernel.org References: <20200522213059.1535892-1-jeremy.linton@arm.com> <20200522213059.1535892-2-jeremy.linton@arm.com> <20200523182054.GW1551@shell.armlinux.org.uk> From: Jeremy Linton Message-ID: Date: Sun, 24 May 2020 21:46:55 -0500 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.8.0 MIME-Version: 1.0 In-Reply-To: <20200523182054.GW1551@shell.armlinux.org.uk> Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Thanks for taking a look at this. On 5/23/20 1:20 PM, Russell King - ARM Linux admin wrote: > On Fri, May 22, 2020 at 04:30:49PM -0500, Jeremy Linton wrote: >> C45 devices are to return 0 for registers they haven't >> implemented. This means in theory we can terminate the >> device search loop without finding any MMDs. In that >> case we want to immediately return indicating that >> nothing was found rather than continuing to probe >> and falling into the success state at the bottom. > > This is a little confusing when you read this comment: > > /* If mostly Fs, there is no device there, > * then let's continue to probe more, as some > * 10G PHYs have zero Devices In package, > * e.g. Cortina CS4315/CS4340 PHY. > */ > > Since it appears to be talking about the case of a PHY where *devs will > be zero. However, tracking down the original submission, it seems this > is not the case at all, and the comment is grossly misleading. > > It seems these PHYs only report a valid data in the Devices In Package > registers for devad=0 - it has nothing to do with a zero Devices In > Package. Yes, this ended up being my understanding of this commit, and is part of my justification for starting the devices search at the reserved address 0 rather than 1. > > Can I suggest that this comment is fixed while we're changing the code > to explicitly reject this "zero Devices In package" so that it's not > confusing? Its probably better to kill it in 5/11 with a mention that we are starting at a reserved address? OTOH, I'm a bit concerned that reading at 0 as the first address will cause problems because the original code was only triggering it after a read returning 0xFFFFFFFF at a valid MMD address. It does simplify/clarify the loop though. If it weren't for this 0 read, I would have tried to avoid some of the additional MMD reserved addresses.