From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-2.7 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS, URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id 5507FC433F5 for ; Thu, 9 Sep 2021 11:21:27 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 3641961100 for ; Thu, 9 Sep 2021 11:21:27 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S235303AbhIILWd (ORCPT ); Thu, 9 Sep 2021 07:22:33 -0400 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:59608 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S235121AbhIILWO (ORCPT ); Thu, 9 Sep 2021 07:22:14 -0400 Received: from mail-wr1-x433.google.com (mail-wr1-x433.google.com [IPv6:2a00:1450:4864:20::433]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id BE42EC061575; Thu, 9 Sep 2021 04:21:04 -0700 (PDT) Received: by mail-wr1-x433.google.com with SMTP id u16so2021987wrn.5; Thu, 09 Sep 2021 04:21:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20210112; h=mime-version:references:in-reply-to:from:date:message-id:subject:to :cc; bh=boyHz0uurKLDf0rs+5Mtb8FIKhFhQqkLeE6SMQCQ7Mw=; b=XnCBIstlrTZ42iymgvoBMiytRwCAZOvCGFqcobFEjL6BQGw42EonvQXM5RgMH9LTJ7 AYF9hLzT6IJOSg0HNMbCOr4NidieAAdYQyDATpCiOZ8aq9RLs4vJ0jIM7NdtcmqYLgmF CT7DnEwASSFwTDZ8t5c+SM9hH3SovzxrY8IhfdhBnlycryy+clKHd4XnIP1uEce5eYqL nNDBylJX6e+ass/kk2XEXn6HhL2W8vKn+zeqADxoRttdR32Mff3FzRko+qVD7wixQW2d l7ea+rb6xQ7n8p6VmUjo74NJqq/B4jTzOA+Qk5b7yicP/zHXg4bcLCO8GYmp1JBtiQtW JjTA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to:cc; bh=boyHz0uurKLDf0rs+5Mtb8FIKhFhQqkLeE6SMQCQ7Mw=; b=pVopGbQh8hBMV3VWTkiTW+m3e/pbcTUi28JPIfwkOzLmpvnR0hCuFuKzEFDe7i0ePq do81TM9QTtJPN0PEZV1OT8vVkv8Fn8D/GxU3YU8658u+Girznqomeu/Ujm85dclMahHZ EYtkjSXw9Gi2867d/hHdpDflrC8qLGAf8+9hp+d/xR2SvFW4zN8D8VWHbzmUs7foDZ46 LE4grIne9o0zHpMhj4J1vhy4TRnPeuKChZycJz3D2STf/pdbUuuHZbLAqk6aAuMD+/Wx 2r2qUAZd0LjEe8CewDRGCUp246nUJ929BwlNgpuE1afuvuFiLTwtMp0yzW4Nf3Ue/rup xn1A== X-Gm-Message-State: AOAM532Z6HCarrTNrj5htbLPkC/AgHy/1QF3v0SgFaMQ1g80ld6FvPoN Re2/jiPH+afQ51jr0jC0/4JLr6+NSb+77yHMR8s= X-Google-Smtp-Source: ABdhPJyWEp4sWX1UjZpYHyCBI2jXJGww22+s01hZJHFPIzOhSQ5OOQWblTaDxzYLJN7KUGOTHPIGmmBBAlGPubdqG9Y= X-Received: by 2002:adf:d20f:: with SMTP id j15mr2922294wrh.255.1631186463282; Thu, 09 Sep 2021 04:21:03 -0700 (PDT) MIME-Version: 1.0 References: <20210903145340.225511-1-daniel.baluta@oss.nxp.com> <20210903145340.225511-3-daniel.baluta@oss.nxp.com> In-Reply-To: From: Daniel Baluta Date: Thu, 9 Sep 2021 14:20:51 +0300 Message-ID: Subject: Re: [PATCH v2 2/2] dt-bindings: dsp: fsl: Add DSP optional clocks documentation To: Rob Herring Cc: Daniel Baluta , Mark Brown , Pierre-Louis Bossart , Liam Girdwood , Ranjani Sridharan , Kai Vehmanen , Devicetree List , Shawn Guo , Pengutronix Kernel Team , Fabio Estevam , dl-linux-imx , =?UTF-8?Q?P=C3=A9ter_Ujfalusi?= , Linux-ALSA , Linux Kernel Mailing List , Suman Anna , Daniel Baluta , Shengjiu Wang Content-Type: text/plain; charset="UTF-8" Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > > 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!