devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Shawn Guo <shawnguo@kernel.org>
To: Fabio Estevam <festevam@gmail.com>
Cc: "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
	<devicetree@vger.kernel.org>,
	jscheel@jusst.de, NXP Linux Team <linux-imx@nxp.com>,
	Fabio Estevam <fabio.estevam@nxp.com>,
	hohatzel@jusst.de,
	"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 4/4] ARM: dts: imx7d: sbc imx7: add uart5
Date: Tue, 11 Dec 2018 10:06:16 +0800	[thread overview]
Message-ID: <20181211020613.GR3987@dragon> (raw)
In-Reply-To: <CAOMZO5At5oSv0MCpsuYj4nEd26Y4h9hj-shadq3477fNz8A+HA@mail.gmail.com>

On Mon, Dec 10, 2018 at 09:43:12AM -0200, Fabio Estevam wrote:
> Hi Hans,
> 
> On Mon, Dec 10, 2018 at 8:52 AM Hans Ole Hatzel <hohatzel@jusst.de> wrote:
> 
> > imx7d-pico.dts does this the same way. Is that good enough of a reason?
> > If so, should it be included in the commit message?
> 
> The UART clock parent initialization has been removed from the imx7d
> clock driver since commit (in linux-next):
> 
> commit ea662d2f804ad13c3c92c75c7dc1abad30e31c31
> Author: Anson Huang <anson.huang@nxp.com>
> Date:   Fri Oct 19 01:05:36 2018 +0000
> 
>     clk: imx7d: remove UART1 clock setting
> 
>     There are clock assignments in all i.MX7D dtb files for UART1,
>     below is the example in imx7d-sdb.dts, so setting UART1 clock
>     in clock driver is NOT necessary, actually, module clocks setting
>     should be done in module driver.
> 
>     &uart1 {
>         pinctrl-names = "default";
>         pinctrl-0 = <&pinctrl_uart1>;
>         assigned-clocks = <&clks IMX7D_UART1_ROOT_SRC>;
>         assigned-clock-parents = <&clks IMX7D_PLL_SYS_MAIN_240M_CLK>;
>         status = "okay";
>     };
> 
>     Signed-off-by: Anson Huang <Anson.Huang@nxp.com>
>     Signed-off-by: Stephen Boyd <sboyd@kernel.org>
> 
> So the UART clock parent should be set in the device tree.

Okay, but would it be better to set the default parent clock in soc
level of dtsi, since the configuration doesn't seem to be board
specific?

Shawn

  reply	other threads:[~2018-12-11  2:06 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-12-04 11:07 [PATCH 0/4] imx7 sbc board support extensions Hans Ole Hatzel
2018-12-04 11:07 ` [PATCH 1/4] ARM: dts: imx7d: cl-som-imx7: fix pinctrl for i2c2 Hans Ole Hatzel
2018-12-04 11:07 ` [PATCH 2/4] ARM: dts: imx7d: cl-som-imx7: WiLink8 WLAN support Hans Ole Hatzel
2018-12-06  3:11   ` Shawn Guo
2018-12-04 11:07 ` [PATCH 3/4] ARM: dts: imx7d: sbc imx7: add uart2 Hans Ole Hatzel
2018-12-06  3:13   ` Shawn Guo
2018-12-04 11:07 ` [PATCH 4/4] ARM: dts: imx7d: sbc imx7: add uart5 Hans Ole Hatzel
2018-12-06  3:15   ` Shawn Guo
2018-12-10 10:51     ` Hans Ole Hatzel
2018-12-10 11:43       ` Fabio Estevam
2018-12-11  2:06         ` Shawn Guo [this message]
2018-12-11  2:35           ` Fabio Estevam
2018-12-06  3:01 ` [PATCH 0/4] imx7 sbc board support extensions Shawn Guo
2018-12-06  4:36 ` 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=20181211020613.GR3987@dragon \
    --to=shawnguo@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=fabio.estevam@nxp.com \
    --cc=festevam@gmail.com \
    --cc=hohatzel@jusst.de \
    --cc=jscheel@jusst.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-imx@nxp.com \
    /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).