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=-5.8 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,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 25D46C47092 for ; Wed, 2 Jun 2021 02:28:33 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 028CF613AD for ; Wed, 2 Jun 2021 02:28:32 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230350AbhFBCaN (ORCPT ); Tue, 1 Jun 2021 22:30:13 -0400 Received: from vps0.lunn.ch ([185.16.172.187]:40078 "EHLO vps0.lunn.ch" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S229828AbhFBCaM (ORCPT ); Tue, 1 Jun 2021 22:30:12 -0400 DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=lunn.ch; s=20171124; h=In-Reply-To:Content-Disposition:Content-Type:MIME-Version: References:Message-ID:Subject:Cc:To:From:Date:From:Sender:Reply-To:Subject: Date:Message-ID:To:Cc:MIME-Version:Content-Type:Content-Transfer-Encoding: Content-ID:Content-Description:Content-Disposition:In-Reply-To:References; bh=4JoMGfga1VbTByDb+krUTuutqYAcuOdoQ70Y27jTzf8=; b=fJXgFc/GRD6OG68GN6GC7fmcNJ sCxWFlYEPPu4yPMgLkS+5YrzUpNY5fCDZ0fhqbHEIo9tjUD3owCdEJNgisENn7quOI6GK7UPcesrt 1I8Qv271k43/RVjJiIT/byYplg7l0n5DINSoQjQynWPfsSi4PXfnM+ZMOGjUgGwdSuSs=; Received: from andrew by vps0.lunn.ch with local (Exim 4.94.2) (envelope-from ) id 1loGcD-007NlP-ME; Wed, 02 Jun 2021 04:28:17 +0200 Date: Wed, 2 Jun 2021 04:28:17 +0200 From: Andrew Lunn To: Wong Vee Khee Cc: Giuseppe Cavallaro , Alexandre Torgue , Jose Abreu , "David S . Miller" , Jakub Kicinski , Maxime Coquelin , netdev@vger.kernel.org, linux-stm32@st-md-mailman.stormreply.com, linux-arm-kernel@lists.infradead.org, linux-kernel@vger.kernel.org Subject: Re: [PATCH net-next 1/1] net: stmmac: enable platform specific safety features Message-ID: References: <20210601135235.1058841-1-vee.khee.wong@linux.intel.com> <20210601225332.GA28151@linux.intel.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20210601225332.GA28151@linux.intel.com> Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Wed, Jun 02, 2021 at 06:53:32AM +0800, Wong Vee Khee wrote: > On Wed, Jun 02, 2021 at 12:11:57AM +0200, Andrew Lunn wrote: > > On Tue, Jun 01, 2021 at 09:52:35PM +0800, Wong Vee Khee wrote: > > > On Intel platforms, not all safety features are enabled on the hardware. > > > > Is it possible to read a register is determine what safety features > > have been synthesised? > > > > No. The value of these registers after reset are 0x0. We need to set it > manually. That is not what i asked. Sometimes with IP you synthesise from VHDL or Verilog, there are registers which describe which features you have actually enabled/disabled in the synthesis. Maybe the stmmac has such a register describing which safety features are actually available in your specific version of the IP? You could go ask your ASIC engineers. Or maybe Synopsys can say that there are no such registers. Andrew