From: Ben Gamari <bgamari.foss@gmail.com>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: linux-omap <linux-omap@vger.kernel.org>, spi-devel-general@lists.sf.net
Subject: Re: GPIO chip select support in McSPI
Date: Mon, 14 Mar 2011 22:22:31 -0400 [thread overview]
Message-ID: <877hc1t95k.fsf@gmail.com> (raw)
In-Reply-To: <20110314192536.GF16096@angua.secretlab.ca>
On Mon, 14 Mar 2011 13:25:36 -0600, Grant Likely <grant.likely@secretlab.ca> wrote:
> I see two solutions:
> 1) platform code registers a bus notifier so that it gets called back
> before the device gets bound to a driver. Then it can augment the
> platform data.
>
This sounds like it might be a bit involved and I'm not terribly
familiar with these facets of the driver model. This would probably be
the more flexible approach but I think I'll stick with the simpler
option.
> 2) add an api to arch/arm/mach-omap2/devices.c for providing a cs
> table before the device gets registered (must be called before
> arch_initcall() time).
>
This is along the lines of what I was thinking. Any thoughts on how to
get function called before arch_initcall()?
- Ben
next prev parent reply other threads:[~2011-03-15 2:22 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <c0ffcf4415b8edbf55d653a620b92fbbbcd8fed7>
[not found] ` <1297635034-24504-1-git-send-email-bgamari.foss@gmail.com>
[not found] ` <20110302215026.GA22854@angua.secretlab.ca>
[not found] ` <87sjv517yd.fsf@gmail.com>
[not found] ` <f7a269db-3bcf-4bac-8c38-b363e5c7bd0b@email.android.com>
2011-03-13 19:04 ` GPIO chip select support in McSPI Ben Gamari
2011-03-13 19:05 ` [PATCH] mcspi: Add support for GPIO chip select lines Ben Gamari
2011-03-14 19:27 ` Grant Likely
2011-03-15 2:06 ` Ben Gamari
2011-03-15 2:10 ` Grant Likely
2011-03-14 19:25 ` GPIO chip select support in McSPI Grant Likely
2011-03-15 2:22 ` Ben Gamari [this message]
2011-03-15 3:29 ` Grant Likely
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=877hc1t95k.fsf@gmail.com \
--to=bgamari.foss@gmail.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-omap@vger.kernel.org \
--cc=spi-devel-general@lists.sf.net \
/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).