linux-kernel - Re: [PATCH v2 2/2] dt-bindings: dsp: fsl: Add DSP optional clocks documentation

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:   Thu, 9 Sep 2021 14:20:51 +0300
From:   Daniel Baluta <daniel.baluta@...il.com>
To:     Rob Herring <robh@...nel.org>
Cc:     Daniel Baluta <daniel.baluta@....nxp.com>,
        Mark Brown <broonie@...nel.org>,
        Pierre-Louis Bossart <pierre-louis.bossart@...ux.intel.com>,
        Liam Girdwood <lgirdwood@...il.com>,
        Ranjani Sridharan <ranjani.sridharan@...ux.intel.com>,
        Kai Vehmanen <kai.vehmanen@...ux.intel.com>,
        Devicetree List <devicetree@...r.kernel.org>,
        Shawn Guo <shawnguo@...nel.org>,
        Pengutronix Kernel Team <kernel@...gutronix.de>,
        Fabio Estevam <festevam@...il.com>,
        dl-linux-imx <linux-imx@....com>,
        Péter Ujfalusi <peter.ujfalusi@...ux.intel.com>,
        Linux-ALSA <alsa-devel@...a-project.org>,
        Linux Kernel Mailing List <linux-kernel@...r.kernel.org>,
        Suman Anna <s-anna@...com>,
        Daniel Baluta <daniel.baluta@....com>,
        Shengjiu Wang <shengjiu.wang@....com>
Subject: Re: [PATCH v2 2/2] dt-bindings: dsp: fsl: Add DSP optional clocks documentation

> > The H/W block is controlled by the DSP firmware. So, we don't want
> > to use the Linux kernel driver (thus the H/W block device tree node).
>
> 'status' is how you disable a device to not be used by the OS.
>
> The information about that device's resources are already in DT, we
> don't need to duplicate that here. If you want a list of devices
> assigned to the DSP here, that would be okay.

Thanks! This is a very good idea. I was thinking at a totally different thing.

So having something like this:

dsp {


hw-block-list = <&sai1>, <&sai2>;

}

And then inside the DSP driver we can get access to sai1 clocks. Do
you know of any standard property name?


>
> > The only thing that we cannot control from the DSP firmware are the clocks
> > hence we handle them in the DSP node.
> >
> > We moved the DAI clocks under the DSP node as I think you suggested here:
> >
> > https://www.lkml.org/lkml/2020/3/12/969
>
> No, that's certainly not what I was suggesting. The resources in the
> DSP node should be the h/w resources of the DSP itself.

I see thanks!