public inbox for linux-omap@vger.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Enrico <ebutera@users.sourceforge.net>
Cc: linux-omap@vger.kernel.org, Russ Dill <Russ.Dill@ti.com>,
	Enric Balletbo i Serra <eballetbo@iseebcn.com>
Subject: Re: "smsc911x: Add fixed board regulators" problem
Date: Mon, 30 Apr 2012 09:11:55 -0700	[thread overview]
Message-ID: <20120430161155.GD3739@atomide.com> (raw)
In-Reply-To: <CA+2YH7tPBeJARm=ipq=HTtqNH6pDu8yQKMRMgL1Cz9rkSpzRBQ@mail.gmail.com>

Hi,

* Enrico <ebutera@users.sourceforge.net> [120430 08:02]:
> Hi,
> 
> hi get this at boot on an IGEP board (igep0020), latest linux-omap
> master (20 Apr):
> 
> [    0.047704] WARNING: at fs/sysfs/dir.c:508 sysfs_add_one+0x9c/0xac()
> [    0.047712] sysfs: cannot create duplicate filename
> '/devices/platform/reg-fixed-voltage.0'

This is because of trying to create multiple fixed regulators with
id 0 as discussed earlier. AFAIK there's still no clean way to deal
with that unfortunately..

Can you try changing the id to something random like below?

Regards,

Tony


--- a/arch/arm/mach-omap2/board-igep0020.c
+++ b/arch/arm/mach-omap2/board-igep0020.c
@@ -641,7 +641,7 @@ static struct regulator_consumer_supply dummy_supplies[] = {
 
 static void __init igep_init(void)
 {
-	regulator_register_fixed(0, dummy_supplies, ARRAY_SIZE(dummy_supplies));
+	regulator_register_fixed(42, dummy_supplies, ARRAY_SIZE(dummy_supplies));
 	omap3_mux_init(board_mux, OMAP_PACKAGE_CBB);
 
 	/* Get IGEP2 hardware revision */

  reply	other threads:[~2012-04-30 16:11 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-30 14:58 "smsc911x: Add fixed board regulators" problem Enrico
2012-04-30 16:11 ` Tony Lindgren [this message]
2012-04-30 16:39   ` Enrico

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=20120430161155.GD3739@atomide.com \
    --to=tony@atomide.com \
    --cc=Russ.Dill@ti.com \
    --cc=eballetbo@iseebcn.com \
    --cc=ebutera@users.sourceforge.net \
    --cc=linux-omap@vger.kernel.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