From: jean-nicolas.graux@stericsson•com (Jean-Nicolas GRAUX)
To: linux-arm-kernel@lists•infradead.org
Subject: Getting your opinion about the best place to put one specific device driver...
Date: Wed, 13 Feb 2013 10:47:44 +0100 [thread overview]
Message-ID: <511B6140.90801@stericsson.com> (raw)
In-Reply-To: <20130213094552.GD3073@tbergstrom-lnx.Nvidia.com>
Le 02/13/2013 10:45 AM, Peter De Schrijver a ?crit :
>> Correct, I try my best to avoid adding random stuff in there that might
>> need a generic interface later. Tony already pointed out the similarity
>> to the OMAP specific hwopbs feature, and whatever user interface we
>> introduce for one should be generic enough to work on the other one as
>> well, and ideally also on future ones to the degree that we can anticipate
>> them today.
>>
>> I like the idea of making the in-kernel configuration part of this a
>> pinctrl driver, which would already allow you to configure it through
>> a custom device tree and no user interface at all.
>>
> Having done significant work with the OMAP3 hwobs feature, you really want a
> userinterface. At least OMAP3 has limitations on which signal can be
> monitored on which hwobs pin. This means that depending on the measurements
> you want to do, you need to change the configuration. If you want to automate
> several measurements, having a user interface (eg using debugfs), makes things
> much easier. Also when using this for debugging, you probably will have to
> experiment with which signals to monitor to rootcause the problem. Also then
> having a userinterface will be much easier than modifying the devicetree
> and rebooting the system.
>
> Cheers,
>
> Peter.
>
Yep, that's true.
next prev parent reply other threads:[~2013-02-13 9:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-12 9:44 Getting your opinion about the best place to put one specific device driver Jean-Nicolas GRAUX
2013-02-12 14:54 ` Arnd Bergmann
2013-02-12 16:26 ` Jean-Nicolas GRAUX
2013-02-12 16:57 ` Tony Lindgren
2013-02-12 17:41 ` Arnd Bergmann
2013-02-13 9:16 ` Jean-Nicolas GRAUX
2013-02-13 11:04 ` Arnd Bergmann
2013-02-13 16:54 ` Tony Lindgren
2013-02-14 10:28 ` Peter De Schrijver
2013-02-14 8:52 ` Linus Walleij
2013-02-14 16:59 ` Tony Lindgren
2013-02-13 9:45 ` Peter De Schrijver
2013-02-13 9:47 ` Jean-Nicolas GRAUX [this message]
2013-02-13 16:52 ` Tony Lindgren
2013-02-12 15:09 ` Russell King - ARM Linux
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=511B6140.90801@stericsson.com \
--to=jean-nicolas.graux@stericsson$(echo .)com \
--cc=linux-arm-kernel@lists$(echo .)infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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