From: Frank Li <frank.li@nxp.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"festevam@gmail.com" <festevam@gmail.com>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
dl-linux-imx <linux-imx@nxp.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>
Subject: RE: [EXT] Re: [PATCH v2 1/3] dt-bindings: usb: cdns-imx8qm: add imx8qm cdns3 glue bindings
Date: Mon, 20 Mar 2023 19:59:36 +0000 [thread overview]
Message-ID: <AM6PR04MB4838FC9492065F4DBCABE60D88809@AM6PR04MB4838.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <614fa099-e666-03da-1b11-29cc804bf847@linaro.org>
>
> The second is a good example - as you can see, there is a choice of
> values, so they are not exactly fixed.
>
> >
> > Such frequency information is necessary. We can put to dts or clock drivers.
> The clock driver
>
> If this is the argument, then the answer is NAK. Sorry, but DTS is not
> for offloading fixed stuff just because you do not want to work on
> drivers. The same for discoverable stuff.
>
> > Become bigger, or dts become bigger. I think the key point is if property to
> descript hardware information.
>
> You have to understand that with your binding you are not allowing to
> any changes of these frequencies.
Do you means it should be okay if one of clocks is not fixed?
Previous owner already left nxp. I double checked our documents and scfw source code.
I miss understood a clock SC_PM_CLK_MST_BUS, which actually mapped to IP's aclk, which
ware 100Mhz to 600Mhz.
>
> Best regards,
> Krzysztof
next prev parent reply other threads:[~2023-03-20 19:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-16 21:27 [PATCH v2 0/3] dts: imx8qxp add cdns usb3 port Frank Li
2023-03-16 21:27 ` [PATCH v2 1/3] dt-bindings: usb: cdns-imx8qm: add imx8qm cdns3 glue bindings Frank Li
2023-03-17 9:09 ` Krzysztof Kozlowski
2023-03-17 14:55 ` [EXT] " Frank Li
2023-03-19 11:13 ` Krzysztof Kozlowski
2023-03-20 14:49 ` Frank Li
2023-03-20 15:23 ` Krzysztof Kozlowski
2023-03-20 16:22 ` Frank Li
2023-03-20 16:27 ` Krzysztof Kozlowski
2023-03-20 17:02 ` Frank Li
2023-03-20 17:28 ` Krzysztof Kozlowski
2023-03-20 19:59 ` Frank Li [this message]
2023-03-21 6:37 ` Krzysztof Kozlowski
2023-03-16 21:27 ` [PATCH v2 2/3] arm64: dts: imx8qxp: add cadence usb3 support Frank Li
2023-03-17 6:39 ` Alexander Stein
2023-03-17 15:05 ` [EXT] " Frank Li
2023-03-16 21:27 ` [PATCH v2 3/3] arm64: dts: freescale: imx8qxp-mek: enable cadence usb3 Frank Li
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=AM6PR04MB4838FC9492065F4DBCABE60D88809@AM6PR04MB4838.eurprd04.prod.outlook.com \
--to=frank.li@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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).