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 0CBD7C47255 for ; Mon, 11 May 2020 12:42:59 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id CEEA3207FF for ; Mon, 11 May 2020 12:42:58 +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="5QYScKwb" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1730146AbgEKMm6 (ORCPT ); Mon, 11 May 2020 08:42:58 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:53358 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1729666AbgEKMm5 (ORCPT ); Mon, 11 May 2020 08:42:57 -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=sinDIPAGMkTelQEyzHkAx61jqUBS8OA/yV4gH5A7mjA=; b=5QYScKwbb9/nzSLTIJzQ9yAeP8 4sCsF1CWxK4bj68mt5Hw5cbVCxQ4SJBdqfjy0mUz10lZHIxuV4Xv/VAbvab37cK/HEEme4mWyQO0t 55rj0zFMh8wPY+aQhCIvHDgMQWa9FqEniWfgiGzQz4606GsqomRRoXFmQhPPYzSOTpDE=; Received: from andrew by vps0.lunn.ch with local (Exim 4.93) (envelope-from ) id 1jY7ld-001qpC-BU; Mon, 11 May 2020 14:42:45 +0200 Date: Mon, 11 May 2020 14:42:45 +0200 From: Andrew Lunn To: Jiri Pirko Cc: Vadym Kochan , 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: <20200511124245.GA409897@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> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20200511112905.GH2245@nanopsycho> Sender: netdev-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: netdev@vger.kernel.org > >I understand this is not good, but currently this is simple solution to > >handle base MAC configuration for different boards which has this PP, > >otherwise it needs to by supported by platform drivers. Is there some > >generic way to handle this ? > > If the HW is not capable holding the mac, I think that you can have it > in platform data. The usual way for such HW is to generate random mac. > module parameter is definitelly a no-go. And i already suggested it should be a device tree property. Andrew