linux-stable.git/include/asm-arm/hardware, branch linux-2.6.14.y Linux kernel stable tree [ARM] 2962/1: scoop: Allow GPIO pin suspend state to be specified 2005-10-10T09:20:06+00:00 Richard Purdie rpurdie@rpsys.net 2005-10-10T09:20:06+00:00 7c3989885cfd37d237eca97832b712a7ffbbf40c Patch from Richard Purdie Allow the GPIO pin suspend states to be specified for SCOOP devices. This is needed for correct operation on the spitz platform. Signed-off-by: Richard Purdie <rpurdie@rpsys.net> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
Patch from Richard Purdie

Allow the GPIO pin suspend states to be specified for SCOOP devices.
This is needed for correct operation on the spitz platform.

Signed-off-by: Richard Purdie <rpurdie@rpsys.net>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[ARM SMP] Add timer/watchdog defines for MPCore 2005-09-14T22:10:48+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2005-09-14T22:10:48+00:00 f6af5da388a5d058cd9a5a47d030e3966b22e991 Actually add the file this time. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
Actually add the file this time.

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[ARM] 2882/1: pxa2xx_sharpsl: Update PCMCIA driver to support variety of new hardware 2005-09-05T19:49:54+00:00 Richard Purdie rpurdie@rpsys.net 2005-09-05T19:49:54+00:00 0ce7625f3c1e3f921f6b83f7e944e00031a39dfa Patch from Richard Purdie This patch updates the PCMCIA pxa2xx_sharpsl driver to support multiple scoop devices by adding a scoop to pcmcia slot mapping structure. It adds platform support for poodle, is known to work on spitz (which is dual slot) and should also support collie with a minor amount of further work. Signed-off-by: Richard Purdie <rpurdie@rpsys.net> Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
Patch from Richard Purdie

This patch updates the PCMCIA pxa2xx_sharpsl driver to support multiple scoop
devices by adding a scoop to pcmcia slot mapping structure. It adds platform
support for poodle, is known to work on spitz (which is dual slot) and
should also support collie with a minor amount of further work.

Signed-off-by: Richard Purdie <rpurdie@rpsys.net>
Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[ARM] Add support for ARM GIC 2005-08-18T20:31:00+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2005-08-18T20:31:00+00:00 f27ecacc54cc0e5397c9b35f6c25065f07c4448d Add support for the ARM Generic Interrupt Controller. Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> 
Add support for the ARM Generic Interrupt Controller.

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
[PATCH] ARM: Convert ARM timer implementations to use readl/writel 2005-06-29T14:15:54+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2005-06-29T14:15:54+00:00 b720f73296916e87c744193c57bc8687d35888fe Convert ARMs timer implementations to use readl/writel instead of accessing the registers via a struct. People have recently asked if accessing timers via a structure is the "right way" and its not the Linux way. So fix this code to conform to "The Linux Way"(tm). Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk> Acked-by: Catalin Marinas <catalin.marinas@arm.com> 
Convert ARMs timer implementations to use readl/writel instead of accessing
the registers via a struct.

People have recently asked if accessing timers via a structure is the
"right way" and its not the Linux way.  So fix this code to conform to
"The Linux Way"(tm).

Signed-off-by: Russell King <rmk+kernel@arm.linux.org.uk>
Acked-by: Catalin Marinas <catalin.marinas@arm.com>
[PATCH] ARM: AMBA CLCD: X resolutions must be multiples of 16 2005-04-28T09:46:15+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2005-04-28T09:46:15+00:00 0f7ad450394560a6b6c72115e04bf7afd6230e70 We ignore the bottom 4 bits of the X resolution, so we should round X resolutions up to the nearest multiple of 16. Signed-off-by: Russell King <rmk@arm.linux.org.uk> 
We ignore the bottom 4 bits of the X resolution, so we should
round X resolutions up to the nearest multiple of 16.

Signed-off-by: Russell King <rmk@arm.linux.org.uk>
[PATCH] ARM: Fix AMBA CLCD fb driver for 32bpp 2005-04-28T09:43:52+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2005-04-28T09:43:52+00:00 82235e9170f19fa327361ee82a76618e60f2db47 We were supporting 24bpp. However, the pixel organisation in memory was 0RGB, so it was 24bpp in 32bit words. This means we're actually supporting 32bpp and not 24bpp. Also, add a check to ensure that we don't exceed the available framebuffer when changing display resolutions. Signed-off-by: Russell King <rmk@arm.linux.org.uk> 
We were supporting 24bpp.  However, the pixel organisation in
memory was 0RGB, so it was 24bpp in 32bit words.  This means
we're actually supporting 32bpp and not 24bpp.

Also, add a check to ensure that we don't exceed the available
framebuffer when changing display resolutions.

Signed-off-by: Russell King <rmk@arm.linux.org.uk>
[PATCH] ARM: Fix AMBA CLCD fb driver for 1bpp/STN mono panels 2005-04-28T09:38:19+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2005-04-28T09:38:19+00:00 c4d12b98ead8bb2437f656c17e7ef065fa160e13 Fix the AMBA CLCD framebuffer driver for 1bpp modes and STN monochrome LCD panels. Signed-off-by: Russell King <rmk@arm.linux.org.uk> 
Fix the AMBA CLCD framebuffer driver for 1bpp modes and STN
monochrome LCD panels.

Signed-off-by: Russell King <rmk@arm.linux.org.uk>
[PATCH] ARM: Add further explaination for clk_get() 2005-04-27T17:19:55+00:00 Russell King rmk@dyn-67.arm.linux.org.uk 2005-04-27T17:19:55+00:00 ea3f4eaca09de1bcc80e922e56a6dabba5882f56 clk_get() comments can be confusing. Add extra explaination of the dev and id parameters to ensure correct usage. Signed-off-by: Russell King <rmk@arm.linux.org.uk> 
clk_get() comments can be confusing.  Add extra explaination of
the dev and id parameters to ensure correct usage.

Signed-off-by: Russell King <rmk@arm.linux.org.uk>
Linux-2.6.12-rc2 2005-04-16T22:20:36+00:00 Linus Torvalds torvalds@ppc970.osdl.org 2005-04-16T22:20:36+00:00 1da177e4c3f41524e886b7f1b8a0c1fc7321cac2 Initial git repository build. I'm not bothering with the full history, even though we have it. We can create a separate "historical" git archive of that later if we want to, and in the meantime it's about 3.2GB when imported into git - space that would just make the early git days unnecessarily complicated, when we don't have a lot of good infrastructure for it. Let it rip! 
Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.

Let it rip!