From: swarren@wwwdotorg.org (Stephen Warren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] ARM: tegra: add clocks properties to USB PHY nodes
Date: Tue, 22 Jan 2013 17:33:20 -0700 [thread overview]
Message-ID: <50FF2FD0.2090003@wwwdotorg.org> (raw)
In-Reply-To: <1358900903-27654-2-git-send-email-swarren@wwwdotorg.org>
On 01/22/2013 05:28 PM, Stephen Warren wrote:
> The patch to add USB PHY nodes to device tree was written before Tegra
> supported the clocks property in device tree. Now that it does, add the
> required clocks properties to these nodes.
>
> This will allow all clk_get_sys() calls in tegra_usb_phy.c to be replaced
> by clk_get(phy->dev, clock_name), as part of converting the PHY driver to
> a platform driver.
> diff --git a/arch/arm/boot/dts/tegra20.dtsi b/arch/arm/boot/dts/tegra20.dtsi
> + clocks = <&tegra_car 22>, <&tegra_car 127>;
> + clock-names = "utmi", "pll_u";
...
> + clocks = <&tegra_car 94>, <&tegra_car 127>;
> + clock-names = "ulpi", "pll_u";
Hmmm. Thinking about that first clock more, if we name it just "phy" in
both the UTMI and ULPI PHY nodes, we could make tegra_phy_init() perform
the clk_get() for all PHY types, and use the same clock name everywhere,
and hence remove the type-specific clk_get()s from tegra_phy_init() and
utmip_pad_open().
Venu, will this work for other chips such as Tegra30/Tegra114 and so on
into the future, or do chips after Tegra20 introduce any new clocks, and
hence break this scheme?
next prev parent reply other threads:[~2013-01-23 0:33 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 0:28 [PATCH 1/2] usb: host: tegra: don't touch EMC clock Stephen Warren
2013-01-23 0:28 ` [PATCH 2/2] ARM: tegra: add clocks properties to USB PHY nodes Stephen Warren
2013-01-23 0:33 ` Stephen Warren [this message]
2013-01-23 6:43 ` Venu Byravarasu
2013-01-23 16:33 ` Stephen Warren
2013-01-23 1:06 ` [PATCH 1/2] usb: host: tegra: don't touch EMC clock Greg Kroah-Hartman
2013-01-23 6:55 ` Venu Byravarasu
2013-01-23 9:45 ` Lucas Stach
2013-01-23 16:17 ` Stephen Warren
2013-01-23 15:23 ` Alan Stern
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=50FF2FD0.2090003@wwwdotorg.org \
--to=swarren@wwwdotorg.org \
--cc=linux-arm-kernel@lists.infradead.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).