linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Marek Vasut <marex@denx.de>, 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: Mon, 11 Jul 2022 11:22:02 +0200	[thread overview]
Message-ID: <c9f769f5-4428-a26c-660e-d250f8c5643a@linaro.org> (raw)
In-Reply-To: <f0583d3e-eef1-7f97-9e06-e8dcd2859e9d@denx.de>

On 08/07/2022 17:32, Marek Vasut wrote:
> 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.

I don't have the hardware manual to know what is it exactly. Some device
which has its own bindings and fsl,imx8mp-media-blk-ctrl compatible.

You already received hint what should you do with that device....
"What I meant, is that probably you should populate children from the
driver instead of adding simple-mfd compatible."


Best regards,
Krzysztof

_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  reply	other threads:[~2022-07-11  9:23 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
2022-07-11  9:22                 ` Krzysztof Kozlowski [this message]
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=c9f769f5-4428-a26c-660e-d250f8c5643a@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=devicetree@vger.kernel.org \
    --cc=l.stach@pengutronix.de \
    --cc=laurent.pinchart@ideasonboard.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=marex@denx.de \
    --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).