All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Igor Grinberg <grinberg@compulab.co.il>
Cc: Paul Gortmaker <paul.gortmaker@windriver.com>,
	haojian.zhuang@gmail.com, linux-arm-kernel@lists.infradead.org,
	linux-next@vger.kernel.org
Subject: Re: [PATCH] ARM: pxa: fix build failure for regulator consumer in em-x270.c
Date: Thu, 29 Mar 2012 15:54:37 +0100	[thread overview]
Message-ID: <20120329145436.GS3668@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4F7471A0.6070208@compulab.co.il>

[-- Attachment #1: Type: text/plain, Size: 1174 bytes --]

On Thu, Mar 29, 2012 at 04:28:48PM +0200, Igor Grinberg wrote:
> On 03/28/12 18:59, Paul Gortmaker wrote:

> >>> static struct platform_device em_x270_gps_userspace_consumer = {
> >>>         .name           = "reg-userspace-consumer",
> >>>         .id             = 0,

> >>> static struct platform_device em_x270_gprs_userspace_consumer = {
> >>>         .name           = "reg-userspace-consumer",
> >>>         .id             = 1,

> > -REGULATOR_CONSUMER(ldo19, "reg-userspace-consumer", "vcc gprs");
> > +REGULATOR_CONSUMER(ldo19, "reg-userspace-consumer.1", "vcc gprs");

> Well, I thought of this solution, but I don't like it, as it makes
> the whole thing very fragile and sensitive to the reg-userspace-consumer
> platform device registration order and count, isn't it?
> (That's why I proposed to use NULL...).

No the platform device numbering should be totally stable for a given
board unless someone deliberately sets out to renumber them - the .ids
are explicitly assigned by the board when it registers the device.

> So, Mark, how do you think the above issues can be handled without
> putting NULL into the dev_name?

It shouldn't be a problem I think.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: pxa: fix build failure for regulator consumer in em-x270.c
Date: Thu, 29 Mar 2012 15:54:37 +0100	[thread overview]
Message-ID: <20120329145436.GS3668@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4F7471A0.6070208@compulab.co.il>

On Thu, Mar 29, 2012 at 04:28:48PM +0200, Igor Grinberg wrote:
> On 03/28/12 18:59, Paul Gortmaker wrote:

> >>> static struct platform_device em_x270_gps_userspace_consumer = {
> >>>         .name           = "reg-userspace-consumer",
> >>>         .id             = 0,

> >>> static struct platform_device em_x270_gprs_userspace_consumer = {
> >>>         .name           = "reg-userspace-consumer",
> >>>         .id             = 1,

> > -REGULATOR_CONSUMER(ldo19, "reg-userspace-consumer", "vcc gprs");
> > +REGULATOR_CONSUMER(ldo19, "reg-userspace-consumer.1", "vcc gprs");

> Well, I thought of this solution, but I don't like it, as it makes
> the whole thing very fragile and sensitive to the reg-userspace-consumer
> platform device registration order and count, isn't it?
> (That's why I proposed to use NULL...).

No the platform device numbering should be totally stable for a given
board unless someone deliberately sets out to renumber them - the .ids
are explicitly assigned by the board when it registers the device.

> So, Mark, how do you think the above issues can be handled without
> putting NULL into the dev_name?

It shouldn't be a problem I think.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20120329/c6b5b0e9/attachment.sig>

  reply	other threads:[~2012-03-29 14:54 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-03-05 23:12 [PATCH] ARM: pxa: fix build failure for regulator consumer in em-x270.c Paul Gortmaker
2012-03-05 23:12 ` Paul Gortmaker
2012-03-06  8:46 ` Igor Grinberg
2012-03-06  8:46   ` Igor Grinberg
2012-03-06  9:12   ` Haojian Zhuang
2012-03-06  9:12     ` Haojian Zhuang
2012-03-06 12:16     ` Mark Brown
2012-03-06 12:16       ` Mark Brown
2012-03-06 12:22       ` Haojian Zhuang
2012-03-06 12:22         ` Haojian Zhuang
2012-03-07  0:10 ` Paul Gortmaker
2012-03-07  0:10   ` Paul Gortmaker
2012-03-08 22:06   ` Paul Gortmaker
2012-03-08 22:06     ` Paul Gortmaker
2012-03-28 15:21     ` Igor Grinberg
2012-03-28 15:21       ` Igor Grinberg
2012-03-28 15:27       ` Mark Brown
2012-03-28 15:27         ` Mark Brown
2012-03-28 15:37         ` Haojian Zhuang
2012-03-28 15:37           ` Haojian Zhuang
2012-03-28 15:39           ` Mark Brown
2012-03-28 15:39             ` Mark Brown
2012-03-28 15:59         ` Paul Gortmaker
2012-03-28 15:59           ` Paul Gortmaker
2012-03-28 16:13           ` Mark Brown
2012-03-28 16:13             ` Mark Brown
2012-03-28 16:59             ` Paul Gortmaker
2012-03-28 16:59               ` Paul Gortmaker
2012-03-29 14:28               ` Igor Grinberg
2012-03-29 14:28                 ` Igor Grinberg
2012-03-29 14:54                 ` Mark Brown [this message]
2012-03-29 14:54                   ` Mark Brown
2012-03-29 14:57                   ` Paul Gortmaker
2012-03-29 14:57                     ` Paul Gortmaker
2012-03-29 15:11                     ` Mark Brown
2012-03-29 15:11                       ` Mark Brown
2012-03-29 17:43                       ` [PATCH v3] " Paul Gortmaker
2012-03-30  0:41                         ` Haojian Zhuang
2012-03-30 12:24                         ` Igor Grinberg
2012-03-29 14:55                 ` [PATCH] " Paul Gortmaker
2012-03-29 14:55                   ` Paul Gortmaker
2012-03-30 11:25                   ` Igor Grinberg
2012-03-30 11:25                     ` Igor Grinberg

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=20120329145436.GS3668@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=grinberg@compulab.co.il \
    --cc=haojian.zhuang@gmail.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-next@vger.kernel.org \
    --cc=paul.gortmaker@windriver.com \
    /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.