From: Anton Vorontsov <cbouatmailru-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: Grant Likely <grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org>
Cc: bgat-uPd5UNENI//N9NzbbXoYwQ@public.gmane.org,
dbaryshkov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org,
dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org,
khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org,
akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org
Subject: Re: [patch 1/6] gpiolib: introduce chip addition/removal notifier
Date: Sun, 2 May 2010 20:59:12 +0400 [thread overview]
Message-ID: <20100502165912.GA11300@oksana.dev.rtsoft.ru> (raw)
In-Reply-To: <n2yfa686aa41004302350i32d385e7gc00b49f39de417cb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
(Cc'ing devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org)
On Sat, May 01, 2010 at 12:50:15AM -0600, Grant Likely wrote:
> Not till now. Here's what I've been working on. It's based on my
> test-devicetree branch.
[...]
> As you can see, I've pretty much come full circle on the adding
> 'automatic' OF support to gpio chips. Originally (as you well know) I
> was strongly opposed to any addition of OF code to the core gpiolib.
> All of the notifier work was a response to that.
>
> However, now that I actually have played with the code and looked and
> the issues deeply, I've got an entirely different opinion.
ROFL :-D
> (The fact
> that OF support is being ported to more architectures is also a
> factor.)
Yeah, I guess without multi-arch OF effort such an OF+gpiolib
integration would be very dubious. But as OF spreads to other
architectures, and we already have of_node in the 'struct
device'... I guess that makes sense now.
> Anyway, please take a look.
It works here with some small fixes (patches on the way).
Tested with MCU (I2C), and QE GPIO (memory mapped) GPIO controllers.
Thanks!
--
Anton Vorontsov
email: cbouatmailru-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org
irc://irc.freenode.net/bd2
next parent reply other threads:[~2010-05-02 16:59 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <201004272111.o3RLBw1f020037@imap1.linux-foundation.org>
[not found] ` <1272428830.24542.72.camel@pasglop>
[not found] ` <20100430174240.GA29769@oksana.dev.rtsoft.ru>
[not found] ` <s2ifa686aa41004301043uca9bfbafz6db2402bfa233de4@mail.gmail.com>
[not found] ` <20100430174609.GA31455@oksana.dev.rtsoft.ru>
[not found] ` <n2yfa686aa41004302350i32d385e7gc00b49f39de417cb@mail.gmail.com>
[not found] ` <n2yfa686aa41004302350i32d385e7gc00b49f39de417cb-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-05-02 16:59 ` Anton Vorontsov [this message]
[not found] ` <20100502165912.GA11300-wnGakbxT3iijyJ0x5qLZdcN33GVbZNy3@public.gmane.org>
2010-05-02 17:00 ` [PATCH 1/3] powerpc/83xx/mcu: Add OF match table Anton Vorontsov
2010-05-02 17:00 ` [PATCH 2/3] serial/ucc_uart: Use .dev.of_node instead of .node in struct of_device Anton Vorontsov
2010-05-02 17:00 ` [PATCH 3/3] USB: FHCI: " Anton Vorontsov
2010-05-02 19:34 ` [patch 1/6] gpiolib: introduce chip addition/removal notifier 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=20100502165912.GA11300@oksana.dev.rtsoft.ru \
--to=cbouatmailru-re5jqeeqqe8avxtiumwx3w@public.gmane.org \
--cc=akpm-de/tnXTf+JLsfHDXvbKv3WD2FQJk+8+b@public.gmane.org \
--cc=bgat-uPd5UNENI//N9NzbbXoYwQ@public.gmane.org \
--cc=dbaryshkov-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=dbrownell-Rn4VEauK+AKRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
--cc=devicetree-discuss-uLR06cmDAlY/bJ5BZ2RsiQ@public.gmane.org \
--cc=grant.likely-s3s/WqlpOiPyB63q8FvJNQ@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.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 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.