devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	Rob Herring <robh@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
	Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
	Lucas Stach <l.stach@pengutronix.de>,
	NXP Linux Team <linux-imx@nxp.com>,
	Paul Elder <paul.elder@ideasonboard.com>,
	Peng Fan <peng.fan@nxp.com>,
	devicetree@vger.kernel.org
Subject: Re: [PATCH] dt-bindings: soc: imx8mp-media-blk-ctrl: Add LDB into DT example
Date: Fri, 8 Jul 2022 17:32:48 +0200	[thread overview]
Message-ID: <f0583d3e-eef1-7f97-9e06-e8dcd2859e9d@denx.de> (raw)
In-Reply-To: <eb8cede8-6493-c116-29eb-0303c1871239@linaro.org>

On 7/4/22 10:00, Krzysztof Kozlowski wrote:
> On 01/07/2022 10:06, Marek Vasut wrote:
>> In the local patch I have to imx8mp.dtsi , the simple-mfd had to be
>> added for the ldb bridge child node to bind.
>>
>>> 'simple-mfd' is saying the child has 0 dependence on the parent. IMO,
>>> 'syscon' contradicts that, but that's an all to common pattern. You are
>>> saying all the clocks (or any other resources) in the parent can be off
>>> and the LDB bridge is still functional.
>>
>> The bridge itself should work even if the block control is clocked off.
>> The block controller apb (register) clock have to be enabled only when
>> accessing these two LDB registers, which should be handled by runtime
>> PM. Or what am I missing here ?
> 
> If I understand correctly, you need the device's APB clocks to be
> enabled to use the child device? You have a dependency between child and
> parent, so it is not a simple-mfd.

OK, then ... what is it ? Some sort of hint would be helpful.

  reply	other threads:[~2022-07-08 15:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-30 17:39 [PATCH] dt-bindings: soc: imx8mp-media-blk-ctrl: Add LDB into DT example Marek Vasut
2022-06-30 19:11 ` Krzysztof Kozlowski
2022-06-30 19:16   ` Marek Vasut
2022-06-30 19:31     ` Krzysztof Kozlowski
2022-06-30 19:50       ` Marek Vasut
2022-07-01  0:09         ` Rob Herring
2022-07-01  8:06           ` Marek Vasut
2022-07-04  8:00             ` Krzysztof Kozlowski
2022-07-08 15:32               ` Marek Vasut [this message]
2022-07-11  9:22                 ` Krzysztof Kozlowski
2022-06-30 23:28 ` Rob Herring

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=f0583d3e-eef1-7f97-9e06-e8dcd2859e9d@denx.de \
    --to=marex@denx.de \
    --cc=devicetree@vger.kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=l.stach@pengutronix.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=paul.elder@ideasonboard.com \
    --cc=peng.fan@nxp.com \
    --cc=robh@kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).