[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-Id: <20190912.010130.736236657631199212.davem@davemloft.net>
Date: Thu, 12 Sep 2019 01:01:30 +0200 (CEST)
From: David Miller <davem@...emloft.net>
To: simon.horman@...ronome.com
Cc: jakub.kicinski@...ronome.com, netdev@...r.kernel.org,
oss-drivers@...ronome.com, dirk.vandermerwe@...ronome.com
Subject: Re: [PATCH net-next] nfp: read chip model from the PluDevice
register
From: Simon Horman <simon.horman@...ronome.com>
Date: Wed, 11 Sep 2019 16:21:18 +0100
> From: Dirk van der Merwe <dirk.vandermerwe@...ronome.com>
>
> The PluDevice register provides the authoritative chip model/revision.
>
> Since the model number is purely used for reporting purposes, follow
> the hardware team convention of subtracting 0x10 from the PluDevice
> register to obtain the chip model/revision number.
>
> Suggested-by: Francois H. Theron <francois.theron@...ronome.com>
> Signed-off-by: Dirk van der Merwe <dirk.vandermerwe@...ronome.com>
> Signed-off-by: Simon Horman <simon.horman@...ronome.com>
Applied.
Powered by blists - more mailing lists