From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Getting your opinion about the best place to put one specific device driver...
Date: Tue, 12 Feb 2013 14:54:10 +0000 [thread overview]
Message-ID: <201302121454.10231.arnd@arndb.de> (raw)
In-Reply-To: <511A0F11.1050608@stericsson.com>
On Tuesday 12 February 2013, Jean-Nicolas GRAUX wrote:
> ello, Arnd, Olof. First, let me introduce myself quickly.
> I am working in Stericsson and i am a colleague of Linus Walleij.
> We are currently doing some cleaning in our mach-ux500 ARM machine.
>
> Among other things, the U8500 SoC and its derivatives embed one small IP
> called the "hardware observer".
> This is used for hardware debug purpose and it provides the ability to
> output some
> modem, power, clocking, ..., hardware signals on 18 external wires.
>
> We did one small platform device driver to handle this piece of hardware.
> In the patch attached to this file, we kept the code in the mach-ux500
> machine folder.
> But we are wondering where is the best place to put that stuff.
> So, the question is: where should we put this code in the kernel tree ?
Hi Jean-Nicolas,
I think I need some more information to understand what that interface
you are driving is actually about, since that is not clear from your
description or from reading the source code.
Why are there exactly 18 wires?
What is the protocol that is used on these wires (i2c, spi, rs232, ...)
Why do you actually need run-time configuration in the kernel?
It does look however like this code is related to the PRCMU, so maybe
it should be part of the prcmu driver rather than a separate device?
Arnd
next prev parent reply other threads:[~2013-02-12 14:54 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 [this message]
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
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=201302121454.10231.arnd@arndb.de \
--to=arnd@arndb.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.