From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S934261AbdKBTGd (ORCPT ); Thu, 2 Nov 2017 15:06:33 -0400 Received: from mail-qk0-f196.google.com ([209.85.220.196]:48228 "EHLO mail-qk0-f196.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S932571AbdKBTGb (ORCPT ); Thu, 2 Nov 2017 15:06:31 -0400 X-Google-Smtp-Source: ABhQp+T2OogESjsF/qcHa3eya1lfyFHDhFvgzCPygZnK6x0HZohQZHMPEbrf2DoECM+RcBzaExifmA== Subject: Re: [PATCH 00/12] bcm63xx-rng conversion to bcm2835-rng To: Stefan Wahren , Florian Fainelli Cc: Krzysztof Kozlowski , Ray Jui , Eric Anholt , Rob Herring , Steffen Trumtrar , Harald Freudenberger , Russell King , "moderated list:BROADCOM BCM2835 ARM ARCHITECTURE" , PrasannaKumar Muralidharan , Scott Branden , "open list:HARDWARE RANDOM NUMBER GENERATOR CORE" , Martin Kaiser , Herbert Xu , "maintainer:BROADCOM BCM281XX/BCM11XXX/BCM216XX ARM ARCHITE..." , Matt Mackall , Mark Rutland , "moderated list:BROADCOM BCM2835 ARM ARCHITECTURE" , linux-kernel@vger.kernel.org, "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" , Sean Wang References: <20171102010408.27736-1-f.fainelli@gmail.com> <1329593033.127526.1509649260041@email.1und1.de> From: Florian Fainelli Message-ID: Date: Thu, 2 Nov 2017 12:06:24 -0700 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:52.0) Gecko/20100101 Thunderbird/52.2.1 MIME-Version: 1.0 In-Reply-To: <1329593033.127526.1509649260041@email.1und1.de> Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi Stefan, On 11/02/2017 12:01 PM, Stefan Wahren wrote: > Hi Florian, > >> Florian Fainelli hat am 2. November 2017 um 02:03 geschrieben: >> >> >> Hi, >> >> As it usually happens when there is a fair amount of HW IP block re-use, >> competing implementations show up. In that case the BCM2835 HWRNG driver and >> the BCM63xx RNG driver have exactly the same register offsets and this is >> indeed the same piece of HW. >> >> This patch series first prepares the bcm2835-rng to be more future proof and >> support newer platforms, and the last part brings in what is necessary to >> migrate the bcm63xx-rng over to bcm2835-rng. Finally we delete bcm63xx-rng >> completely. >> >> The reason why BCM2835 RNG was kept over BCM63xx RNG is because the former >> deals correctly with a warm up count and the number of words available in the >> FIFO size. > > are these the same patches as in this branch [1]? > > https://github.com/ffainelli/linux/commits/rng-consolidation Yes, this branch contains these 12 patches. -- Florian