Received: by 2002:ac0:a594:0:0:0:0:0 with SMTP id m20-v6csp4802568imm; Fri, 18 May 2018 10:53:53 -0700 (PDT) X-Google-Smtp-Source: AB8JxZogfZIE/jcj7T1+jb9DvPmCzXp17trapsgXfVnbgLg/hX+UHLCJon/J3LBLV1XCIPaDRJa0 X-Received: by 2002:a62:dfcd:: with SMTP id d74-v6mr10425083pfl.114.1526666032973; Fri, 18 May 2018 10:53:52 -0700 (PDT) ARC-Seal: i=1; a=rsa-sha256; t=1526666032; cv=none; d=google.com; s=arc-20160816; b=d7XpcPvRtF38/+Ueqn1qlZ+viCBQa855qewPkTKcDW9ft/R3Z9EN00HlGv7/pkqkv1 WAFWXRb3pwpr5yeGonkpy7e4D0A624izBrdIwRM0QHfPRT6auibryOBAGHsyMCWJWP6X c4PQNl4M9VkYxNaM+XlJXZDx63Tz/QSN8pKeqxtdcgzHp1vHk27JiWfGd8T15WuAFzIT Acqa7gJXy5do4t2w9igPrS7yJdLzIA8fRFhIrxQSHIAx9Az7Lpyv7J2Jnqr+X8b5h/ij NWOPSFUgQVECw5aU+fBCB4KwryWoHXNLn6YQKXI5qAZpESdgfEtZ7q0Od3SchUNYhWMa FZEQ== 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:mime-version :references:in-reply-to:from:subject:cc:to:message-id:date :arc-authentication-results; bh=oP+h8jTZnDlZBoJYsSnl7Sae4yts5YRjaFuTW11SBIg=; b=f9HU6IefoLaPQ9d9aHiWJAXc5Ef+EDfUj2jICKVMxZyZPA5Ak+QgJyncjJowN0OCON B5RazUcg/vMthPFwTf3k3qMy+O5Y/vg4lkwSXvDoJcc9CKvr9ctLG+B+dzR19+FLkqhl zMeGECsXcAoVk9s2aFLR7tDb4YJT1RCRun1DNgeNASiAbPQltT8HDUs9aJv0fGqkLRAc xMZr3ZBhmMYTcBiRktDwRe2MQE5mrxp8MFw2j4YdirJgPNlkg1p+vdxBKWcU7f4EzpA8 nCMLH8ExjF1NWnLKLadbuKci+bmdnYQDu4lD8aTppCM1lic/UYupYc0EdMUuDH0YPz30 Zsog== ARC-Authentication-Results: i=1; mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Return-Path: Received: from vger.kernel.org (vger.kernel.org. [209.132.180.67]) by mx.google.com with ESMTP id y1-v6si7709546plt.316.2018.05.18.10.53.38; Fri, 18 May 2018 10:53:52 -0700 (PDT) Received-SPF: pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) client-ip=209.132.180.67; Authentication-Results: mx.google.com; spf=pass (google.com: best guess record for domain of linux-kernel-owner@vger.kernel.org designates 209.132.180.67 as permitted sender) smtp.mailfrom=linux-kernel-owner@vger.kernel.org Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752433AbeERRwA (ORCPT + 99 others); Fri, 18 May 2018 13:52:00 -0400 Received: from shards.monkeyblade.net ([184.105.139.130]:48176 "EHLO shards.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751363AbeERRvy (ORCPT ); Fri, 18 May 2018 13:51:54 -0400 Received: from localhost (67.110.78.66.ptr.us.xo.net [67.110.78.66]) (using TLSv1 with cipher AES256-SHA (256/256 bits)) (Client did not present a certificate) (Authenticated sender: davem-davemloft) by shards.monkeyblade.net (Postfix) with ESMTPSA id C3BD71425B2DE; Fri, 18 May 2018 10:51:53 -0700 (PDT) Date: Fri, 18 May 2018 13:51:52 -0400 (EDT) Message-Id: <20180518.135152.51730771671749217.davem@davemloft.net> To: andrea.greco.gapmilano@gmail.com Cc: tobin@apporbit.com, a.greco@4sigma.it, m.grzeschik@pengutronix.de, linux-kernel@vger.kernel.org, netdev@vger.kernel.org Subject: Re: [PATCH 1/4] arcnet: com20020: Add com20020 io mapped version From: David Miller In-Reply-To: References: <20180517130529.2684-1-andrea.greco.gapmilano@gmail.com> <20180517.163113.2110198960037727630.davem@davemloft.net> X-Mailer: Mew version 6.7 on Emacs 25.3 / Mule 6.0 (HANACHIRUSATO) Mime-Version: 1.0 Content-Type: Text/Plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH, not delayed by milter-greylist-4.5.12 (shards.monkeyblade.net [149.20.54.216]); Fri, 18 May 2018 10:51:54 -0700 (PDT) Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org From: Andrea Greco Date: Fri, 18 May 2018 14:18:41 +0200 > In com20020.c found this: > /* FIXME: do this some other way! */ > if (!dev->dev_addr[0]) > dev->dev_addr[0] = arcnet_inb(ioaddr, 8); > > NODE-ID, must be univoque, for all arcnet network. > My previews idea was take random value but, this could create a > collision over network. > > A possible solution is: > In case of collision com20020 set a bit in status register. > Then peak a new NODE-ID and repeat this while correct NODE-ID is found. > > Other ideas is pass it via DTS. > But suppose have 2 same product in same network, same address same problem. > For this reason i prefer left standard driver behavior. > > Other ideas for solve this ? Is there no way to obtain a unique value from the device? If having a unique ID to talk on the ARCNET is so critical, there must be some way to properly allocation and use a unique ID. I guess this must be a general problem with this driver already. You still need to address the issue of 'dev' being leaked on probe error paths. Thank you.