All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Hongxing Zhu <hongxing.zhu@nxp.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Cc: Alexander Stein <alexander.stein@ew.tq-group.com>,
	Fabio Estevam <festevam@denx.de>, Peng Fan <peng.fan@nxp.com>,
	Shawn Guo <shawnguo@kernel.org>, dl-linux-imx <linux-imx@nxp.com>
Subject: Re: [PATCH v3 2/2] arm64: dts: imx8mq: Deduplicate PCIe clock-names property
Date: Tue, 17 Jan 2023 13:31:33 +0100	[thread overview]
Message-ID: <d4183d30-61e6-6168-c4be-830371411bf2@denx.de> (raw)
In-Reply-To: <AS8PR04MB8676943FC303D65C0A1B47C08CC69@AS8PR04MB8676.eurprd04.prod.outlook.com>

On 1/17/23 05:00, Hongxing Zhu wrote:

Hi,

[...]

>> diff --git a/arch/arm64/boot/dts/freescale/imx8mq.dtsi
>> b/arch/arm64/boot/dts/freescale/imx8mq.dtsi
>> index faed28e3ffa17..98fbba4c99a99 100644
>> --- a/arch/arm64/boot/dts/freescale/imx8mq.dtsi
>> +++ b/arch/arm64/boot/dts/freescale/imx8mq.dtsi
>> @@ -1542,6 +1542,11 @@ pcie0: pcie@33800000 {
>>   			                <0 0 0 4 &gic GIC_SPI 122
>> IRQ_TYPE_LEVEL_HIGH>;
>>   			fsl,max-link-speed = <2>;
>>   			linux,pci-domain = <0>;
>> +			clocks = <&clk IMX8MQ_CLK_PCIE1_ROOT>,
>> +				 <&clk IMX8MQ_CLK_PCIE1_PHY>,
>> +				 <&clk IMX8MQ_CLK_PCIE1_PHY>,
> Why there are two PHY clocks?
> Do you want to define IMX8MQ_CLK_PCIE1_PHY clock as "pcie_bus" clock here,
>   and then change "pcie_bus" clock to "pcie0_refclk" in the evk board dts later?

Yes

> How about to set the "pcie_bus" clock as " pcie#_refclk " directly in i.MX8MQ
>   dtsi file?
> Thus, it can avoid more duplicated codes in boards dts files further.

I can do that, but is that really the right approach ?

Consider a board which supplies 'pcie_bus' from some I2C PCIe clock 
generator, such board would now have a useless /pcie#-clock {} node in 
DT , right ?

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

  reply	other threads:[~2023-01-17 12:32 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-16 10:14 [PATCH v3 1/2] arm64: dts: imx8mm: Deduplicate PCIe clock-names property Marek Vasut
2023-01-16 10:14 ` [PATCH v3 2/2] arm64: dts: imx8mq: " Marek Vasut
2023-01-17  4:00   ` Hongxing Zhu
2023-01-17 12:31     ` Marek Vasut [this message]
2023-01-18  1:48       ` Hongxing Zhu
2023-01-17  3:35 ` [PATCH v3 1/2] arm64: dts: imx8mm: " Hongxing Zhu
2023-01-26  6:50 ` Shawn Guo

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=d4183d30-61e6-6168-c4be-830371411bf2@denx.de \
    --to=marex@denx.de \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=festevam@denx.de \
    --cc=hongxing.zhu@nxp.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    --cc=peng.fan@nxp.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.