nt to fail to work:
WARNING: CPU: 0 PID: 1 at drivers/clk/clk.c:883 __clk_enable+0x2c/0xa0()
Cc: "Rafael J. Wysocki"
Cc: Pavel Machek
Cc: Greg Kroah-Hartman
Cc: linux...@vger.kernel.org
Cc: linux...@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Signed-off-by: Ben Dooks
Rev
-off-by: Ben Dooks ben.do...@codethink.co.uk
Reviewed-by: Ian Molton ian.mol...@codethink.co.uk
---
drivers/base/power/clock_ops.c | 7 +--
1 file changed, 5 insertions(+), 2 deletions(-)
diff --git a/drivers/base/power/clock_ops.c b/drivers/base/power/clock_ops.c
index 9d8fde7..b9dd8fa 100644
...@linuxfoundation.org
Signed-off-by: Ben Dooks ben.do...@codethink.co.uk
---
drivers/Makefile| 1 +
drivers/sh/Makefile | 3 +++
2 files changed, 4 insertions(+)
diff --git a/drivers/Makefile b/drivers/Makefile
index 8e3b8b0..abc4744 100644
--- a/drivers/Makefile
+++ b/drivers/Makefile
@@ -118,6 +118,7
Sorry, as a note the patch title /should/ have been:
power: fixup clock_ops clk prepare count usage
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
--
To unsubscribe from this list: send the line
On 10/01/14 15:59, Geert Uytterhoeven wrote:
Hi Ben,
On Fri, Jan 10, 2014 at 4:06 PM, Ben Dooks ben.do...@codethink.co.uk wrote:
On the Renesas Lager board, this causes numerous warnings of the following
and even worse the clock system will not enable clocks, causing drivers
On 10/01/14 17:09, Geert Uytterhoeven wrote:
On Fri, Jan 10, 2014 at 5:23 PM, Ben Dooks ben.do...@codethink.co.uk wrote:
On 10/01/14 15:59, Geert Uytterhoeven wrote:
On Fri, Jan 10, 2014 at 4:06 PM, Ben Dooks ben.do...@codethink.co.uk
wrote:
On the Renesas Lager board, this causes numerous
On Mon, Nov 25, 2013 at 02:55:37PM -0800, Doug Anderson wrote:
> On modern SoCs the watchdog timer is parented on a clock that doesn't
> change every time we have a cpufreq change. That means we don't need
> to constantly adjust the watchdog timer, so avoid registering for and
> dealing with
On Mon, Nov 25, 2013 at 02:55:37PM -0800, Doug Anderson wrote:
On modern SoCs the watchdog timer is parented on a clock that doesn't
change every time we have a cpufreq change. That means we don't need
to constantly adjust the watchdog timer, so avoid registering for and
dealing with cpufreq
to add a note about endian-ness.
Given these are single instructoins for ARM, is it possible we could
make a table of all the callers and fix them up when we initialise
as we do for the SMP/UP case and for page-offset?
--
Ben Dooks htt
these are single instructoins for ARM, is it possible we could
make a table of all the callers and fix them up when we initialise
as we do for the SMP/UP case and for page-offset?
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink
clocks, which I added
in mine. This is also an issue with the clock and serial drivers
which do not ensure the bus/module clocks have been enabled in
the driver.
Mine also dealt with the multiple parents that some of these
clocks have.
I can try and re-post tonight for discussion.
--
Ben Dooks
try and re-post tonight for discussion.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord
to indicate the criticality of operation
+ * r3 - @pargs: Physical address of parameter list
+ */
+ENTRY(omap_smc3)
+ stmfd sp!, {r4-r11, lr}
+ mov r12, r0 @ Copy the secure service ID
I think you should save r12 in the call.
--
Ben Dooks http
service ID
I think you should save r12 in the call.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer Codethink - Providing Genius
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message
ble
without changing the kernel source to add these flag checks.
I also don't like information hidden away that the user cannot see.
Having the device specifically named allows us to see from sysfs
exactly what we are dealing with.
--
Ben Dooks http://www.codethink.co
the kernel source to add these flag checks.
I also don't like information hidden away that the user cannot see.
Having the device specifically named allows us to see from sysfs
exactly what we are dealing with.
--
Ben Dooks http://www.codethink.co.uk/
Senior Engineer
ernel/people/jdelvare/linux-2.6/jdelvare-i2c/
> -T: git git://git.fluff.org/bjdooks/linux.git
> +T: git git://git.pengutronix.de/git/wsa/linux.git
> S: Maintained
> F: Documentation/i2c/
> F: drivers/i2c/
Acked-by: Ben Dooks
--
Ben Dooks, b...@fluff.org, ht
/jdelvare-i2c/
-T: git git://git.fluff.org/bjdooks/linux.git
+T: git git://git.pengutronix.de/git/wsa/linux.git
S: Maintained
F: Documentation/i2c/
F: drivers/i2c/
Acked-by: Ben Dooks ben-li...@fluff.org
--
Ben Dooks, b...@fluff.org, http://www.fluff.org/ben/
Large Hadron Colada
On 20/08/2012 06:49, Linus Walleij wrote:
On Sat, Aug 11, 2012 at 2:56 PM, Sebastian Hesselbarth
wrote:
This patch adds a SoC specific pinctrl driver for Marvell Kirkwood
SoCs
plus DT binding documentation. This driver will use the mvebu
pinctrl
driver core.
Thanks for working on
On 20/08/2012 06:49, Linus Walleij wrote:
On Sat, Aug 11, 2012 at 2:56 PM, Sebastian Hesselbarth
sebastian.hesselba...@gmail.com wrote:
This patch adds a SoC specific pinctrl driver for Marvell Kirkwood
SoCs
plus DT binding documentation. This driver will use the mvebu
pinctrl
driver core.
On Wed, Feb 20, 2008 at 08:37:09PM +0100, Sam Ravnborg wrote:
> On Wed, Feb 20, 2008 at 03:44:04PM +0100, Michael Buesch wrote:
> > On Wednesday 20 February 2008 01:44:38 Gordon Farquharson wrote:
> > > Hi Michael
> > >
> > > On Feb 19, 2008 3:41 AM, Michael Buesch <[EMAIL PROTECTED]> wrote:
> >
On Wed, Feb 20, 2008 at 08:37:09PM +0100, Sam Ravnborg wrote:
On Wed, Feb 20, 2008 at 03:44:04PM +0100, Michael Buesch wrote:
On Wednesday 20 February 2008 01:44:38 Gordon Farquharson wrote:
Hi Michael
On Feb 19, 2008 3:41 AM, Michael Buesch [EMAIL PROTECTED] wrote:
[2]
I've just found how easy it is to accidentally register
a sysdev_driver for two different classes. When this
happens, bad things happen as the sysdev_driver structure
keeps has the list entry for the driver registration.
The following patch makes a WARN_ON() if this happens,
although I think
I've just found how easy it is to accidentally register
a sysdev_driver for two different classes. When this
happens, bad things happen as the sysdev_driver structure
keeps has the list entry for the driver registration.
The following patch makes a WARN_ON() if this happens,
although I think
On Thu, Feb 14, 2008 at 01:53:15PM -0800, Harvey Harrison wrote:
> In C, signed 1-bit bitfields can only take the values 0 and -1, only
> 0 and 1 are ever assigned in current code. Make them unsigned
> bitfields.
>
> Fixes the (repeated) sparse errors:
> drivers/mtd/ubi/ubi.h:220:15: error:
The drivers/memstick/Kconfig references MMC where it should read MemoryStick
Signed-off-by: Ben Dooks <[EMAIL PROTECTED]>
diff -urNp linux-2.6.25-rc1/drivers/memstick/Kconfig
linux-2.6.25-rc1-bjd1/drivers/memstick/Kconfig
--- linux-2.6.25-rc1/drivers/memstick/Kconfig 2008-02-13
The drivers/memstick/Kconfig references MMC where it should read MemoryStick
Signed-off-by: Ben Dooks [EMAIL PROTECTED]
diff -urNp linux-2.6.25-rc1/drivers/memstick/Kconfig
linux-2.6.25-rc1-bjd1/drivers/memstick/Kconfig
--- linux-2.6.25-rc1/drivers/memstick/Kconfig 2008-02-13 20:04
On Thu, Feb 14, 2008 at 01:53:15PM -0800, Harvey Harrison wrote:
In C, signed 1-bit bitfields can only take the values 0 and -1, only
0 and 1 are ever assigned in current code. Make them unsigned
bitfields.
Fixes the (repeated) sparse errors:
drivers/mtd/ubi/ubi.h:220:15: error: dubious
On Fri, Feb 08, 2008 at 06:57:42PM +0900, Magnus Damm wrote:
> This patch extends the sm501 mfd with 8250 uart support. We're currently
> doing this in the board specific r2d-1 code already, but it would be nice to
> do move things into the mfd since it's more chip specific than board specific.
On Fri, Feb 08, 2008 at 06:57:42PM +0900, Magnus Damm wrote:
This patch extends the sm501 mfd with 8250 uart support. We're currently
doing this in the board specific r2d-1 code already, but it would be nice to
do move things into the mfd since it's more chip specific than board specific.
On Mon, Feb 04, 2008 at 12:37:14PM +0100, Kristoffer Ericson wrote:
> Greetings,
>
> Trying to wrap my head around sm501. From what I can tell an mfd driver is a
> "master" driver that takes control of all
> memory and io areas. It then hands out areas of those to drivers. Anywhere
> near
On Mon, Feb 04, 2008 at 12:37:14PM +0100, Kristoffer Ericson wrote:
Greetings,
Trying to wrap my head around sm501. From what I can tell an mfd driver is a
master driver that takes control of all
memory and io areas. It then hands out areas of those to drivers. Anywhere
near correct?
On Mon, Jan 21, 2008 at 10:05:56PM -0600, Corey Minyard wrote:
> From: Corey Minyard <[EMAIL PROTECTED]>
>
> The DNS-323 system has several bogus memory entries in the tag table,
> and it caused the system to crash at startup. Ignore tag entries that
> are obviously bogus.
This should have gone
On Mon, Jan 21, 2008 at 10:05:56PM -0600, Corey Minyard wrote:
From: Corey Minyard [EMAIL PROTECTED]
The DNS-323 system has several bogus memory entries in the tag table,
and it caused the system to crash at startup. Ignore tag entries that
are obviously bogus.
This should have gone to the
On Fri, Jan 18, 2008 at 06:11:45PM +, Dmitry Baryshkov wrote:
> Hi,
>
> Dmitry Torokhov wrote:
>
> > I will need some more time to review and understand the need for the new
> > bus in the driver.
>
> Most likely this can be converted to platform_bus. Maybe this can also get
> help from
On Thu, Jan 10, 2008 at 04:11:08PM +0100, Marc Pignat wrote:
> watchdog driver for embedded systems with a supervisor watchdog (MAX823 or so)
> connected to a gpio. This is the platform_driver and needs platform_data for
> defining the gpio pin and the watchdog timeout.
>
> Signed-off-by: Marc
On Mon, Jan 07, 2008 at 11:28:29AM +0800, cksim wrote:
> Hi,
>
> Yesterday, I have encountered an issue when the kernel size is more than
> 1.3MB.
>
> Info on problem encountered as follows:
> 1) I am using Atmel AT91SAM9261 part. Circuit similar to that of AT91SAM9261EK
> evaluation board.
>
On Mon, Jan 07, 2008 at 11:28:29AM +0800, cksim wrote:
Hi,
Yesterday, I have encountered an issue when the kernel size is more than
1.3MB.
Info on problem encountered as follows:
1) I am using Atmel AT91SAM9261 part. Circuit similar to that of AT91SAM9261EK
evaluation board.
2) I am
On Thu, Jan 03, 2008 at 04:04:06PM -0600, Josh Boyer wrote:
> Rework the architecture specific Makefiles to use the in-kernel version of
> the mkubootimg tool.
>
> Signed-off-by: Josh Boyer <[EMAIL PROTECTED]>
A CC: to RMK and any other arch maintainers being touched by this
would have useful
On Thu, Jan 03, 2008 at 04:04:06PM -0600, Josh Boyer wrote:
Rework the architecture specific Makefiles to use the in-kernel version of
the mkubootimg tool.
Signed-off-by: Josh Boyer [EMAIL PROTECTED]
A CC: to RMK and any other arch maintainers being touched by this
would have useful too.
--
On Mon, Dec 03, 2007 at 08:22:07AM -0600, Matt Porter wrote:
> On Sat, Dec 01, 2007 at 09:50:10PM +0100, Pierre Ossman wrote:
> > As for the patch, it's a big NAK at this point. Vendors who can't be
> > bothered to follow
> > the standard will have to wait for Ben's separation patches before they
On Mon, Dec 03, 2007 at 08:22:07AM -0600, Matt Porter wrote:
On Sat, Dec 01, 2007 at 09:50:10PM +0100, Pierre Ossman wrote:
As for the patch, it's a big NAK at this point. Vendors who can't be
bothered to follow
the standard will have to wait for Ben's separation patches before they can
On Fri, Nov 23, 2007 at 01:43:29PM +0200, Heikki Orsila wrote:
> On Fri, Nov 23, 2007 at 12:15:53AM +, Daniel Drake wrote:
> > Why unaligned access is bad
> > ===
> >
> > Most architectures are unable to perform unaligned memory accesses. Any
> > unaligned access
On Fri, Nov 23, 2007 at 01:43:29PM +0200, Heikki Orsila wrote:
On Fri, Nov 23, 2007 at 12:15:53AM +, Daniel Drake wrote:
Why unaligned access is bad
===
Most architectures are unable to perform unaligned memory accesses. Any
unaligned access causes a
Remove errnoeous x character from dev_dbg() call that
stops the driver compiling under debug.
Signed-off-by: Ben Dooks <[EMAIL PROTECTED]>
Index: linux-2.6.22-quilt2/drivers/mfd/sm501.c
===
--- linux-2.6.22-quilt2.orig/drive
Remove errnoeous x character from dev_dbg() call that
stops the driver compiling under debug.
Signed-off-by: Ben Dooks [EMAIL PROTECTED]
Index: linux-2.6.22-quilt2/drivers/mfd/sm501.c
===
--- linux-2.6.22-quilt2.orig/drivers/mfd
On Tue, Nov 13, 2007 at 10:34:37PM +, Russell King wrote:
> On Tue, Nov 13, 2007 at 06:25:16PM +, Alan Cox wrote:
> > > Given the wide range of ARM platforms today, it is utterly idiotic to
> > > expect a single person to be able to provide responses for all ARM bugs.
> > > I for one wish
On Tue, Nov 13, 2007 at 10:34:37PM +, Russell King wrote:
On Tue, Nov 13, 2007 at 06:25:16PM +, Alan Cox wrote:
Given the wide range of ARM platforms today, it is utterly idiotic to
expect a single person to be able to provide responses for all ARM bugs.
I for one wish I'd never
On Sat, Sep 29, 2007 at 10:15:12PM -0500, Rob Landley wrote:
> From: Rob Landley <[EMAIL PROTECTED]>
>
> The existing Documentation/SM501.txt gives no clue what the chip is or does,
> so copy the description from Kconfig help text.
>
> cc: Ben Dooks <[EMAIL PROT
On Sat, Sep 29, 2007 at 10:15:12PM -0500, Rob Landley wrote:
From: Rob Landley [EMAIL PROTECTED]
The existing Documentation/SM501.txt gives no clue what the chip is or does,
so copy the description from Kconfig help text.
cc: Ben Dooks [EMAIL PROTECTED]
Acked-by: Ben Dooks [EMAIL PROTECTED
On Wed, Aug 15, 2007 at 02:11:17AM +0800, Conke Hu wrote:
> regs-nand.h and nand.h for s3c nand driver have been moved to plat-s3c/ dir.
>
> Signed-off-by: [EMAIL PROTECTED]
This patch is currently awaiting the MTD maintainer to push
to linus, which should hopefully be next week.
--
Ben
On Wed, Aug 15, 2007 at 02:11:17AM +0800, Conke Hu wrote:
regs-nand.h and nand.h for s3c nand driver have been moved to plat-s3c/ dir.
Signed-off-by: [EMAIL PROTECTED]
This patch is currently awaiting the MTD maintainer to push
to linus, which should hopefully be next week.
--
Ben ([EMAIL
Fixup the changes from moving around the arch
support for s3c24xx based systems.
Signed-off-by: Ben Dooks <[EMAIL PROTECTED]>
diff -urpN -X linux-2.6.22-git16-moves1/Documentation/dontdiff
linux-2.6.22-git16-moves1/drivers/rtc/rtc-s3c.c
linux-2.6.22-git16-moves1-fixups-split-moves2
Fixup the s3c2410 watchdog driver after moving some
of the arch specific includes it has been relying on.
Signed-off-by: Ben Dooks <[EMAIL PROTECTED]>
diff -urpN -X linux-2.6.22-git16-moves1/Documentation/dontdiff
linux-2.6.22-git16-moves1/drivers/char/watchdog/s3c2410_wdt.c
linux-2.6.22
Fixup the s3c2410 watchdog driver after moving some
of the arch specific includes it has been relying on.
Signed-off-by: Ben Dooks [EMAIL PROTECTED]
diff -urpN -X linux-2.6.22-git16-moves1/Documentation/dontdiff
linux-2.6.22-git16-moves1/drivers/char/watchdog/s3c2410_wdt.c
linux-2.6.22-git16
Fixup the changes from moving around the arch
support for s3c24xx based systems.
Signed-off-by: Ben Dooks [EMAIL PROTECTED]
diff -urpN -X linux-2.6.22-git16-moves1/Documentation/dontdiff
linux-2.6.22-git16-moves1/drivers/rtc/rtc-s3c.c
linux-2.6.22-git16-moves1-fixups-split-moves2-fixup/drivers
On Tue, Jul 17, 2007 at 02:40:42PM -0700, David Miller wrote:
> From: Al Viro <[EMAIL PROTECTED]>
> Date: Tue, 17 Jul 2007 22:29:46 +0100
>
> > ... or we end up with header include order problems from hell.
> > E.g. on m68k this is 100% fatal - local_irq_enable() there
> > wants preempt_count(),
On Tue, Jul 17, 2007 at 02:40:42PM -0700, David Miller wrote:
From: Al Viro [EMAIL PROTECTED]
Date: Tue, 17 Jul 2007 22:29:46 +0100
... or we end up with header include order problems from hell.
E.g. on m68k this is 100% fatal - local_irq_enable() there
wants preempt_count(), which wants
On Fri, Jun 22, 2007 at 11:34:36AM +0200, Rodolfo Giometti wrote:
> I just updated my linux tree from 2.6.20-rc6 to 2.6.22-rc3 for my
> custom PXA270 based board and I discovered that now sleep/wakeup
> functionality doesn't work anymore! :'(
This is already on linux-arm-kernel, the best place to
On Fri, Jun 22, 2007 at 11:34:36AM +0200, Rodolfo Giometti wrote:
I just updated my linux tree from 2.6.20-rc6 to 2.6.22-rc3 for my
custom PXA270 based board and I discovered that now sleep/wakeup
functionality doesn't work anymore! :'(
This is already on linux-arm-kernel, the best place to
The suspend and resume support only needs to be built if
CONFIG_PM is defined.
Signed-off-by: Ben Dooks <[EMAIL PROTECTED]>
Index: linux-2.6.21-quilt9/drivers/mfd/sm501.c
===
--- linux-2.6.21-quilt9.orig/drivers/mfd/s
The suspend and resume support only needs to be built if
CONFIG_PM is defined.
Signed-off-by: Ben Dooks [EMAIL PROTECTED]
Index: linux-2.6.21-quilt9/drivers/mfd/sm501.c
===
--- linux-2.6.21-quilt9.orig/drivers/mfd/sm501.c
+++ linux
On Thu, Jun 14, 2007 at 01:22:00PM +0200, Sam Ravnborg wrote:
> On Thu, Jun 14, 2007 at 11:01:09AM +0100, Ben Dooks wrote:
> > A set of fixes and documentation updates for
> > the drivers/mfd/sm501.c SM501 driver
>
> What is this mfd / sm501 thing?
> A _very_ quick
Announce the watchdog once the initialisation is
complete. This aides debugging problems where the
watchdog driver has been loaded and shows the
current state for the user.
Signed-off-by: Ben Dooks <[EMAIL PROTECTED]>
Index: linux-2.6.21-quilt2/drivers/char/watchdog/s3c2410
Move to using dev_info(), dev_dbg() and dev_err() for
reporting information from the driver.
Signed-off-by: Ben Dooks <[EMAIL PROTECTED]>
Index: linux-2.6.21-quilt2/drivers/char/watchdog/s3c2410_wdt.c
===
--- linux-2.6.21-
Updates for the S3C24XX watchdog driver
--
Ben ([EMAIL PROTECTED], http://www.fluff.org/)
'a smiley only costs 4 bytes'
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
On Mon, May 28, 2007 at 07:05:43PM +0800, ?? wrote:
> Hi,All.
>
> I compiled new kernel2.6.22-rc3 for my s3c2440 platform yesterday,
> I got follow error message from gcc-compiler.
>
> >CC arch/arm/plat-s3c24xx/devs.o
> >linux/linux-2.6/arch/arm/plat-s3c24xx/devs.c:410:
>
This patch adds support for suspending the core
(mfd driver) of the SM501.
Signed-off-by: Ben Dooks <[EMAIL PROTECTED]>
Index: linux-2.6.21-quilt8/drivers/mfd/sm501.c
===
--- linux-2.6.21-quilt8.orig/drivers/mfd/sm501.c
Add documentation for the SM501 in Documentation/SM501.txt
outlining the SM501 driver.
Signed-off-by: Ben Dooks <[EMAIL PROTECTED]>
Index: linux-2.6.21-quilt8/Documentation/SM501.txt
===
--- /dev/null 1970-01-01 00:00:00.000
When binding the driver, check the ID register for a valid
identity, in case the SM501 is not functioning correctly.
Signed-off-by: Ben Dooks <[EMAIL PROTECTED]>
Index: linux-2.6.21-quilt8/drivers/mfd/sm501.c
===
--- linux-
Ensure that the M1XCLK and MCLK are sourced from
the same PLL (and refuse to bind the driver if they
are not).
Update the PCI to safe initialisation values, as 72MHz
is the maximum clock for 33MHz PCI bus mastering.
Signed-off-by: Ben Dooks <[EMAIL PROTECTED]>
Index: linux-2.6.21-quilt8/d
A set of fixes and documentation updates for
the drivers/mfd/sm501.c SM501 driver
--
Ben ([EMAIL PROTECTED], http://www.fluff.org/)
'a smiley only costs 4 bytes'
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More
The order of the set and mask operation in sm501_init_reg()
was setting and then masking the bits set. Correct the order
so that we do not end up with 288MHz SDRAM clocks on certain
systems.
Signed-off-by: Ben Dooks <[EMAIL PROTECTED]>
Index: linux-2.6.21-quilt8/drivers/mfd/s
This init sequence of setting the SDRAM clock before the
bus clock is recommend by Silicon Motion to stop problems
with writes not sticking into registers.
Signed-off-by: Vincent Sanders <[EMAIL PROTECTED]>
Signed-off-by: Ben Dooks <[EMAIL PROTECTED]>
Index: linux-2.6.21-quilt8/drive
The order of the set and mask operation in sm501_init_reg()
was setting and then masking the bits set. Correct the order
so that we do not end up with 288MHz SDRAM clocks on certain
systems.
Signed-off-by: Ben Dooks [EMAIL PROTECTED]
Index: linux-2.6.21-quilt8/drivers/mfd/sm501.c
This init sequence of setting the SDRAM clock before the
bus clock is recommend by Silicon Motion to stop problems
with writes not sticking into registers.
Signed-off-by: Vincent Sanders [EMAIL PROTECTED]
Signed-off-by: Ben Dooks [EMAIL PROTECTED]
Index: linux-2.6.21-quilt8/drivers/mfd/sm501.c
Ensure that the M1XCLK and MCLK are sourced from
the same PLL (and refuse to bind the driver if they
are not).
Update the PCI to safe initialisation values, as 72MHz
is the maximum clock for 33MHz PCI bus mastering.
Signed-off-by: Ben Dooks [EMAIL PROTECTED]
Index: linux-2.6.21-quilt8/drivers
A set of fixes and documentation updates for
the drivers/mfd/sm501.c SM501 driver
--
Ben ([EMAIL PROTECTED], http://www.fluff.org/)
'a smiley only costs 4 bytes'
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More
Add documentation for the SM501 in Documentation/SM501.txt
outlining the SM501 driver.
Signed-off-by: Ben Dooks [EMAIL PROTECTED]
Index: linux-2.6.21-quilt8/Documentation/SM501.txt
===
--- /dev/null 1970-01-01 00:00:00.0
When binding the driver, check the ID register for a valid
identity, in case the SM501 is not functioning correctly.
Signed-off-by: Ben Dooks [EMAIL PROTECTED]
Index: linux-2.6.21-quilt8/drivers/mfd/sm501.c
===
--- linux-2.6.21
This patch adds support for suspending the core
(mfd driver) of the SM501.
Signed-off-by: Ben Dooks [EMAIL PROTECTED]
Index: linux-2.6.21-quilt8/drivers/mfd/sm501.c
===
--- linux-2.6.21-quilt8.orig/drivers/mfd/sm501.c2007
On Mon, May 28, 2007 at 07:05:43PM +0800, ?? wrote:
Hi,All.
I compiled new kernel2.6.22-rc3 for my s3c2440 platform yesterday,
I got follow error message from gcc-compiler.
CC arch/arm/plat-s3c24xx/devs.o
linux/linux-2.6/arch/arm/plat-s3c24xx/devs.c:410:
error:'S3C2443_PA_HSMMC'
Updates for the S3C24XX watchdog driver
--
Ben ([EMAIL PROTECTED], http://www.fluff.org/)
'a smiley only costs 4 bytes'
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo info at
Announce the watchdog once the initialisation is
complete. This aides debugging problems where the
watchdog driver has been loaded and shows the
current state for the user.
Signed-off-by: Ben Dooks [EMAIL PROTECTED]
Index: linux-2.6.21-quilt2/drivers/char/watchdog/s3c2410_wdt.c
Move to using dev_info(), dev_dbg() and dev_err() for
reporting information from the driver.
Signed-off-by: Ben Dooks [EMAIL PROTECTED]
Index: linux-2.6.21-quilt2/drivers/char/watchdog/s3c2410_wdt.c
===
--- linux-2.6.21-quilt2.orig
On Thu, Jun 14, 2007 at 01:22:00PM +0200, Sam Ravnborg wrote:
On Thu, Jun 14, 2007 at 11:01:09AM +0100, Ben Dooks wrote:
A set of fixes and documentation updates for
the drivers/mfd/sm501.c SM501 driver
What is this mfd / sm501 thing?
A _very_ quick googeling did not reveal it.
drivers
SM501: Check SM501 ID register on initialisation
When binding the driver, check the ID register for a valid
identity, in case the SM501 is not functioning correctly.
Signed-off-by: Ben Dooks <[EMAIL PROTECTED]>
Index: linux-2.6.21-quilt8/drivers/mfd/s
SM501: Clock updates and checks
Ensure that the M1XCLK and MCLK are sourced from
the same PLL (and refuse to bind the driver if they
are not).
Update the PCI to safe initialisation values, as 72MHz
is the maximum clock for 33MHz PCI bus mastering.
Signed-off-by: Ben Dooks <[EMAIL PROTEC
SM501: Add Documentation/SM501.txt
Add documentation for the SM501 in Documentation/SM501.txt
outlining the SM501 driver.
Signed-off-by: Ben Dooks <[EMAIL PROTECTED]>
Index: linux-2.6.21-quilt8/Documentation/SM501.txt
===
--
Fixes and documentation updates for the SM501
MFD driver. These should all be suitable for
inclusion into the current kernel.
All patches based on 2.6.22-rc4
--
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo
SM501: suspend support
This patch adds support for suspending the core
(mfd driver) of the SM501.
Signed-off-by: Ben Dooks <[EMAIL PROTECTED]>
Index: linux-2.6.21-quilt8/drivers/mfd/sm501.c
===
--- linux-2.6.21-quilt8.orig/d
SM501: Fix sm501_init_reg() mask/set order
The order of the set and mask operation in sm501_init_reg()
was setting and then masking the bits set. Correct the order
so that we do not end up with 288MHz SDRAM clocks on certain
systems.
Signed-off-by: Ben Dooks <[EMAIL PROTECTED]>
Index:
SM501: initialise SDRAM clock before bus clocks
This init sequence of setting the SDRAM clock before the
bus clock is recommend by Silicon Motion to stop problems
with writes not sticking into registers.
Signed-off-by: Vincent Sanders <[EMAIL PROTECTED]>
Signed-off-by: Ben Dooks &
SM501: Fix sm501_init_reg() mask/set order
The order of the set and mask operation in sm501_init_reg()
was setting and then masking the bits set. Correct the order
so that we do not end up with 288MHz SDRAM clocks on certain
systems.
Signed-off-by: Ben Dooks [EMAIL PROTECTED]
Index: linux
SM501: initialise SDRAM clock before bus clocks
This init sequence of setting the SDRAM clock before the
bus clock is recommend by Silicon Motion to stop problems
with writes not sticking into registers.
Signed-off-by: Vincent Sanders [EMAIL PROTECTED]
Signed-off-by: Ben Dooks [EMAIL PROTECTED
Fixes and documentation updates for the SM501
MFD driver. These should all be suitable for
inclusion into the current kernel.
All patches based on 2.6.22-rc4
--
-
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to [EMAIL PROTECTED]
More majordomo
SM501: suspend support
This patch adds support for suspending the core
(mfd driver) of the SM501.
Signed-off-by: Ben Dooks [EMAIL PROTECTED]
Index: linux-2.6.21-quilt8/drivers/mfd/sm501.c
===
--- linux-2.6.21-quilt8.orig/drivers
SM501: Clock updates and checks
Ensure that the M1XCLK and MCLK are sourced from
the same PLL (and refuse to bind the driver if they
are not).
Update the PCI to safe initialisation values, as 72MHz
is the maximum clock for 33MHz PCI bus mastering.
Signed-off-by: Ben Dooks [EMAIL PROTECTED
SM501: Add Documentation/SM501.txt
Add documentation for the SM501 in Documentation/SM501.txt
outlining the SM501 driver.
Signed-off-by: Ben Dooks [EMAIL PROTECTED]
Index: linux-2.6.21-quilt8/Documentation/SM501.txt
===
--- /dev
SM501: Check SM501 ID register on initialisation
When binding the driver, check the ID register for a valid
identity, in case the SM501 is not functioning correctly.
Signed-off-by: Ben Dooks [EMAIL PROTECTED]
Index: linux-2.6.21-quilt8/drivers/mfd/sm501.c
501 - 600 of 688 matches
Mail list logo
