From: Russell King <rmk+lkml@arm.linux.org.uk>
To: Pavel Machek <pavel@ucw.cz>
Cc: rpurdie@rpsys.net, lenz@cs.wisc.edu,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [patch] fix ucb1x00 support on collie
Date: Sun, 31 Jul 2005 16:42:45 +0100 [thread overview]
Message-ID: <20050731164245.B20106@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20050731134617.GA25906@elf.ucw.cz>; from pavel@ucw.cz on Sun, Jul 31, 2005 at 03:46:17PM +0200
On Sun, Jul 31, 2005 at 03:46:17PM +0200, Pavel Machek wrote:
> Collie is slightly strange; it does not seem to have proper ucb1x00
> ID. With this patch, basic ucb support seems to work and I can get
> interrupts from battery.
Out of interest, what ID does it appear to have?
> diff --git a/drivers/misc/mcp-sa1100.c b/drivers/misc/mcp-sa1100.c
> --- a/drivers/misc/mcp-sa1100.c
> +++ b/drivers/misc/mcp-sa1100.c
> @@ -149,7 +149,7 @@ static int mcp_sa1100_probe(struct devic
> !machine_is_graphicsmaster() && !machine_is_lart() &&
> !machine_is_omnimeter() && !machine_is_pfs168() &&
> !machine_is_shannon() && !machine_is_simpad() &&
> - !machine_is_yopy())
> + !machine_is_yopy() && !machine_is_collie())
I think it's about time we did something better with this, like only
registering the platform device on those which use it.
> @@ -181,7 +187,10 @@ static int mcp_sa1100_probe(struct devic
>
> Ser4MCSR = -1;
> Ser4MCCR1 = 0;
> - Ser4MCCR0 = 0x00007f7f | MCCR0_ADM;
> + if (machine_is_collie())
> + Ser4MCCR0 = MCCR0_ADM | MCCR0_ExtClk;
> + else
> + Ser4MCCR0 = 0x00007f7f | MCCR0_ADM;
And this setup should probably be passed as part of the platform device
data.
--
Russell King
Linux kernel 2.6 ARM Linux - http://www.arm.linux.org.uk/
maintainer of: 2.6 Serial core
next prev parent reply other threads:[~2005-07-31 15:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-31 13:46 [patch] fix ucb1x00 support on collie Pavel Machek
2005-07-31 15:42 ` Russell King [this message]
2005-08-07 14:08 ` Russell King
2005-08-12 11:11 ` Pavel Machek
2005-08-12 19:49 ` Russell King
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=20050731164245.B20106@flint.arm.linux.org.uk \
--to=rmk+lkml@arm.linux.org.uk \
--cc=lenz@cs.wisc.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.cz \
--cc=rpurdie@rpsys.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 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.