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=-0.6 required=3.0 tests=DKIM_INVALID,DKIM_SIGNED, 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 40605C54E8D for ; Mon, 11 May 2020 13:54:20 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 1425D20736 for ; Mon, 11 May 2020 13:54:20 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=fail reason="signature verification failed" (1024-bit key) header.d=lunn.ch header.i=@lunn.ch header.b="Ybxhfi/J" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730228AbgEKNyT (ORCPT ); Mon, 11 May 2020 09:54:19 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:53602 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1730407AbgEKNyJ (ORCPT ); Mon, 11 May 2020 09:54:09 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Type:MIME-Version:References:Message-ID: Subject:Cc:To:From:Date:Sender:Reply-To:Content-Transfer-Encoding:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=WaLCPKDlYTN7PG6jziEvzv4jpBO1YzFsUfFc0Au8bEo=; b=Ybxhfi/J86rdLrb2W+md8xD1zn 2SdswnS9uuxPvv51+c7kNLDqcjpB93cvzVI43Yk1wxbP6CDkStuXXl1+fTVRjKZa9A8QOQekPO9d5 wZxKgMKXkEG5pC4KCIN9yXmfcCrb6VSBm4kRimkf/4iBKIY4WFBqspKMohL6E9tvFILQ=; Received: from andrew by vps0.lunn.ch with local (Exim 4.93) (envelope-from ) id 1jY8sZ-001rH1-NC; Mon, 11 May 2020 15:53:59 +0200 Date: Mon, 11 May 2020 15:53:59 +0200 From: Andrew Lunn To: Vadym Kochan Cc: Jiri Pirko , netdev@vger.kernel.org, "David S. Miller" , Oleksandr Mazur , Serhiy Boiko , Serhiy Pshyk , Volodymyr Mytnyk , Taras Chornyi , Andrii Savka , Jiri Pirko , Ido Schimmel , Chris Packham Subject: Re: [RFC next-next v2 1/5] net: marvell: prestera: Add driver for Prestera family ASIC devices Message-ID: <20200511135359.GB413878@lunn.ch> References: <20200430232052.9016-1-vadym.kochan@plvision.eu> <20200430232052.9016-2-vadym.kochan@plvision.eu> <20200511103222.GF2245@nanopsycho> <20200511111134.GD25096@plvision.eu> <20200511112905.GH2245@nanopsycho> <20200511124245.GA409897@lunn.ch> <20200511130252.GE25096@plvision.eu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200511130252.GE25096@plvision.eu> Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org > Looks like it might be hard for the board manufacturing? I mean each > board item need to have updated dtb file with base mac address, instead > to have common dtb for the board type. > > And it sounds that platform data might be the way in case if the vendor > will implement platform device driver which will handle reading base mac > from eeprom (or other storage) depending on the board and put it to the > platform data which will be provided to prestera driver ? Hi Vadym This is not a new problem. Go look at the standard solutions to this. of_get_mac_address(), eth_platform_get_mac_address(), nvmem_get_mac_address(), of_get_mac_addr_nvmem(), etc. Andrew