All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anton Vorontsov <cbouatmailru@gmail.com>
To: Scott Wood <scottwood@freescale.com>
Cc: patches@linaro.org, devicetree-discuss@lists.ozlabs.org,
	linux-mmc@vger.kernel.org,
	Grant Likely <grant.likely@secretlab.ca>,
	Chris Ball <cjb@laptop.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v3 4/4] mmc: sdhci-esdhc-imx: add device tree probe support
Date: Wed, 13 Jul 2011 20:28:12 +0400	[thread overview]
Message-ID: <20110713162812.GA7764@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <20110713110940.460a7966@schlenkerla.am.freescale.net>

On Wed, Jul 13, 2011 at 11:09:40AM -0500, Scott Wood wrote:
[...]
> > - You can't automatically convert named resources into 'struct
> >   resource *', as we do for platform devices now;
> 
> So add named resource support to platform devices. :-)

There are surely no technical difficulties, it's more about 'type
safety', and as a consequence -- resources being discoverable.

If we want to use named resources, I think we should explicitly reserve
the *-{regs,interrupts,gpios} suffixes for such purposes. And once such
a reservation is done, we're safe again -- resources become discoverable.

Thanks,

-- 
Anton Vorontsov
Email: cbouatmailru@gmail.com

WARNING: multiple messages have this Message-ID (diff)
From: cbouatmailru@gmail.com (Anton Vorontsov)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v3 4/4] mmc: sdhci-esdhc-imx: add device tree probe support
Date: Wed, 13 Jul 2011 20:28:12 +0400	[thread overview]
Message-ID: <20110713162812.GA7764@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <20110713110940.460a7966@schlenkerla.am.freescale.net>

On Wed, Jul 13, 2011 at 11:09:40AM -0500, Scott Wood wrote:
[...]
> > - You can't automatically convert named resources into 'struct
> >   resource *', as we do for platform devices now;
> 
> So add named resource support to platform devices. :-)

There are surely no technical difficulties, it's more about 'type
safety', and as a consequence -- resources being discoverable.

If we want to use named resources, I think we should explicitly reserve
the *-{regs,interrupts,gpios} suffixes for such purposes. And once such
a reservation is done, we're safe again -- resources become discoverable.

Thanks,

-- 
Anton Vorontsov
Email: cbouatmailru at gmail.com

  reply	other threads:[~2011-07-13 16:28 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-06 16:47 [PATCH v3 0/4] Add device tree probe for sdhci-esdhc-imx Shawn Guo
2011-07-06 16:47 ` Shawn Guo
2011-07-06 16:47 ` [PATCH v3 1/4] mmc: sdhci-esdhc-imx: do not reference platform data after probe Shawn Guo
2011-07-06 16:47   ` Shawn Guo
2011-07-06 21:03   ` Grant Likely
2011-07-06 21:03     ` Grant Likely
2011-07-06 16:47 ` [PATCH v3 2/4] mmc: sdhci-esdhc-imx: get rid of the uses of cpu_is_mx() Shawn Guo
2011-07-06 16:47   ` Shawn Guo
2011-07-06 16:47 ` [PATCH v3 3/4] mmc: sdhci-pltfm: dt device does not pass parent to sdhci_alloc_host Shawn Guo
2011-07-06 16:47   ` Shawn Guo
2011-07-06 16:47 ` [PATCH v3 4/4] mmc: sdhci-esdhc-imx: add device tree probe support Shawn Guo
2011-07-06 16:47   ` Shawn Guo
2011-07-06 21:05   ` Grant Likely
2011-07-06 21:05     ` Grant Likely
2011-07-13 15:52     ` Anton Vorontsov
2011-07-13 15:52       ` Anton Vorontsov
2011-07-13 16:09       ` Scott Wood
2011-07-13 16:09         ` Scott Wood
2011-07-13 16:28         ` Anton Vorontsov [this message]
2011-07-13 16:28           ` Anton Vorontsov
2011-07-13 16:36       ` Grant Likely
2011-07-13 16:36         ` Grant Likely
2011-07-13 17:32         ` Anton Vorontsov
2011-07-13 17:32           ` Anton Vorontsov
2011-07-09 22:14 ` [PATCH v3 0/4] Add device tree probe for sdhci-esdhc-imx Chris Ball
2011-07-09 22:14   ` Chris Ball
2011-07-10  1:37   ` Shawn Guo
2011-07-10  1:37     ` Shawn Guo
2011-07-19  1:51     ` Chris Ball
2011-07-19  1:51       ` Chris Ball
2011-07-19  8:10       ` Sascha Hauer
2011-07-19  8:10         ` Sascha Hauer
2011-07-19  8:59         ` Shawn Guo
2011-07-19  8:59           ` Shawn Guo

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=20110713162812.GA7764@oksana.dev.rtsoft.ru \
    --to=cbouatmailru@gmail.com \
    --cc=cjb@laptop.org \
    --cc=devicetree-discuss@lists.ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=patches@linaro.org \
    --cc=scottwood@freescale.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.