[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <1861597197.20753.36a104a6-5284-487f-b397-da7ff0407f1f.open-xchange@email.1und1.de>
Date: Thu, 12 May 2016 16:50:54 +0200 (CEST)
From: Stefan Wahren <stefan.wahren@...e.com>
To: kernel@...tin.sperl.org
Cc: Eric Anholt <eric@...olt.net>, Lee Jones <lee@...nel.org>,
Pawel Moll <pawel.moll@....com>,
Rob Herring <robh+dt@...nel.org>,
linux-rpi-kernel@...ts.infradead.org,
Stephen Warren <swarren@...dotorg.org>,
linux-kernel@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
Russell King <linux@....linux.org.uk>,
Mark Rutland <mark.rutland@....com>, devicetree@...r.kernel.org
Subject: Re: [PATCH 0/4] add minimal bcm2835-sdram driver
Hi Martin,
> kernel@...tin.sperl.org hat am 12. Mai 2016 um 14:38 geschrieben:
>
>
> From: Martin Sperl <kernel@...tin.sperl.org>
>
> As the sdram clock is a critical clock to the system
> the minimal bcm2835-sdram driver claims (and enables)
> this clock and also exposes the corresponding sdram
> registers via debugfs.
sounds like this driver should fix an clock handling issue. Unfortunately this
isn't a solution in case the driver is disabled.
Does the GPU firmware handle the SDRAM controller or is it initialized by
bootcode?
Stefan
Powered by blists - more mailing lists