lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Mon, 24 Feb 2020 20:25:46 +0100 From: Stefan Wahren <stefan.wahren@...e.com> To: Maxime Ripard <maxime@...no.tech>, Nicolas Saenz Julienne <nsaenzjulienne@...e.de>, Eric Anholt <eric@...olt.net> Cc: Tim Gover <tim.gover@...pberrypi.com>, Dave Stevenson <dave.stevenson@...pberrypi.com>, Stephen Boyd <sboyd@...nel.org>, Michael Turquette <mturquette@...libre.com>, linux-kernel@...r.kernel.org, dri-devel@...ts.freedesktop.org, linux-clk@...r.kernel.org, bcm-kernel-feedback-list@...adcom.com, linux-rpi-kernel@...ts.infradead.org, Phil Elwell <phil@...pberrypi.com>, linux-arm-kernel@...ts.infradead.org Subject: Re: [PATCH 16/89] clk: bcm: rpi: Add clock id to data Hi Maxime, Am 24.02.20 um 10:06 schrieb Maxime Ripard: > The driver has really only supported one clock so far and has hardcoded the > ID used in communications with the firmware in all the functions > implementing the clock framework hooks. Let's store that in the clock data > structure so that we can support more clocks later on. thank you for this series. I looked through it but i couldn't find an explanation why we need to expose firmware clocks via DT instead of extending clk-bcm2835. The whole pllb / clk-raspberrypi stuff was an exception to get cpufreq working. I prefer to keep it an exception. Regards Stefan
Powered by blists - more mailing lists