From: dirk.behme@gmail.com (Dirk Behme)
To: linux-arm-kernel@lists.infradead.org
Subject: PCI support for IMX6
Date: Sat, 30 Mar 2013 13:12:14 +0100 [thread overview]
Message-ID: <5156D69E.3050600@gmail.com> (raw)
In-Reply-To: <20130330113703.GA21042@amd.pavel.ucw.cz>
Am 30.03.2013 12:37, schrieb Pavel Machek:
> Hi!
>
>> What is the state of PCI support for IMX6? I have board that has
>> e1000e connected via PCI, and I'd like to get network to work.
>>
>> I'm currently trying to port PCI support from 3.0, but it does not
>> look exactly easy.
>
> This is what I ended up with. Currently it is unable to turn on clock
> for PCI, thus it hangs. If someone has any ideas, let me know...
...
> +static void imx_pcie_enable_controller(struct device *dev)
> +{
> + struct clk *pcie_clk;
...
> +/* FIXME */
> +#define PCIE_CLK "pcie_ref"
> + /* enable the clks */
> + pcie_clk = clk_get(NULL, PCIE_CLK);
> + if (IS_ERR(pcie_clk)) {
> + pr_err("no pcie (?) clock.\n");
> + } else if (clk_enable(pcie_clk)) {
> + pr_err("can't enable pcie clock.\n");
> + clk_put(pcie_clk);
> + }
I'm not sure, Shawn might be the expert on this ;)
But have you tried using 'pcie_ref_125m'? And/or, as a test only, to
add pcie_ref and/or pcie_ref_125m to clks_init_on:
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/tree/arch/arm/mach-imx/clk-imx6q.c#n174
?
Best regards
Dirk
next prev parent reply other threads:[~2013-03-30 12:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-29 18:55 PCI support for IMX6 Pavel Machek
2013-03-30 11:37 ` Pavel Machek
2013-03-30 12:12 ` Dirk Behme [this message]
[not found] ` <20130331201614.GC25751@amd.pavel.ucw.cz>
2013-04-01 6:42 ` MicroSys sbc6x support (i.MX6) Shawn Guo
2013-04-01 7:43 ` Anatolij Gustschin
2013-04-01 7:47 ` Shawn Guo
[not found] ` <20130401122422.GA13982@amd.pavel.ucw.cz>
2013-04-01 12:51 ` ARM: dts: " Shawn Guo
2013-04-01 14:43 ` Pavel Machek
2013-03-30 15:52 ` PCI support for IMX6 Fabio Estevam
2013-03-31 18:33 ` Pavel Machek
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=5156D69E.3050600@gmail.com \
--to=dirk.behme@gmail.com \
--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).