From: One Thousand Gnomes <gnomes@lxorguk.ukuu.org.uk>
To: Mark Brown <broonie@kernel.org>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
Chew Chiau Ee <chiau.ee.chew@intel.com>,
Eric Miao <eric.y.miao@gmail.com>,
Russell King <linux@arm.linux.org.uk>,
Haojian Zhuang <haojian.zhuang@gmail.com>,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] spi/pxa2xx-pci: Pass host clock rate info from PCI glue layer
Date: Tue, 22 Apr 2014 15:27:23 +0100 [thread overview]
Message-ID: <20140422152723.7542a3bc@alan.etchedpixels.co.uk> (raw)
In-Reply-To: <20140422120948.GT12304@sirena.org.uk>
> Why is this conditional? It's really unhelpful for writing generic code
> handling clocks that the API isn't available as standard. Allowing the
> user to disable it if it's not required makes sense but not making it
> available at all is just unhelpful.
KConfig allows drivers to select features they need - this seems to be a
non issue ?
> As far as I can tell the clock here is part of the same glue that allows
> the generic pxa2xx support to be instantiated from PCI. I would
> therefore expect the glue to also instantiate the clock. Or if it's a
> standard PCI clock then perhaps the PCI subsystem ought to be providing
> it.
For most cases it probably makes sense to do something of that form,
although as clk_enable/clk_disable allow NULL it's much less of an issue
than it might otherwise be for some of the other drivers.
Alan
next prev parent reply other threads:[~2014-04-22 14:27 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-17 16:26 [PATCH 0/2] Add PCI mode support for BayTrail LPSS SPI Chew Chiau Ee
2014-04-17 16:26 ` [PATCH 1/2] spi/pxa2xx-pci: " Chew Chiau Ee
2014-04-18 17:06 ` Mark Brown
2014-04-17 16:26 ` [PATCH 2/2] spi/pxa2xx-pci: Pass host clock rate info from PCI glue layer Chew Chiau Ee
2014-04-18 16:30 ` Mark Brown
2014-04-22 11:57 ` Mika Westerberg
2014-04-22 12:09 ` Mark Brown
2014-04-22 12:37 ` Mika Westerberg
2014-04-22 14:27 ` One Thousand Gnomes [this message]
2014-04-22 18:21 ` Mark Brown
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=20140422152723.7542a3bc@alan.etchedpixels.co.uk \
--to=gnomes@lxorguk.ukuu.org.uk \
--cc=broonie@kernel.org \
--cc=chiau.ee.chew@intel.com \
--cc=eric.y.miao@gmail.com \
--cc=haojian.zhuang@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=mika.westerberg@linux.intel.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
all inboxes | Powered by JetHome®