From: Sascha Hauer <s.hauer@pengutronix.de>
To: Sean Cross <xobs@kosagi.com>
Cc: devicetree@vger.kernel.org, linux-pci@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Shawn Guo <shawn.guo@linaro.org>
Subject: Re: [PATCH v3 3/3] PCI: imx6: Add support for i.MX6 PCIe controller
Date: Thu, 12 Sep 2013 12:41:26 +0200 [thread overview]
Message-ID: <20130912104126.GS30088@pengutronix.de> (raw)
In-Reply-To: <65E0D2C79B2B43D28CC77454F44ECCFA@kosagi.com>
On Thu, Sep 12, 2013 at 03:11:45PM +0800, Sean Cross wrote:
> > Even if it should be configurable I'm still unsure whether this should
> > be done at pci driver level.
>
> I'm a bit wary of including clock setup like this in the SoC code, as
> different boards might be different. If a board designer wants to run
> LVDS2 to the PCIe slot, that's entirely acceptable. It might not
> actually ever get done, but it seems like the sort of board-specific
> thing that device tree was designed to handle.
The devicetree was designed to handle hardware descriptions, not
configuration options.
Chosing the clock parent is probably in the grey area between hardware
description and configuration, so I assume when we find a good reason to
add this option to the devicetree then it's acceptable to add it there.
But we shouldn't add this option for something that, as you say, 'might
not actually ever get done'. Just hardcode the clock selection in SoC
code for now. If someone ever finds the good reason to make this configurable
then he will speak up and we can discuss this again.
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
next prev parent reply other threads:[~2013-09-12 10:41 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-12 4:03 [PATCH v3 0/3] Add PCIe support for i.MX6q Sean Cross
2013-09-12 4:03 ` [PATCH v3 1/3] ARM: imx: Add LVDS general-purpose clocks to i.MX6Q Sean Cross
2013-09-12 4:03 ` [PATCH v3 2/3] ARM: imx6q: Add PCIe bits to GPR syscon definition Sean Cross
2013-09-12 4:03 ` [PATCH v3 3/3] PCI: imx6: Add support for i.MX6 PCIe controller Sean Cross
2013-09-12 6:28 ` Sascha Hauer
2013-09-12 6:44 ` Sean Cross
2013-09-12 7:01 ` Sascha Hauer
2013-09-12 7:11 ` Sean Cross
2013-09-12 10:41 ` Sascha Hauer [this message]
2013-09-12 6:35 ` Zhu Richard-R65037
2013-09-12 6:55 ` Sean Cross
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=20130912104126.GS30088@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pci@vger.kernel.org \
--cc=shawn.guo@linaro.org \
--cc=xobs@kosagi.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).