linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: u.kleine-koenig@pengutronix.de (Uwe Kleine-König)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/2] ARM: efm32: switch to properly namespaced location property
Date: Tue, 8 Jul 2014 20:26:20 +0200	[thread overview]
Message-ID: <20140708182620.GH7827@pengutronix.de> (raw)
In-Reply-To: <CAOesGMjJJPJr7GnB=aoydGqtoaTd8wdBYDD92S0+5-y1PJepsA@mail.gmail.com>

Hi Olof,

On Tue, Jul 08, 2014 at 09:06:13AM -0700, Olof Johansson wrote:
> I really don't want a hodge-podge of whatever someone felt like
> picking as a name at the time. It makes it really hard for newcomers
> to find a good best practices to follow, and over time will result in
> total chaos.
That's right. I did it in good faith. If you think it would be worth to
switch to say "energymicro,location" I think it wouldn't be that hard,
because I think there are no boards in the wild that use a device tree
and don't use the BSP I'm providing where switching is a no brainer.
> 
> What's this binding for anyway? It looks a lot like an ad-hoc pinctrl
> binding for configuring pinout, is that accurate?
Well, it has to do with pinctrl, but it was agreed that managing it with
a single pinctrl device would complicate things considerably and in the
end the device tree wouldn't describe how the hardware looks like but
would result in a lot of complexity just to fit into the Linux pinctrl
model.

See the thread around
http://marc.info/?l=linux-spi&m=137485291802157&w=2 for the glory
details.

Best regards
Uwe

-- 
Pengutronix e.K.                           | Uwe Kleine-K?nig            |
Industrial Linux Solutions                 | http://www.pengutronix.de/  |

  reply	other threads:[~2014-07-08 18:26 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-30 15:40 [GIT PULL] efm32 for 3.17-rc1 Uwe Kleine-König
2014-06-30 15:41 ` [PATCH 1/2] ARM: efm32: switch to properly namespaced location property Uwe Kleine-König
2014-07-08  5:46   ` Olof Johansson
2014-07-08  6:41     ` Uwe Kleine-König
2014-07-08 16:06       ` Olof Johansson
2014-07-08 18:26         ` Uwe Kleine-König [this message]
2014-07-10 22:05           ` Olof Johansson
2014-07-11  8:16             ` [PATCH] serial: efm32: correct namespacing of " Uwe Kleine-König
2014-07-11  8:17             ` [PATCH] spi: " Uwe Kleine-König
2014-07-11 12:39               ` Mark Brown
2014-07-11  8:22             ` [PATCH] i2c: " Uwe Kleine-König
2014-07-11  8:28               ` Uwe Kleine-König
2014-07-11  8:38                 ` Wolfram Sang
2014-07-11  8:50               ` [PATCH v2] " Uwe Kleine-König
2014-07-17 13:40                 ` Wolfram Sang
2014-07-17 18:42                   ` Uwe Kleine-König
2014-06-30 15:41 ` [PATCH 2/2] ARM: efm32: switch to vendor,device compatible strings Uwe Kleine-König
  -- strict thread matches above, loose matches on Subject: below --
2015-09-10  8:09 [PATCH 0/2] arm: efm32: dts updates Uwe Kleine-König
2015-09-10  8:09 ` [PATCH 1/2] ARM: efm32: switch to properly namespaced location property Uwe Kleine-König

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=20140708182620.GH7827@pengutronix.de \
    --to=u.kleine-koenig@pengutronix.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).