From: Alessandro Zummo <alessandro.zummo@towertech.it>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: Jean Delvare <khali@linux-fr.org>,
Wolfram Sang <w.sang@pengutronix.de>,
Juergen Beisert <j.beisert@pengutronix.de>,
Andrew Morton <akpm@linux-foundation.org>,
Ben Dooks <ben-linux-arm@fluff.org>,
linux-kernel@vger.kernel.org
Subject: Re: Fwd: PCF8583 not detected on RiscPC
Date: Sun, 22 Feb 2009 10:42:05 +0100 [thread overview]
Message-ID: <20090222104205.4539d3ef@i1501.lan.towertech.it> (raw)
In-Reply-To: <20090222082829.GG16596@n2100.arm.linux.org.uk>
On Sun, 22 Feb 2009 08:28:29 +0000
Russell King - ARM Linux <linux@arm.linux.org.uk> wrote:
> So, really, I'm not listening to NACKs from anyone for this. The only
> thing I'll listen to is something _constructive_ to make it work again.
> I'm sure Andrew Morton will back me up on this.
You never listened to anyone, as far as I can remember. The constructive
part was where I said I'd be happy to give help.
> Now, we can either totally reorganize i2c-acorn, but that won't be
> acceptable for 2.6.29-rc.
i2c-acorn is just fine as is, while you might want to change
it to a platform driver at a later time.
> The problem is that this *is* a regression, and therefore must be fixed
> in 2.6.29-rc. As I see it, the only sane way to do that is to revert
> the conversion until a proper fix can be done.
>
> So, please provide constructive suggestions on how to add boardinfo to
> this in a sane way, or we revert PCF8583 back to something which works.
That's very simple, even if acorn is a bit unstructured. You just
need to choice a place under arch/arm that you like
(arch/arm/plat-acorn/ ? ) and place a bit of code called
by an appropriate initcall.
There you write something like that, changing
the values to match your rtc name and i2c address:
static struct i2c_board_info __initdata nslu2_i2c_board_info [] = {
{
I2C_BOARD_INFO("x1205", 0x6f),
},
};
...
i2c_register_board_info(0, nslu2_i2c_board_info,
ARRAY_SIZE(nslu2_i2c_board_info));
Unless I missed something that should be all you need.
--
Best regards,
Alessandro Zummo,
Tower Technologies - Torino, Italy
http://www.towertech.it
next prev parent reply other threads:[~2009-02-22 9:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-21 19:48 Fwd: PCF8583 not detected on RiscPC Russell King - ARM Linux
2009-02-21 20:41 ` Russell King - ARM Linux
2009-02-22 0:19 ` Alessandro Zummo
2009-02-22 8:28 ` Russell King - ARM Linux
2009-02-22 9:42 ` Alessandro Zummo [this message]
2009-02-22 9:51 ` Russell King - ARM Linux
2009-02-22 10:35 ` Alessandro Zummo
2009-02-22 11:26 ` Russell King - ARM Linux
2009-02-22 13:03 ` Alessandro Zummo
2009-02-22 9:52 ` Jean Delvare
2009-02-22 10:22 ` Russell King - ARM Linux
2009-02-22 10:40 ` Jean Delvare
2009-02-22 12:01 ` Russell King - ARM Linux
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=20090222104205.4539d3ef@i1501.lan.towertech.it \
--to=alessandro.zummo@towertech.it \
--cc=akpm@linux-foundation.org \
--cc=ben-linux-arm@fluff.org \
--cc=j.beisert@pengutronix.de \
--cc=khali@linux-fr.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=w.sang@pengutronix.de \
/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.