linux-kernel - Re: [PATCH v2 00/10] Usable clocks on Mobileye EyeQ5 & EyeQ6H

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

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <D5MPD4TS05ML.12HKW12NG083W@bootlin.com>
Date: Fri, 15 Nov 2024 12:06:58 +0100
From: Théo Lebrun <theo.lebrun@...tlin.com>
To: "Thomas Bogendoerfer" <tsbogend@...ha.franken.de>
Cc: <linux-mips@...r.kernel.org>, <linux-kernel@...r.kernel.org>, "Thomas
 Petazzoni" <thomas.petazzoni@...tlin.com>, "Tawfik Bayouk"
 <tawfik.bayouk@...ileye.com>, "Vladimir Kondratiev"
 <vladimir.kondratiev@...ileye.com>, Grégory Clement
 <gregory.clement@...tlin.com>, "Stephen Boyd" <sboyd@...nel.org>, "Michael
 Turquette" <mturquette@...libre.com>
Subject: Re: [PATCH v2 00/10] Usable clocks on Mobileye EyeQ5 & EyeQ6H

On Fri Nov 15, 2024 at 10:34 AM CET, Thomas Bogendoerfer wrote:
> On Fri, Nov 15, 2024 at 10:24:29AM +0100, Théo Lebrun wrote:
> > On Wed Nov 6, 2024 at 5:03 PM CET, Théo Lebrun wrote:
> > >  - MIPS:
> > >    [PATCH v2 09/10] MIPS: mobileye: eyeq5: use OLB as provider for fixed factor clocks
> > >    [PATCH v2 10/10] MIPS: mobileye: eyeq6h: add OLB nodes OLB and remove fixed clocks
> > 
> > Do you think we can make those two patches go in before the next merge
> > window? Stephen just accepted the above patches. This makes both MIPS
> > platforms usable on upstream kernels!
>
> I've applied, but not pushed, because this
>
> Error: /local/tbogendoerfer/korg/linux/arch/mips/boot/dts/mobileye/eyeq5.dtsi:20.19-20 syntax error
> FATAL ERROR: Unable to parse input treeo
>
> My tree misses the new CLK defines.
>
> I haven't decided whether I'll ignore that and push it now or put them
> into a second request vor 6.13.

It was either breaking the driver build or the DTS builds. I preferred
breaking DTS as that way no kernel robot would come yelling after me.
Sorry it has to fall onto you to handle that.

Thanks,

--
Théo Lebrun, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com