mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Arnd Bergmann <arnd@arndb.de>
To: guenter.roeck@ericsson.com
Cc: "Hans J. Koch" <hjk@hansjkoch.de>,
	"Greg Kroah-Hartman" <gregkh@suse.de>,
	Andrew Morton <akpm@linux-foundation.org>,
	Jonathan Cameron <kernel@jic23.retrosnub.co.uk>,
	Randy Dunlap <rdunlap@xenotime.net>,
	"linux-doc@vger.kernel.org" <linux-doc@vger.kernel.org>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2] misc: Driver for Silicon Labs Si570 and compatibles
Date: Tue, 26 Apr 2011 16:00:23 +0200	[thread overview]
Message-ID: <201104261600.23675.arnd@arndb.de> (raw)
In-Reply-To: <1303501213.31666.27.camel@groeck-laptop>

On Friday 22 April 2011, Guenter Roeck wrote:
> On Thu, 2011-04-21 at 19:34 -0400, Hans J. Koch wrote:
> > I don't think the UIO framework is the right place for such a thing. If it's
> > just this one driver that needs modification of a clock from userspace, then
> > a sysfs attribute could be added to that driver. If there are several drivers
> > that need this, then the clock framework should be extended.
> 
> Agreed. Also, the desire to control the clock frequency through such a
> driver (user mode or not) seems odd. Such an approach would be
> inherently non-scalable (for my part I would have to support two drivers
> already). Voltage regulators are not controlled through the drivers of
> the chips they are providing power to either, but have an independent
> existence.

I think you are talking about different things here. What I think
Hans was saying is that it should be in the specific UIO driver, not
in the framework, which I can agree with. If we get a bunch of these,
we can still make it generic at a later point, but that is not your
problem.

I think exporting the clock to kernel drivers as a struct clk is
the most useful approach to allow reuse, and then you just have to
interface to that from your existing UIO driver.

	Arnd

  reply	other threads:[~2011-04-26 14:01 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-19 21:36 Guenter Roeck
2011-04-20  9:23 ` Jonathan Cameron
2011-04-20 16:34   ` Guenter Roeck
2011-04-20 16:44 ` Arnd Bergmann
2011-04-20 18:16   ` Guenter Roeck
2011-04-21 11:11     ` Arnd Bergmann
2011-04-21 15:56       ` Guenter Roeck
2011-04-21 16:23         ` Arnd Bergmann
2011-04-21 18:47           ` Guenter Roeck
2011-04-21 19:00             ` Arnd Bergmann
2011-04-21 21:58               ` Guenter Roeck
2011-04-21 23:34       ` Hans J. Koch
2011-04-22 19:40         ` Guenter Roeck
2011-04-26 14:00           ` Arnd Bergmann [this message]
2011-04-26 15:33             ` Guenter Roeck
2011-04-22 12:53 Sid Boyce
2011-05-09 18:31 ` Guenter Roeck
2011-05-09 20:18   ` Sid Boyce

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=201104261600.23675.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=akpm@linux-foundation.org \
    --cc=gregkh@suse.de \
    --cc=guenter.roeck@ericsson.com \
    --cc=hjk@hansjkoch.de \
    --cc=kernel@jic23.retrosnub.co.uk \
    --cc=linux-doc@vger.kernel.org \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    /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

Powered by JetHome