linux-kernel - Re: [PATCH v2 00/11] Add Mobileye EyeQ system controller support (clk, reset, pinctrl)

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]

Date: Fri, 03 May 2024 19:34:35 -0700
From: Stephen Boyd <sboyd@...nel.org>
To: Conor Dooley <conor+dt@...nel.org>, Greg Kroah-Hartman <gregkh@...uxfoundation.org>, Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>, Lee Jones <lee@...nel.org>, Linus Walleij <linus.walleij@...aro.org>, Michael Turquette <mturquette@...libre.com>, Philipp Zabel <p.zabel@...gutronix.de>, Rafael J. Wysocki <rafael@...nel.org>, Rob Herring <robh@...nel.org>, Thomas Bogendoerfer <tsbogend@...ha.franken.de>, Théo Lebrun <theo.lebrun@...tlin.com>
Cc: linux-mips@...r.kernel.org, devicetree@...r.kernel.org, linux-kernel@...r.kernel.org, linux-clk@...r.kernel.org, linux-gpio@...r.kernel.org, Vladimir Kondratiev <vladimir.kondratiev@...ileye.com>, Gregory CLEMENT <gregory.clement@...tlin.com>, Thomas Petazzoni <thomas.petazzoni@...tlin.com>, Tawfik Bayouk <tawfik.bayouk@...ileye.com>, Théo Lebrun <theo.lebrun@...tlin.com>
Subject: Re: [PATCH v2 00/11] Add Mobileye EyeQ system controller support (clk, reset, pinctrl)

Quoting Théo Lebrun (2024-05-03 07:20:45)
> Hello,
> 
> This builds on previous EyeQ5 system-controller revisions[0], supporting
> EyeQ5, EyeQ6L and EyeQ6H. We expose a few OLB system-controller
> features here:
>  - Clocks: some read-only PLLs derived from main crystal and some
>    divider clocks based on PLLs.
>  - Resets.
>  - Pin controller, only on EyeQ5 (rest will use generic pinctrl-single).
> 
> EyeQ6H is special in that it has seven instances of this
> system-controller. Those are spread around and cannot be seen as a
> single device, hence are exposed as seven DT nodes and seven
> compatibles.
> 
> This revision differs from previous in that it exposes all devices as a
> single DT node. Driver-wise, a MFD registers multiple cells for each
> device. Each driver is still in isolation from one another, each in
> their respective subsystem.

Why can't you use auxiliary device and driver APIs?