From: =?utf-8?Q?=C3=81lvaro_Fern=C3=A1ndez_Rojas?= Date: Thu, 2 Apr 2020 17:57:14 +0200 Subject: [PATCH] nand: brcmnand: return without disabling clock In-Reply-To: <20200402154929.GT27133@bill-the-cat> References: <20200402083752.14077-1-noltari@gmail.com> <9631f3c5-a224-9e33-a681-4b81a095b5d2@gmail.com> <20200402154929.GT27133@bill-the-cat> Message-ID: <9F1168DC-57A0-4248-AF2D-3F6892364DF5@gmail.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de > El 2 abr 2020, a las 17:49, Tom Rini escribi?: > > On Thu, Apr 02, 2020 at 11:15:51AM +0200, Daniel Schwierzeck wrote: >> >> >> Am 02.04.20 um 10:37 schrieb ?lvaro Fern?ndez Rojas: >>> Linux Broadcom NAND driver only disabled clock if no childs are initialized. >>> This section of the code seems to have been accidentally dropped when it was >>> imported in U-Boot. >>> >>> Signed-off-by: ?lvaro Fern?ndez Rojas >>> --- >>> drivers/mtd/nand/raw/brcmnand/brcmnand.c | 9 ++++++++- >>> 1 file changed, 8 insertions(+), 1 deletion(-) >>> >> >> Reviewed-by: Daniel Schwierzeck > > Does this need to go in to v2020.04? Thanks! > > -- > Tom Not really. I tested it with a development branch and this affects bcm6362 devices (nand not currently supported), but it doesn?t affect bcm63268 devices (1 device supported). Best regards, ?lvaro.