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: Thu, 7 Oct 2021 23:09:32 +0300 From: Nikita Yushchenko <nikita.yoush@...entembedded.com> To: Geert Uytterhoeven <geert@...ux-m68k.org> Cc: Geert Uytterhoeven <geert+renesas@...der.be>, Michael Turquette <mturquette@...libre.com>, Stephen Boyd <sboyd@...nel.org>, Linux-Renesas <linux-renesas-soc@...r.kernel.org>, linux-clk <linux-clk@...r.kernel.org>, Linux Kernel Mailing List <linux-kernel@...r.kernel.org>, Andrey Gusakov <andrey.gusakov@...entembedded.com> Subject: Re: [PATCH] clk: renesas: r8a779[56]x: add MLP clock > These additions look fine to me. I'm only wondering about the > actual parent clocks, which are not well-documented in the Hardware > User's Manual. > It does say that MLP uses the Audio main bus (AXI). > The related AUDIO-DMAC uses S1D2, which runs at 266 MHz, while S2D1 > runs at 400 MHz? This patch was included in this form into Renesas BSP for years. Indeed, the information on the parent clock is missing in the manual, and can be inexact here. I've sent a question to our contact at Renesas but not sure they will reply. But, AFAIU, these parent clocks are not software-controlled, so having them wrong does not result in any issues other than inexact information exported via sysfs/debugfs. > BTW, do you plan to enable full support for MLP in the upstream kernel? Yes, we are upstreaming full KF board support now. Nikita
Powered by blists - more mailing lists