linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: lee.jones@linaro.org (Lee Jones)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/1] mfd: Fix runtime warning caused by duplicate device registration
Date: Tue, 03 Jul 2012 14:07:45 +0100	[thread overview]
Message-ID: <4FF2EEA1.6080204@linaro.org> (raw)
In-Reply-To: <20120703123552.GC25995@sirena.org.uk>

On 03/07/12 13:35, Mark Brown wrote:
> On Tue, Jul 03, 2012 at 12:59:48PM +0100, Lee Jones wrote:
>> We register the ab8500 as an MFD device from db8500 code during Device Tree
>> boot in order to solve some limitations of DT. However, when Device Tree is
>> not enabled, we still want to allow platform code to register the ab8500 in
>> the normal way. Here we force MFD device registration of the ab8500 only
>> when booting with Device Tree enabled.
>>
>> Solves this issue:
>> WARNING: at fs/sysfs/dir.c:526 sysfs_add_one+0x88/0xb0()
>> sysfs: cannot create duplicate filename '/bus/platform/devices/ab8500-core.0'
>
> Do we really want to create MFD cells like this (which are really Linux
> internal things and might vary if another OS or another version of Linux
> changes its internal abstractions) from the device tree?

We're not creating them. We're merely using current infrastructure.

Before, when we probed each device from Device Tree we came up against 
some fairly major limitations of the Device Tree. As a result, Arnd and 
I agreed that this was the way to go.

See c5395e7ed8f16cc7bb72a783de68659db5aed515 for a short description of 
the troubles we faced.

-- 
Lee Jones
Linaro ST-Ericsson Landing Team Lead
M: +44 77 88 633 515
Linaro.org ? Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog

  reply	other threads:[~2012-07-03 13:07 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-03 11:59 [PATCH 1/1] mfd: Fix runtime warning caused by duplicate device registration Lee Jones
2012-07-03 12:35 ` Mark Brown
2012-07-03 13:07   ` Lee Jones [this message]
2012-07-03 13:24     ` Mark Brown
2012-07-03 13:48       ` Lee Jones
2012-07-03 14:21         ` Mark Brown
2012-07-05  7:36           ` Lee Jones
2012-07-05  9:45             ` Mark Brown
2012-07-05 11:46               ` Lee Jones
2012-07-05 12:06                 ` Mark Brown
2012-07-05 12:15                   ` Lee Jones
2012-07-05 12:29                     ` Mark Brown
2012-07-05 12:41                       ` Lee Jones
2012-07-05 12:45                         ` Mark Brown
2012-07-05 12:55                           ` Lee Jones
2012-07-05 13:03                             ` Mark Brown
2012-07-05 13:12                               ` Lee Jones
2012-07-05 13:20                                 ` Mark Brown
2012-07-05 13:54                                   ` Lee Jones
2012-07-05 13:57                                     ` Mark Brown
2012-07-05 14:06                                 ` Samuel Ortiz
2012-07-05 13:57                           ` Arnd Bergmann
2012-07-05 14:04                             ` Mark Brown
2012-07-05 14:06                             ` Lee Jones
2012-07-05 14:13                               ` Mark Brown
2012-07-05 14:35                                 ` Lee Jones
2012-07-05 15:41                                   ` Arnd Bergmann
2012-07-05 15:51                                     ` Lee Jones
2012-07-03 14:01       ` Arnd Bergmann
2012-07-03 14:43         ` Mark Brown
2012-07-05  7:33 ` Lee Jones
2012-07-05 13:08 ` Fabio Estevam
2012-07-05 13:13   ` Lee Jones

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=4FF2EEA1.6080204@linaro.org \
    --to=lee.jones@linaro.org \
    --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).