From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: Tegra board file deprecation schedule
Date: Sat, 28 Apr 2012 22:34:56 +0100 [thread overview]
Message-ID: <20120428213456.GD27792@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <6014194.Op4vnW6Cge@ax5200p>
On Sat, Apr 28, 2012 at 06:09:32PM +0200, Marc Dietrich wrote:
> Another (maybe a bit off-topic) thing that puzzels me is the how to assign
> the clock to the nvec.
What's the nvec?
> The device needs the clock (tegra-i2c.2) but there is no sane way to get
> it. I was thinking to add an device name alias (nvec = tegra-i2c.2) to
> the board file so I can use clk_get(&pdev->dev, NULL) instead of
> clk_get_sys which seems to be unwanted.
clk_get() is preferred in drivers which have struct device's to get them.
And if you know the device name, then I see no problem with the aliasing
approach.
next prev parent reply other threads:[~2012-04-28 21:34 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-27 21:24 Tegra board file deprecation schedule Stephen Warren
2012-04-27 21:39 ` Olof Johansson
2012-04-27 21:53 ` Stephen Warren
2012-04-27 22:00 ` Fabio Estevam
2012-04-27 22:20 ` Stephen Warren
2012-04-28 16:09 ` Marc Dietrich
2012-04-28 21:34 ` Russell King - ARM Linux [this message]
2012-04-29 18:11 ` Marc Dietrich
2012-04-29 18:56 ` Russell King - ARM Linux
2012-04-29 19:16 ` Stephen Warren
2012-04-30 8:58 ` Marc Dietrich
2012-04-30 15:58 ` Stephen Warren
2012-04-30 16:51 ` Marc Dietrich
2012-04-29 19:21 ` Stephen Warren
2012-04-30 9:00 ` Marc Dietrich
2012-04-28 21:26 ` Lucas Stach
2012-04-29 19:25 ` Stephen Warren
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=20120428213456.GD27792@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).