[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <35c11eae-4ebe-16aa-0d87-1858e90db5d6@i2se.com>
Date: Mon, 20 May 2019 14:14:29 +0200
From: Stefan Wahren <stefan.wahren@...e.com>
To: Nicolas Saenz Julienne <nsaenzjulienne@...e.de>,
Florian Fainelli <f.fainelli@...il.com>,
Ray Jui <rjui@...adcom.com>,
Scott Branden <sbranden@...adcom.com>,
bcm-kernel-feedback-list@...adcom.com,
Eric Anholt <eric@...olt.net>
Cc: linux-pm@...r.kernel.org, sboyd@...nel.org,
viresh.kumar@...aro.org, mturquette@...libre.com,
ptesarik@...e.com, rjw@...ysocki.net, linux-kernel@...r.kernel.org,
mbrugger@...e.de, linux-rpi-kernel@...ts.infradead.org,
linux-clk@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
ssuloev@...altech.com
Subject: Re: [RFC v2 3/5] clk: bcm2835: use firmware interface to update pllb
On 20.05.19 14:11, Stefan Wahren wrote:
>
> Please verify that the kernel still works (and this clock driver probe)
> under the following conditions:
>
> - CONFIG_RASPBERRYPI_FIRMWARE=n
> - CONFIG_RASPBERRYPI_FIRMWARE=m
> - older DTBs without patch #1
Sorry, i meant patch #4
Powered by blists - more mailing lists