From: Pavel Machek <pavel@suse.cz>
To: Richard Purdie <richard@openedhand.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Russell King <rmk@arm.linux.org.uk>, Greg KH <gregkh@suse.de>
Subject: Re: [RFC] The driver model, I2C and gpio provision on Sharp SL-C1000 (Akita)
Date: Sat, 29 Oct 2005 21:08:19 +0200 [thread overview]
Message-ID: <20051029190819.GB657@openzaurus.ucw.cz> (raw)
In-Reply-To: <1130493129.8414.70.camel@localhost.localdomain>
Hi!
> This code is the final link is getting akita working but I'm not sure
> its the right approach. I'm posting this in the hope someone might see a
> better way to achieve this driver's objectives. I'd like to get akita
> support into mainline and this is the only barrier.
Well, what you describe is not too nice, but I do not see nicer solutions :-(.
> I2C drivers appear relatively late in the boot procedure and changing
> that isn't practical. I therefore ended up writing akita-ioexp which
It seems that making i2c init early is only sane choice. I realize PC people
will hate it... but apart from that, why is it impractical?
> There is a fundamental problem with the lack of a proper gpio interface
> in Linux. Every driver does something different with them (be it pxa
> specific gpios, SCOOP gpios, those on a IO expander, those on a video
> chip (w100fb springs to mind) to name just the Zaurus specific ones.
Yup. GPIOs are not problem on i386, so noone solved this one :-(.
Pavel
--
64 bytes from 195.113.31.123: icmp_seq=28 ttl=51 time=448769.1 ms
next prev parent reply other threads:[~2005-10-30 12:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-10-28 9:52 [RFC] The driver model, I2C and gpio provision on Sharp SL-C1000 (Akita) Richard Purdie
2005-10-28 16:08 ` Russell King
2005-10-29 19:08 ` Pavel Machek [this message]
2005-11-02 19:44 ` Andy Isaacson
2005-11-02 22:52 ` Russell King
-- strict thread matches above, loose matches on Subject: below --
2005-11-03 7:06 David Brownell
2005-11-03 9:07 ` Richard Purdie
2005-11-03 15:38 ` David Brownell
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=20051029190819.GB657@openzaurus.ucw.cz \
--to=pavel@suse.cz \
--cc=gregkh@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=richard@openedhand.com \
--cc=rmk@arm.linux.org.uk \
/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.