public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: tony@atomide•com (Tony Lindgren)
To: linux-arm-kernel@lists•infradead.org
Subject: Getting your opinion about the best place to put one specific device driver...
Date: Thu, 14 Feb 2013 08:59:04 -0800	[thread overview]
Message-ID: <20130214165903.GA7144@atomide.com> (raw)
In-Reply-To: <CACRpkdbGLoXY=g_pkF42FZgH+8yRUnKafvMmab_gwqDhYpE69A@mail.gmail.com>

* Linus Walleij <linus.walleij@linaro•org> [130214 00:56]:
> 
> The hardware observer already use the pinctrl interfaces from
> pinctrl-nomadik.c to set up the pins per se: i.e. to set up so
> that these pins are available to put signals on. But then we
> can plug this stuff as a front-end, and yeah.
> drivers/pinctrl/ux500-hwobs.c might be a good idea!

Just please try to keep the data added to kernel to minimum..

The user space app can decipher what each register means
based on the register address + SoC model. Kernel just needs
to be able to route the signals.

Otherwise we'll end up with data for each SoC in the kernel,
which we're trying to avoid :)

Regards,

Tony

  reply	other threads:[~2013-02-14 16:59 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 [this message]
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=20130214165903.GA7144@atomide.com \
    --to=tony@atomide$(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