This allows the ssbi module to be autoloaded on boot.
Cc: David Brown dav...@codeaurora.org
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
drivers/mfd/ssbi.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mfd/ssbi.c b/drivers/mfd/ssbi.c
index f32da02..e561d3b 100644
---
Use devm_ioremap_resource and devm_kzalloc to simplify error
paths and reduce lines of code.
Cc: David Brown dav...@codeaurora.org
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
drivers/mfd/ssbi.c | 69 +-
1 file changed, 11
This patch adds support of recognizing hard-wired (permanent) cards
to Freescale's SDHC host driver. This is done by adding the option
fsl,card-wired to the SDHC device-tree entry. Detection of this
option is done in the probe function. Update documentation in file
fsl-esdhc.txt
Signed-off-by:
If we're suspended and sched_clock() is called we're going to
read the hardware one more time and throw away that value and
return back the cached value we saved during the suspend
callback. This is wasteful. Let's short circuit all that and
return the cached value as early as possible if we're
This is mostly a resend of a patch series I sent a little over a month
ago. I've reordered the patches so that John can pick up the first three
and get a generic sched_clock layer without having to take the 64 bit
patches. The last three patches add 64 bit support and move the architected
timers
The needs_suspend member is unused now that we always do the
suspend/resume handling (see 6a4dae5 (ARM: 7565/1: sched: stop
sched_clock() during suspend, 2012-10-23)).
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/kernel/sched_clock.c | 1 -
1 file changed, 1 deletion(-)
diff
Register with the ARM sched_clock framework now that it supports
64 bits. This fixes two problems with the current sched_clock
support for machines using the architected timers. First off, we
don't subtract the start value from subsequent sched_clock calls
so we can potentially start off with
The ARM architected system counter has at least 56 useable bits.
Add support for counters with more than 32 bits to the generic
sched_clock implementation so we can avoid the complexity of
dealing with wrap-around on these devices while benefiting from
the irqtime accounting and suspend/resume
Use the generic sched_clock infrastructure instead of rolling our
own. This has the added benefit of fixing suspend/resume as
outlined in 6a4dae5 (ARM: 7565/1: sched: stop sched_clock()
during suspend, 2012-10-23) and correcting the timestamps when
the hardware returns a value instead of 0 upon
Nothing about the sched_clock implementation in the ARM port is
specific to the architecture. Generalize the code so that other
architectures can use it by selecting GENERIC_SCHED_CLOCK.
Signed-off-by: Stephen Boyd sb...@codeaurora.org
---
arch/arm/Kconfig |
On 06/02/2013 02:02 AM, Jeremy Fitzhardinge wrote:
On 06/01/2013 12:21 PM, Raghavendra K T wrote:
x86/spinlock: Replace pv spinlocks with pv ticketlocks
From: Jeremy Fitzhardinge jeremy.fitzhardi...@citrix.com
I'm not sure what the etiquette is here; I did the work while at Citrix,
but
The P2020 has a non-standard implementation of the SDHCI_HOST_CONTROL
register. This patch adds a QUIRK in the SDHCI header to signal that
a host controller has a non-standard SDHCI_HOST_CONTROL register. The
patch adds a check to the function esdhc_writeb in file
sdhci-of-esdhc.c, where it checks
This patch adds support of connecting an MMC media using an 8-bit
bus width connection to Freescale's P2020 H/W SDHC controller. During
the probe function, it detects if the processor is P2020 (by looking
at device tree) and if so, it adds the MMC_CAP_8_BIT_DATA to the MMC
caps
Ben Greear gree...@candelatech.com writes:
It turns out, the bug I spent yesterday chasing in various 3.9 kernels is
apparently
fixed by the commit in the title (c9c390bb5535380d40614571894ef0c00bc026ff).
Apparently being the operative word.
This commit avoids the entire module insert
On Sat, Jun 01, 2013 at 06:15:55PM +0200, Robert Richter wrote:
Instead I reviewed the code while developing it with certain goals in
mind. Most changes I found necessary while building and running a
modified version during development. That never could be found in a
patch review. These
During booting kernel 3.9.4 on an AOpen i915GMm-hfs, Pentium-M Dothan 2GHz, 2GB
RAM
system the pipe_off wait timed out warning was triggered. Reproducibility:
low, problem was
found only once.
cu,
Knut
[ 16.276006] =
[ 16.276006] [ INFO:
On Fri, May 31, 2013 at 10:27:26AM -0500, Mark Langsdorf wrote:
The Calxeda SATA phy intermittently fails to bring up a link with Gen3
Retrying the phy hard reset can work around the issue, but the drive
may fail again. In less than 150 out of 15000 test runs, it took more
than 10 tries for
Hi Mark,
On Sun, Jun 2, 2013 at 12:06 AM, Mark Brown broo...@kernel.org wrote:
On Sat, Jun 01, 2013 at 11:29:23PM +0200, Geert Uytterhoeven wrote:
On Sat, Jun 1, 2013 at 11:10 PM, Mark Brown broo...@kernel.org wrote:
Sorry, I sent it to your Wolfson address, as suggested by
On Sun, Jun 02, 2013 at 12:51:25AM +0530, Raghavendra K T wrote:
This series replaces the existing paravirtualized spinlock mechanism
with a paravirtualized ticketlock mechanism. The series provides
implementation for both Xen and KVM.
High level question here. We have a big hope for
Another week, another -rc. But this time (at least for now) only as a git
tree - for people actually using the tar-balls and patches, I apologize,
but I'm a complete moron, and didn't install kup, its perl dependencies,
and my kup release scripts on the pixel before the trip.
And while I can
Hello Thomas,
additionally to provide a proper log message it is a usual to provide the
coccinelle expression that found the source to be changed.
http://lwn.net/Articles/315686/
E.g. like these
http://marc.info/?l=linux-netdevm=135081679626023w=2
Certain watchdog drivers use a timer to keep kicking the watchdog at
a rate of 0.5s (HZ/2) untill userspace times out.They do this as
we can't guarantee that watchdog will be pinged fast enough
for all system loads, especially if timeout is configured for
less than or equal to 1 second(basically
On Sat, Jun 01, 2013 at 11:42:11AM +0200, Thomas Meyer wrote:
Signed-off-by: Thomas Meyer tho...@m3y3r.de
---
diff -u -p a/arch/x86/kernel/microcode_amd.c b/arch/x86/kernel/microcode_amd.c
--- a/arch/x86/kernel/microcode_amd.c
+++ b/arch/x86/kernel/microcode_amd.c
@@ -345,7 +345,7 @@
On Fri, May 31, 2013 at 05:27:49PM -0400, Steven Rostedt wrote:
Paul,
I've been debugging the last couple of days why my tests have been
locking up. One of my tracing tests, runs all available tracers. The
lockup always happened with the mmiotrace, which is used to trace
interactions
On Sun, Jun 2, 2013 at 3:43 PM, anish kumar anish198519851...@gmail.com wrote:
Certain watchdog drivers use a timer to keep kicking the watchdog at
a rate of 0.5s (HZ/2) untill userspace times out.They do this as
we can't guarantee that watchdog will be pinged fast enough
for all system loads,
On Sun, Jun 02, 2013 at 10:04:42AM +0200, Geert Uytterhoeven wrote:
But in this case, the commit was commited with a SoB using your old
email address, only 5 days ago. So you may still have a stale
.gitconfig somewhere:
No, this is correct. I only finished working at Wolfson on Friday and
On Sat, Jun 1, 2013 at 10:27 AM, Jingoo Han jg1@samsung.com wrote:
The usage of strict_strtoul() is not preferred, because
strict_strtoul() is obsolete. Thus, kstrtoul() should be
used.
--- a/drivers/power/ab8500_fg.c
+++ b/drivers/power/ab8500_fg.c
@@ -2467,7 +2467,7 @@ static ssize_t
On Sat, Jun 1, 2013 at 10:13 AM, Jingoo Han jg1@samsung.com wrote:
The usage of strict_strtoul() is not preferred, because
strict_strtoul() is obsolete. Thus, kstrtoul() should be
used.
--- a/drivers/mfd/aat2870-core.c
+++ b/drivers/mfd/aat2870-core.c
@@ -312,7 +312,7 @@ static ssize_t
http://www.arkansascollisionrepair.com/hgrhj/qbpbafrnoobol.tvpcyluf.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at
On Fri, May 31, 2013 at 05:53:24PM +0800, Jason Wang wrote:
This patch adds TUNSETQUEUE ioctl to let userspace can temporarily disable or
enable a queue of macvtap. This is used to be compatible at API layer of
tuntap
to simplify the userspace to manage the queues.
This is done by split
On Sat, Jun 1, 2013 at 10:31 AM, Jingoo Han jg1@samsung.com wrote:
The usage of strict_strtoul() is not preferred, because
strict_strtoul() is obsolete. Thus, kstrtoul() should be
used.
--- a/drivers/rtc/rtc-pcf2123.c
+++ b/drivers/rtc/rtc-pcf2123.c
@@ -94,7 +94,7 @@ static ssize_t
On Fri, May 31, 2013 at 11:30:24PM +0100, Grant Likely wrote:
On Fri, 31 May 2013 14:59:11 +0200, Alexander Gordeev agord...@redhat.com
wrote:
What exactly is the problem that you're trying to solve with this patch?
It's not clear from the description.
Hi Grant,
Thanks for the
On Sat, Jun 1, 2013 at 10:37 AM, Jingoo Han jg1@samsung.com wrote:
The usage of strict_strtoul() is not preferred, because
strict_strtoul() is obsolete. Thus, kstrtoul() should be
used.
--- a/drivers/misc/apds9802als.c
+++ b/drivers/misc/apds9802als.c
@@ -126,7 +126,7 @@ static ssize_t
On Sat, Jun 1, 2013 at 7:11 AM, Joe Perches j...@perches.com wrote:
Add a new pkt_notice macro to prefix the name to the logging output.
One nitpick below.
--- a/drivers/block/pktcdvd.c
+++ b/drivers/block/pktcdvd.c
@@ -71,17 +71,19 @@
#define DRIVER_NAMEpktcdvd
+#define pkt_err(pd,
On Sun, 2013-06-02 at 15:12 +0300, Andy Shevchenko wrote:
On Sat, Jun 1, 2013 at 7:11 AM, Joe Perches j...@perches.com wrote:
Add a new pkt_notice macro to prefix the name to the logging output.
One nitpick below.
--- a/drivers/block/pktcdvd.c
[]
+#define pkt_err(pd, fmt, ...)
On Sun, Jun 02, 2013 at 12:37:21AM +0200, Arnd Bergmann wrote:
I got compile errors with the cw1200, which has lead me to take a
closer look. It seems the driver still has a number of issues,
and this addresses some of them and marks others as FIXME:
In short, NACK, at least not as posted.
From: Borislav Petkov b...@suse.de
Hi all,
this one is 64-bit only for now and it has been tested only in kvm with
OVMF.
Keeping in mind the ihnerent efi b0rkedness left and right, I'd like to
be very cautious and conservative with this and not hurry anything until
it has been actually very
From: Borislav Petkov b...@suse.de
Add the ability to map pages in an arbitrary pgd.
Signed-off-by: Borislav Petkov b...@suse.de
---
arch/x86/include/asm/pgtable_types.h | 3 +-
arch/x86/mm/pageattr.c | 80
2 files changed, 65 insertions(+),
From: Borislav Petkov b...@suse.de
.. for passing miscellaneous options from the kernel command line.
Signed-off-by: Borislav Petkov b...@suse.de
---
arch/x86/platform/efi/efi.c | 16
1 file changed, 16 insertions(+)
diff --git a/arch/x86/platform/efi/efi.c
From: Borislav Petkov b...@suse.de
Due to the braindead design of EFI, we cannot map runtime services more
than once for the duration of a booted system. Thus, if we want to use
EFI runtime services in a kexec'ed kernel, maybe the only possible and
sensible approach would be to map them 1:1 so
From: Borislav Petkov b...@suse.de
... to void * like the boot services and lose all the void * casts. No
functionality change.
Signed-off-by: Borislav Petkov b...@suse.de
---
arch/x86/boot/compressed/eboot.c | 2 +-
arch/x86/include/asm/efi.h | 28 ++--
http://videlex.pl/ixzuau/nldnuoakeqgkuef.odzcfedd
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On Sun, Jun 02, 2013 at 08:29:54AM -0400, Solomon Peachy wrote:
* Add comments about passing GPIO numbers in platform_data:
You should not use IORESOURCE_IO, which is for legacy ISA
I/O ports on PCs, not for GPIOs.
Fair enough. The use of resources was something already in the driver
Maybe wait and see if %pa gets more usage and if the discussion comes up again.
Best regards,
Emil
On Sat, Jun 01, 2013 at 04:22:18PM -0700, Joe Perches wrote:
On Sun, 2013-06-02 at 01:06 +0200, Emil Goode wrote:
Maybe there should be another format specifier %da and Randy's
clarifying
On Sunday 02 June 2013 08:29:54 Solomon Peachy wrote:
On Sun, Jun 02, 2013 at 12:37:21AM +0200, Arnd Bergmann wrote:
I got compile errors with the cw1200, which has lead me to take a
closer look. It seems the driver still has a number of issues,
and this addresses some of them and marks
On 30/05/2013 14:40, Eliezer Tamir wrote:
more fixes.
Thank you all for your input.
-Eliezer
change log:
v7
- suggested by Ben Hutchings and Eric Dumazet:
type fixes, static for globals in net/core.c,
avoid napi_id collisions in napi_hash_add()
Dave,
Please tell my how you think I
On Sat, Jun 01, 2013 at 07:54:25PM -0700, Paul E. McKenney wrote:
On Fri, May 31, 2013 at 05:27:49PM -0400, Steven Rostedt wrote:
Paul,
I've been debugging the last couple of days why my tests have been
locking up. One of my tracing tests, runs all available tracers. The
lockup always
On Sun, Jun 02, 2013 at 03:59:12PM +0200, Arnd Bergmann wrote:
The driver doesn't reliably build, and I'm trying to fix it.
From my perspective, we can just mark it 'depends on !ARM'
to get it off my radar, but other people are doing build
testing on x86 and will run into the same issues.
The current radeon driver initialization routines, when using KMS, are written
so that the IRQ installation routine is called before initializing the WB buffer
and the CP rings. With some ASICs, though, the IRQ routine tries to access the
GFX_INDEX ring causing a call to RREG32 with the value of
From: Oliver Schinagl oli...@schinagl.nl
This should add support for the sunxi-sid driver to the device table for sun4i
and sun5i
Signed-off-by: Oliver Schinagl oli...@schinagl.nl
---
arch/arm/boot/dts/sun4i-a10.dtsi | 5 +
arch/arm/boot/dts/sun5i-a13.dtsi | 5 +
2 files changed, 10
From: Oliver Schinagl oli...@schinagl.nl
Changes from v1:
* Renamed the sys-fs exported key to eeprom, since it really a read-only eeprom
* Removed mention of sun[67]i since we haven't tested those
* Fixed up mistakes in comments
* Removed PAGE_SIZE references, since this is a binary only driver
From: Oliver Schinagl oli...@schinagl.nl
Allwinner has electric fuses (efuse) on their line of chips. This driver
reads those fuses, seeds the kernel entropy and exports them as a sysfs node.
These fuses are most likly to be programmed at the factory, encoding
things like Chip ID, some sort of
On Sun, Jun 02, 2013 at 04:58:49PM +0200, Oliver Schinagl wrote:
+#include asm/io.h
We have an include file called linux/io.h. Please use linux/*.h files which
include asm/*.h files in preference to directly using asm/*.h.
In fact, no driver should include an asm/*.h header.
+#include
On 05/24/2013 03:42 AM, Jonghwan Choi wrote:
This patch looks like it should be in the 3.9-stable tree, should we apply
it?
It's a pretty unlikely problem to hit in reality so up to you on whether
you think it worth picking up. Also note that only the -EINVAL bit
is actually a fix. The rest of
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
On 06/02/13 17:09, Russell King - ARM Linux wrote:
On Sun, Jun 02, 2013 at 04:58:49PM +0200, Oliver Schinagl wrote:
+#include asm/io.h
We have an include file called linux/io.h. Please use linux/*.h files which
include asm/*.h files in preference to directly using asm/*.h.
In fact, no
After quick testing it looks like this fixes the boot problem.
Boots with grub2 (EFI stubs), grub (no EFI stubs) and elilo.
Thanks!
On Sat, Jun 01, 2013 at 04:06:20PM -0400, Matthew Garrett wrote:
This patch reworks the UEFI anti-bricking code, including an effective
reversion of cc5a080c and
On Sun, Jun 2, 2013 at 1:07 AM, Gleb Natapov g...@redhat.com wrote:
High level question here. We have a big hope for Preemptable Ticket
Spinlock patch series by Jiannan Ouyang to solve most, if not all,
ticketing spinlocks in overcommit scenarios problem without need for PV.
So how this patch
On Sun, Jun 2, 2013 at 12:56 PM, Alexander Gordeev agord...@redhat.com wrote:
On Fri, May 31, 2013 at 11:30:24PM +0100, Grant Likely wrote:
On Fri, 31 May 2013 14:59:11 +0200, Alexander Gordeev agord...@redhat.com
wrote:
What exactly is the problem that you're trying to solve with this patch?
On Thu, May 30, 2013 at 04:35:55PM +0200, Paolo Bonzini wrote:
The x86-64 extended low-byte registers were fetched correctly from reg,
but not from mod/rm.
This fixes another bug in the boot of RHEL5.9 64-bit, but it is still
not enough.
Did I missed unit test patch? :)
Cc:
Hi Linus,
Please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/cjb/mmc.git
tags/mmc-fixes-for-3.10-rc5
to receive MMC fixes for 3.10-rc5. There are no merge conflicts, and
the patches have been tested in linux-next. Thanks.
The following changes since commit
On 06/02/13 01:45, Linus Torvalds wrote:
Another week, another -rc. But this time (at least for now) only as a git
tree - for people actually using the tar-balls and patches, I apologize,
but I'm a complete moron, and didn't install kup, its perl dependencies,
and my kup release scripts
On Sun, Jun 2, 2013 at 4:47 PM, Solomon Peachy pi...@shaftnet.org wrote:
In fact my mobile phone has a cw1200 chip that was working until
recently. Now it just crashes when I do 'ifconfig wlan0 up'
or enable WLAN in the Android settings menu. :(
I'm not blaming you for that ;-)
What model,
On Tue, May 28, 2013 at 11:38 AM, Geert Uytterhoeven
ge...@linux-m68k.org wrote:
On Thu, May 23, 2013 at 10:09 PM, Geert Uytterhoeven
ge...@linux-m68k.org wrote:
I created a branch where I collected several exotic architecture fixes
(and a few
other trivial fixes):
On 29 May 2013 01:29, Rafael J. Wysocki r...@sisk.pl wrote:
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
The runtime idle helper routine, rpm_idle(), currently ignores
return values from .runtime_idle() callbacks executed by it.
However, it turns out that many subsystems use the
1. register_wide_hw_breakpoint() can use unregister_ if failure,
no need to duplicate the code.
2. struct perf_event **pevent adds the unnecesary lever of
indirection and complication, use per_cpu(*cpu_events, cpu).
Signed-off-by: Oleg Nesterov o...@redhat.com
---
Hello.
More cleanups, on top of [PATCH 0/3] hw_breakpoint: cleanups.
Oleg.
kernel/events/hw_breakpoint.c | 103 +++--
1 files changed, 47 insertions(+), 56 deletions(-)
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of
This patch simply moves all per-cpu variables into the new single
per-cpu struct bp_cpuinfo.
To me this looks more logical and clean, but this can also simplify
the further potential changes. In particular, I do not think this
memory should be per-cpu, it is never used locally. After this
change
From: Eliezer Tamir eliezer.ta...@linux.intel.com
Date: Sun, 02 Jun 2013 17:02:33 +0300
Or I can submit a v8 with those fixes.
Please submit v8
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at
From: Rafael J. Wysocki rafael.j.wyso...@intel.com
The runtime idle helper routine, rpm_idle(), currently ignores
return values from .runtime_idle() callbacks executed by it.
However, it turns out that many subsystems use
pm_generic_runtime_idle() which checks the return value of the
driver's
From: Alan Stern st...@rowland.harvard.edu
Runtime PM documentation needs to be updated after the previous
change of the rpm_idle() behavior, so modify it as appropriate.
[rjw: Subject and changelog]
Signed-off-by: Alan Stern st...@rowland.harvard.edu
Index:
On Thursday, May 30, 2013 01:08:08 PM Alan Stern wrote:
On Thu, 30 May 2013, Rafael J. Wysocki wrote:
Since you're making this change, wouldn't it be a good idea to adopt
Mika's original suggestion and turn on the RPM_AUTO bit in rpmflags
when the use_autosuspend flag is set?
I'm
We need to map boot services regions during startup in order to avoid
firmware bugs, but we shouldn't be passing those regions to
SetVirtualAddressMap(). Ensure that we're only passing regions that are
marked as being mapped at runtime.
Signed-off-by: Matthew Garrett matthew.garr...@nebula.com
This can be used for cache types for which syncing values one by one is
equally efficient as syncing a range, such as the flat cache.
Signed-off-by: Maarten ter Huurne maar...@treewalker.org
---
drivers/base/regmap/regcache.c | 46
1 file changed, 42
FireWire upper layer drivers are converted from generic
struct driver.probe() and .remove()
to bus-specific
struct fw_driver.probe() and .remove().
The new .probe() adds a const struct ieee1394_device_id *id argument,
indicating the entry in the driver's device identifiers table which
After all drivers being converted to bus-specific .probe/.remove methods,
remove support of the obsolete generic methods.
Signed-off-by: Stefan Richter stef...@s5r6.in-berlin.de
---
To be merged maybe one release cycle after patch firewire: introduce
fw_driver.probe and .remove methods.
On Mon, Jun 03, 2013 at 12:27:49AM +0200, Stefan Richter wrote:
FireWire upper layer drivers are converted from generic
struct driver.probe() and .remove()
to bus-specific
struct fw_driver.probe() and .remove().
The new .probe() adds a const struct ieee1394_device_id *id argument,
I've just run Windows 8 under a hacked up copy of OVMF that dumps the
data passed to SetVirtualAddressMap. It seems that Windows *is* mapping
the runtime services to higher addresses - so presumably the 1:1 mapping
is in addition to the virtual mapping.
--
Matthew Garrett |
Thanks for the kind reply.
Best Regards.~
-Original Message-
From: Jonathan Cameron [mailto:ji...@jic23.retrosnub.co.uk]
Sent: Monday, June 03, 2013 12:13 AM
To: Jonghwan Choi
Cc: linux-kernel@vger.kernel.org; sta...@vger.kernel.org; 'Wei Yongjun';
'Jonathan Cameron'
Subject: Re:
Uarts on all recent Rockchip SoCs are Synopsis DesignWare 8250 types.
Only their addresses vary very much.
This patch adds the necessary definitions to use any of the uart ports
for early debug purposes.
Signed-off-by: Heiko Stuebner he...@sntech.de
---
arch/arm/Kconfig.debug| 34
This adds basic support for clocks on Rockchip rk3066 SoCs.
The clock handling thru small dt nodes is heavily inspired by the
sunxi clk code.
The clock specifiers are named as x-cortex-a9-x, because the clock
semantics are the same thru the whole cortex-a9 series (rk30xx,
rk3188, rk2928; but not
This adds a generic devicetree board file and a dtsi for boards
based on the RK3066a SoCs from Rockchip.
Apart from the generic parts (gic, clocks, pinctrl) the only components
currently supported are the timers, uarts and mmc ports (all DesignWare-
based).
Signed-off-by: Heiko Stuebner
On Thu, 2013-05-30 at 12:25 +0400, Roman Gushchin wrote:
On 29.05.2013 23:06, Eric Dumazet wrote:
On Wed, 2013-05-29 at 14:09 +0400, Roman Gushchin wrote:
True, these lookup functions are usually structured the same around the
hlist_nulls_for_each_entry_rcu() loop.
A barrier() right
On Jun 02 Greg Kroah-Hartman wrote:
On Mon, Jun 03, 2013 at 12:27:49AM +0200, Stefan Richter wrote:
Although all in-tree drivers are being converted to the new methods,
support for the old methods is left in place for the time being, aiming
to avoid conflicts if/when new drivers are being
Add the possibility to get the clock-frequency from a timer clock instead
of specifying it as dt property. Additionally also add the possibility
to also define a controlling periphal clock for the timer block.
The clock-frequency property is kept to act as fallback if no clocks
are specified.
This driver adds support the Cortex-A9 based SoCs from Rockchip,
so at least the RK2928, RK3066 (a and b) and RK3188.
Earlier Rockchip SoCs seem to use similar mechanics for gpio
handling so should be supportable with relative small changes.
Pull handling on the rk3188 is currently a stub, due to
Prepare your eggs and tomatoes please, I got myself a second playground ;-) .
As the title implies this series adds basic support for Rockchip's Cortex-A9
SoCs, like the RK3066 used in many cheaper tablets.
On the periphal side it's very lightweight, as it seems someone from Rockchip
was
SoCs like the Rockchip Cortex-A9 ones contain divider some clocks
that use the regular mechanisms for storage but allow only even
dividers and 1 to be used.
Therefore add a flag that lets _is_valid_div limit the valid dividers
to these values. _get_maxdiv is also adapted to return even values
for
There exist platforms, namely at least all Rockchip Cortex-A9 based ones,
that don't use the paradigm of reading-changing-writing the register contents,
but instead only write the changes to the register with a mask that indicates
the changed bits.
This patch adds flags and code to support the
Currently the dw_apb_timer always expects a separate special timer to be
availbable for the sched_clock. Some devices using dw_apb_timers do not
have the sptimer but can use the clocksource as sched_clock.
Therefore this patch adds using the clocksource timer as
a fallback if no usable sched timer
Cortex-A9 SoCs from Rockchip use a slightly modified variant of dw_mmc
controllers that seems to require the SDMMC_CMD_USE_HOLD_REG bit to
always be set.
There also seem to be no other modifications (additional register etc)
present, so to keep the footprint low, add this small variant to the
dw_mci_pltfm_remove gets exported and used by dw_mmc-exynos, so should
not be static.
Signed-off-by: Heiko Stuebner he...@sntech.de
---
drivers/mmc/host/dw_mmc-pltfm.c |2 +-
1 files changed, 1 insertions(+), 1 deletions(-)
diff --git a/drivers/mmc/host/dw_mmc-pltfm.c
The Nomadik HW RNG driver has seen some rust and is not preparing
the clock before use. Fix this up so we get rid of runtime
complaints from the clock subsystem.
Signed-off-by: Linus Walleij linus.wall...@linaro.org
---
drivers/char/hw_random/nomadik-rng.c | 2 +-
1 file changed, 1 insertion(+),
在 2013-05-31五的 16:02 -0700，Andrew Morton写道：
On Thu, 30 May 2013 15:58:05 +0800 liguang lig.f...@cn.fujitsu.com wrote:
--- a/include/linux/reboot.h
+++ b/include/linux/reboot.h
@@ -35,7 +35,7 @@ extern void kernel_restart(char *cmd);
extern void kernel_halt(void);
extern void
Hi Grant,
Today's linux-next merge of the devicetree-current tree got a conflict in
scripts/Makefile.lib between commit ad06156876c0 (kbuild: Don't assume dts
files live in arch/*/boot/dts) from the tree and commit 2c302eb0a6a5
(kbuild: make sure we clean up DTB temporary files) from the
On Tue, May 14, 2013 at 12:49:44PM +0100, majianpeng wrote:
Signed-off-by: Jianpeng Ma majianp...@gmail.com
---
mm/kmemleak.c | 8 +---
1 file changed, 1 insertion(+), 7 deletions(-)
diff --git a/mm/kmemleak.c b/mm/kmemleak.c
index b1525db..f0ece93 100644
--- a/mm/kmemleak.c
+++
On Fri, 2013-05-31 at 16:02 -0700, Andrew Morton wrote:
there's no rule
which states that sizeof(bool) must equal sizeof(int).
For gcc, sizeof(_Bool) isn't sizeof(int) so it would
work for one endian but not the other.
gcc has sizeof(_Bool) == sizeof(unsigned char)
--
To unsubscribe from this
The bios may clear the rtc control register when resuming the system. Since the
cmos interrupt handler may now be run before the rtc_cmos is resumed, this can
cause the interrupt handler to ignore an alarm since the alarm bit is not set in
the rtc control register. To work around this, check if
Hi Geert,
Today's linux-next merge of the m68k tree got a conflict in
arch/cris/arch-v32/drivers/Kconfig between commit aca30fdc0fb6 (CRIS:
drop unused Kconfig symbols) from the cris tree and commit 6b8faf979bca
(cris: Switch cris to drivers/Kconfig) from the m68k tree.
Thanks for the heads up
We kernel guys have been asking the distros to ship 64-bit kernels even
in their 32-bit distros for many years, but concerns of compat issues
and the desire to deprecate 32-bit userspace seems to have kept that
from happening.
And now there is another reason: to call 64-bit EFI runtime
1 - 100 of 342 matches
Mail list logo
