On Mon, 23 Feb 2015, Brian Norris wrote:
> On Tue, Feb 10, 2015 at 05:04:33PM +0800, Lee Jones wrote:
> > On Thu, 05 Feb 2015, Brian Norris wrote:
> > > On Wed, Jan 21, 2015 at 01:02:04PM +, Lee Jones wrote:
> > > > On Mon, 12 Jan 2015, Brian Norris wrote:
> > > > > On Mon, Dec 15, 2014 at 11:5
Hi Zhangfei,
On 22/02/15 05:10, zhangfei wrote:
> Hi, Balbi
>
> On 02/22/2015 12:21 AM, Felipe Balbi wrote:
>> Hi,
>>
>> On Sat, Feb 21, 2015 at 11:03:05PM +0800, zhangfei wrote:
>>> +static void hi6220_start_peripheral(struct hi6220_priv *priv, bool on)
>>> +{
>>> +struct usb_otg
From: Tien Hock Loh
Adds a new driver for Altera soft GPIO IP. The driver is able to do
read/write and allows GPIO to be a interrupt controller.
Tested on Altera GHRD on interrupt handling and IO.
Signed-off-by: Tien Hock Loh
---
MAINTAINERS| 6 +
drivers/gpio/Kconfig
This patch adds support for Intel's FieldsPeak NFC solution.
The device is enumerated with ACPI and platform init.
In order to implement the driver the nci_core_conn_create was
modified in order to report the ID of the newly created connection.
Fixed a bug that prevented to close a connection from
diff --git a/Makefile b/Makefile
index cc7535a0f9d0..eff7a4bcda71 100644
--- a/Makefile
+++ b/Makefile
@@ -1,7 +1,7 @@
VERSION = 3
PATCHLEVEL = 16
SUBLEVEL = 7
-EXTRAVERSION =-ckt6
+EXTRAVERSION =-ckt7
NAME = Museum of Fishiegoodies
# *DOCUMENTATION*
diff --git a/arch/arm/boot/dts/exynos4.dt
nci_send_cmd was exported in order to send commands to the device from
the driver. For the firmware update the driver may use nci_send_data.
Signed-off-by: Robert Dolca
---
net/nfc/nci/core.c | 1 +
net/nfc/nci/data.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/net/nfc/nci/core.c b/net
In order to communicate with the device during the setup
phase, the driver may need to initialize the device. After
the setup is done the driver should reset the device to leave
it in the same state that it was before the setup function
call.
Signed-off-by: Robert Dolca
---
include/net/nfc/nci_c
If the previous nci_request (NCI reset) failed the setup function
was being called anyway. It shouldn't be called if the reset failed.
The result of the setup function is taken into consideration. If it
fails the init should fail.
Signed-off-by: Robert Dolca
---
net/nfc/nci/core.c | 4 ++--
1 f
nci_core_conn_create not has a new parameter so it can return
the ID of the new connection. Also not you can't call nci_core_conn_create
without waiting the answer for the previous call.
Signed-off-by: Robert Dolca
---
drivers/nfc/st21nfcb/st21nfcb_se.c | 2 +-
include/net/nfc/nci_core.h
FDP driver needs to send the firmware as regular packets
(not fragmented). That's whay the driver should have a way to
get the max packet size for a given connection.
Signed-off-by: Robert Dolca
---
include/net/nfc/nci_core.h | 1 +
net/nfc/nci/data.c | 12
2 files changed,
The device can be enumerated using ACPI using the id INT339A.
The 1st GPIO is the IRQ and the 2nd is the RESET pin.
I can be also enumerated using platform init.
Signed-off-by: Robert Dolca
---
drivers/nfc/Kconfig | 1 +
drivers/nfc/fdp/Kconfig | 22 ++
drivers/nfc/fdp
This patch adds nci_request_driver and nci_req_complete_driver
as a wrapper for __nci_request. When nci_req_complete_driver is
called it also sets cmd_cnt to 1. This is done because the response is not
sent to the NFC subsystem so cmd_cnt is not decremented there.
nci_send_cmd was previously expor
By calling __nci_request instead of nci_request allows the driver to use
the function while initializing the device (setup stage)
Signed-off-by: Robert Dolca
---
net/nfc/nci/core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/net/nfc/nci/core.c b/net/nfc/nci/core.c
index 9
I am announcing the release of the Linux 3.16.7-ckt7 kernel.
The updated 3.16.y-ckt tree can be found at:
git://kernel.ubuntu.com/ubuntu/linux.git linux-3.16.y
and can be browsed at:
http://kernel.ubuntu.com/git?p=ubuntu/linux.git;h=refs/heads/linux-3.16.y;a=shortlog
The diff from v3.16.7-c
Re-work and fix handling of errors when retrieving power supply
properties:
1. Return errno values directly from get_property() instead of storing
'unknown' as intval for given property.
2. Handle regmap_read() errors when getting 'online' and 'present'
proprties and return errno code. Prev
Re-work and fix handling of errors when retrieving power supply
properties:
1. Return errno values directly from get_property() instead of
storing 'unknown' as intval for given property.
2. Handle regmap_read() errors and return errno code. Previously the
regmap_read() return code was ignor
Mixing IRQF_NO_SUSPEND and !IRQF_NO_SUSPEND on the same IRQ line is highly
discouraged, but in some cases (IRQ shared by a timer and other devices)
you don't have any other choice.
Since some devices sharing the IRQ line might tag it as a wakeup source,
you might end up with your handler that reque
From: Ingo Molnar
...
> So why not trylock and time out here after a few seconds,
> instead of indefinitely supressing some potentially vital
> output due to some other CPU crashing/locking with the lock
> held?
I've used that for status requests that usually lock a table
to get a consistent view.
On Tue, Feb 24, 2015 at 08:15:35AM +, Naoya Horiguchi wrote:
> Let me update my explanation about the problem. I wrote the description about
> race window of nmi shoot down threads. That's not wrong, but that's only the
> part of the problem. The more suitable description is that all "shot down
Get a loan here at low rate
Amount Needed:
Loan Duration:
Phone Number:
Country
--
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
Add two helper functions to help drivers that are sharing IRQs with
timer devices (or other devices setting the IRQF_NO_SUSPEND flag) deal
with system wakeup and state detection.
Such drivers should expect their IRQ handler to be called in 2 different
contexts:
1/ the system is resumed and the han
Hello,
I put the IRQF_NO_SUSPEND_SAFE/IRQF_TIMER_SIBLING_OK/WHATEVER_NAME_YOU_CHOOSE
debate aside to concentrate on another problem pointed out by Rafael and
Mark: the fact that we cannot mix IRQF_NO_SUSPEND and wakeup sources on
a shared IRQ line.
This is because the wakeup code is prevailing th
The IRQ line used by the RTC device is often shared with the system timer
(PIT) on at91 platforms.
Since timers are registering their handlers with IRQF_NO_SUSPEND, we should
expect being called in suspended state, and properly wake the system up
when this is the case.
Signed-off-by: Boris Brezill
Consolidate regmap_read() and regmap_write() into one
regmap_update_bits() call. This is more readable and safer because
regmap's mutex will prevent any concurrent access to modified registers
(the concurrent access could happen through max17042_init_chip() in
scheduled work).
Signed-off-by: Krzys
The scheduled work in max17040_battery driver reads device parameters
and stores them in memory. Any CPU could do that so use system efficient
workqueues to limit unnecessary CPU wake ups.
Signed-off-by: Krzysztof Kozlowski
---
drivers/power/max17040_battery.c | 9 ++---
1 file changed, 6 in
Remove caching of charging and battery states in driver's state
container because the cached value was not used later.
Signed-off-by: Krzysztof Kozlowski
---
drivers/power/max14577_charger.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/drivers/power/max14577_charger.c b/drivers/power/
From: Tien Hock Loh
Adds a new device tree binding and driver for Altera soft GPIO IP.
The driver is able to do read/write and allows GPIO to be a interrupt
controller.
Tested on Altera GHRD on interrupt handling and IO.
v10:
Updated conflicting device tree parameters
Removed unused headers
Us
From: Tien Hock Loh
Adds a new driver device tree binding for Altera soft GPIO IP
Signed-off-by: Tien Hock Loh
---
.../devicetree/bindings/gpio/gpio-altera.txt | 43 ++
1 file changed, 43 insertions(+)
create mode 100644 Documentation/devicetree/bindings/gpio/gpio-al
The regmap_config struct may be const because it is not modified by the
driver and regmap_init() accepts pointer to const.
Signed-off-by: Krzysztof Kozlowski
---
drivers/power/rt5033_battery.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/power/rt5033_battery.c b/dr
On Tuesday 24 February 2015 18:01:27 Chanwoo Choi wrote:
> On 02/24/2015 05:33 PM, Arnd Bergmann wrote:
> > On Tuesday 24 February 2015 14:16:45 Chanwoo Choi wrote:
> >> This patch adds new Exynos5433 dtsi to support 64-bit Exynos5433 SoC based
> >> on
> >> Octal core CPUs (quad Cortex-A57 and qua
The regmap_config struct may be const because it is not modified by the
driver and regmap_init() accepts pointer to const.
Signed-off-by: Krzysztof Kozlowski
---
drivers/rtc/rtc-ab-b5ze-s3.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/rtc/rtc-ab-b5ze-s3.c b/driver
On Tuesday 24 February 2015 17:52:01 Chanwoo Choi wrote:
>
> But, I have a question.
> If we put the aliases into the board dts file instaed of SoC dtsi,
> each board dts file may use the different alias name about same phandle.
Yes, that is the idea. In particular with the uarts, the intention i
* Vojtech Pavlik wrote:
> On Sun, Feb 22, 2015 at 03:01:48PM -0800, Andrew Morton wrote:
>
> > On Sun, 22 Feb 2015 20:13:28 +0100 (CET) Jiri Kosina
> > wrote:
> >
> > > But if you ask the folks who are hungry for live bug
> > > patching, they wouldn't care.
> > >
> > > You mentioned "10 se
On 23/02/15 21:38, David Miller wrote:
From: Stathis Voukelatos
Date: Mon, 23 Feb 2015 14:26:22 +
Driver for the Ethernet Mii packet sniffer H/W module found in
the IMG Pistachio SoC.
Signed-off-by: Stathis Voukelatos
You really have to explain what this thing does, how it is used,
wh
The regmap_access_table and regmap_config structures may be const
because they are not modified by the driver and regmap_init() accepts
pointer to const.
Signed-off-by: Krzysztof Kozlowski
---
drivers/staging/iio/magnetometer/hmc5843_i2c.c | 8
drivers/staging/iio/magnetometer/hmc5843_s
The regmap_config struct may be const because it is not modified by the
driver and regmap_init() accepts pointer to const.
Signed-off-by: Krzysztof Kozlowski
---
drivers/iio/light/jsa1212.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/iio/light/jsa1212.c b/drivers/
On Mon, 23 Feb 2015, Brian Norris wrote:
> On Tue, Feb 10, 2015 at 03:46:34PM +0800, Lee Jones wrote:
> > On Thu, 05 Feb 2015, Brian Norris wrote:
> > > On Wed, Jan 21, 2015 at 03:24:20PM +, Lee Jones wrote:
> > > > To trim down on the amount of properties used by this driver and to
> > > > c
The regmap_config struct may be const because it is not modified by the
driver and regmap_init() accepts pointer to const.
Signed-off-by: Krzysztof Kozlowski
---
drivers/clk/clk-si570.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clk/clk-si570.c b/drivers/clk/clk-
The regmap_config struct may be const because it is not modified by the
driver and regmap_init() accepts pointer to const.
Signed-off-by: Krzysztof Kozlowski
---
drivers/mfd/da9150-core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/mfd/da9150-core.c b/drivers/mfd/
The regmap_config struct may be const because it is not modified by the
driver and regmap_init() accepts pointer to const.
Signed-off-by: Krzysztof Kozlowski
---
drivers/pwm/pwm-pca9685.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pwm/pwm-pca9685.c b/drivers/pwm/
>> Some architectures already have their own recursive
>> locking for oopses and we have another version for
>> serialising dump_stack.
>>
>> Create a common version and use it everywhere (oopses,
>> BUGs, WARNs, dump_stack, soft lockups and hard lockups).
>
> Dunno. I've had cases where the simult
The regmap_config struct may be const because it is not modified by the
driver and regmap_init() accepts pointer to const.
Signed-off-by: Krzysztof Kozlowski
---
drivers/clk/clk-cdce706.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clk/clk-cdce706.c b/drivers/clk/
The regmap_config struct may be const because it is not modified by the
driver and regmap_init() accepts pointer to const.
Make function rockchip_get_core_reset() static because it is not used
outside of the platsmp.c file.
Signed-off-by: Krzysztof Kozlowski
---
arch/arm/mach-rockchip/platsmp.c
The regmap_config struct may be const because it is not modified by the
driver and regmap_init() accepts pointer to const.
Replace doubled const in the arrays of clock names with proper const
pointer to const data. This fixes the warnings:
drivers/clk/clk-si5351.c:71:25: warning: duplicate const
Hi Michael,
On Tue, Feb 24, 2015 at 5:52 AM, Michael Ellerman wrote:
>> > + error: book3s_64_vio_hv.c: undefined reference to
>> > `power7_wakeup_loss': => .text+0x408)
>>
>> pseries_defconfig
>
> This one is actually from pseries_defconfig+POWERNV=n, so I think I
Thanks!
> broke your scrip
commit 303e4697e762dc92a40405f4e4b8aac02cd0d70b
OMAPDSS: rename display-sysfs 'name' entry
broke the xorg X server on my device as it couldn't find the display
any more. It needs the 'name' file and now there isn't one.
That commit claims that 'name' is not compatible with i2c or spi.
i2c
On 23/02/15 21:37, David Miller wrote:
From: Stathis Voukelatos
Date: Mon, 23 Feb 2015 14:26:21 +
+ spin_lock_irqsave(&priv->lock, flags);
+ /* Stop the hardware */
+ sch->stop(sch);
+ /* Set the new command pattern */
+ ret = sch->set_pattern(sch, skb->data
This patch add the CLKOUT register source clock as xusbxti in
PMU (Power Management Unit) dt node on Exynos3250.
Cc: Kukjin Kim
Signed-off-by: Inha Song
---
arch/arm/boot/dts/exynos3250.dtsi | 3 +++
1 file changed, 3 insertions(+)
diff --git a/arch/arm/boot/dts/exynos3250.dtsi
b/arch/arm/boo
On Mon, Feb 23, 2015 at 03:14:01PM -0800, H. Peter Anvin wrote:
> That may cause the same line to be flushed twice. I would suggest,
> instead, also removing the arithmetic on void *:
Btw, should we hold down all those suggested usages somewhere in
Documentation/x86/ as commit messages are genera
On 24/02/15 07:58, Ingo Molnar wrote:
* Sudeep Holla wrote:
This patch removes the redundant sysfs cacheinfo code by
reusing the newly introduced generic cacheinfo
infrastructure through the commit 246246cbde5e ("drivers:
base: support cpu cache information interface to
userspace via sysfs"
dl_task_timer() may fire on a different rq from where a task was removed
after throttling. Since the call path is:
dl_task_timer() ->
enqueue_task_dl() ->
enqueue_dl_entity() ->
replenish_dl_entity()
and replenish_dl_entity() uses dl_se's rq, we can't use current's rq
in dl_ta
When cpumask of an exclusive cpuset is changed the cpuset needs
to be destroyed and recreated with the new span. Since we keep
track of the current used deadline bandwidth in the root_domain(s)
associated with exclusive cpusets, the information is gone after
the rood_domain is destroyed.
Add two m
On Mon, Feb 23, 2015 at 03:11:40PM -0800, Stephen Boyd wrote:
> >>> I would do something more simple that is just a list of keys and
> >>> their location like this:
> >>>
> >>> device-serial-number = ;
> >>> key1 = ;
> >>> key2 = ;
> >> I'm sorry, but what's the difference?
> > It can describe the
Paravirt spinlock clears slowpath flag after doing unlock.
As explained by Linus currently it does:
prev = *lock;
add_smp(&lock->tickets.head, TICKET_LOCK_INC);
/* add_smp() is a full mb() */
if (unlikely(lock->tickets.tail & TICKET_
This patch add CLKOUT driver support for Exynos3250 SoC.
Signed-off-by: Inha Song
---
drivers/clk/samsung/clk-exynos-clkout.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/clk/samsung/clk-exynos-clkout.c
b/drivers/clk/samsung/clk-exynos-clkout.c
index 3a7cb25..1c02e73 100644
---
On Sat, Feb 21, 2015 at 5:37 AM, Al Viro wrote:
> On Thu, Feb 19, 2015 at 08:19:35PM +0300, Konstantin Khlebnikov wrote:
>> I've noticed significant locking contention in memory reclaimer around
>> sb_lock inside grab_super_passive(). Grab_super_passive() is called from
>> two places: in icache/dc
* Arjan van de Ven wrote:
> I think 10 seconds is Ingo being a bit exaggerating,
> since you can boot a full system in a lot less time than
> that, and more so if you know more about the system (e.g.
> don't need to spin down and then discover and spin up
> disks). If you're talking about in
Use early_ioremap() to map an I/O-area instead of early_memremap().
Signed-off-by: Juergen Gross
---
arch/x86/platform/efi/efi-bgrt.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/platform/efi/efi-bgrt.c b/arch/x86/platform/efi/efi-bgrt.c
index d143d21..d7f997f
Memory mapped via early_memremap() should be unmapped with
early_memunmap() instead of early_iounmap().
Signed-off-by: Juergen Gross
---
arch/x86/kernel/e820.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/x86/kernel/e820.c b/arch/x86/kernel/e820.c
index 46201de..7d46b
Memory mapped via early_memremap() should be unmapped with
early_memunmap() instead of early_iounmap().
Signed-off-by: Juergen Gross
---
arch/x86/kernel/setup.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/arch/x86/kernel/setup.c b/arch/x86/kernel/setup.c
index 98d
Memory mapped via early_memremap() should be unmapped with
early_memunmap() instead of early_iounmap().
Signed-off-by: Juergen Gross
---
arch/x86/kernel/devicetree.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/kernel/devicetree.c b/arch/x86/kernel/devicetree.
On Tue, Feb 24, 2015 at 05:26:42PM +0900, Mark Brown wrote:
> On Sun, Feb 15, 2015 at 01:37:11AM -0800, Nicolin Chen wrote:
> > According to i.MX6 Series Reference Manual, the formula to calculate
> > the sys clock is
>
> This doesn't apply against current code, pleae check and resend.
That's str
Areas mapped via early_memremap() should be unmapped via
early_memunmap(), while I/O-areas should be mapped via early_ioremap()
and unmapped via early_iounmap().
There are multiple spots where an area is mapped via the mem variant
and unmapped via the io variant. This series corrects this by using
On 24/02/15 08:55, Mark Brown wrote:
On Thu, Feb 19, 2015 at 01:02:03PM +, Srinivas Kandagatla wrote:
The culprit was in my test code, which I eventually fixed. However I would
have expected regmap to do some out of bound check before it tries to access
the register space.
If I try to
On 02/24/2015 11:07 AM, Ingo Molnar wrote:
>
> * Boaz Harrosh wrote:
>
>> --- a/kernel/resource.c
>> +++ b/kernel/resource.c
>> @@ -1075,8 +1075,13 @@ struct resource * __request_region(struct resource
>> *parent,
>> break;
>> if (conflict != parent) {
>>
Drop ucc_slow_poll_transmitter_now() which has no users since its
inception in 2007 in commit 986585385131 ("[POWERPC] Add QUICC
Engine (QE) infrastructure").
Signed-off-by: Arseny Solokha
---
arch/powerpc/include/asm/ucc_slow.h | 13 -
arch/powerpc/sysdev/qe_lib/ucc_slow.c | 5 --
On 02/24/2015 11:06 AM, Ingo Molnar wrote:
>
> * Boaz Harrosh wrote:
>
>> --- a/include/linux/ioport.h
>> +++ b/include/linux/ioport.h
>> @@ -255,6 +256,5 @@ static inline bool resource_overlaps(struct resource
>> *r1, struct resource *r2)
>> return (r1->start <= r2->end && r1->end >= r
Drop unused fsl_mpic_primary_get_version(), mpic_set_clk_ratio(),
mpic_set_serial_int().
+ fsl_mpic_primary_get_version() is just a safe wrapper around
fsl_mpic_get_version() for SMP configurations. While the latter is
called explicitly for handling PIC initialization and setting up error
interr
* Boaz Harrosh wrote:
> --- a/kernel/resource.c
> +++ b/kernel/resource.c
> @@ -1075,8 +1075,13 @@ struct resource * __request_region(struct resource
> *parent,
> break;
> if (conflict != parent) {
> parent = conflict;
> -
Hi Prabhakar,
On Tuesday 24 February 2015 08:04:40 Lad, Prabhakar wrote:
> On Tue, Feb 24, 2015 at 12:35 AM, Laurent Pinchart wrote:
> > On Monday 23 February 2015 20:19:32 Lad Prabhakar wrote:
> >> From: "Lad, Prabhakar"
> >>
> >> this patch drops driver specific isp_video_fh, as this
> >> can
* Boaz Harrosh wrote:
> --- a/include/linux/ioport.h
> +++ b/include/linux/ioport.h
> @@ -255,6 +256,5 @@ static inline bool resource_overlaps(struct resource *r1,
> struct resource *r2)
> return (r1->start <= r2->end && r1->end >= r2->start);
> }
>
> -
> #endif /* __ASSEMBLY__ */
Drop unused static procedure which doesn't have callers within its
translation unit. It had been already removed independently in QEMU[1]
from the OpenPIC implementation borrowed from the kernel.
[1] https://lists.gnu.org/archive/html/qemu-devel/2014-06/msg01812.html
Signed-off-by: Arseny Solokha
Drop planetcore_set_serial_speed() which had no users since its
inception in commit fec6047047fd ("[POWERPC] bootwrapper: Add PlanetCore
firmware support") in 2007.
Signed-off-by: Arseny Solokha
---
arch/powerpc/boot/planetcore.c | 33 -
arch/powerpc/boot/planetco
This series removes unused functions from powerpc tree that I've been
able to discover.
Two machines at hands, e300 and e500 based, boot and run without
regressions on my workload with this series applied. The removed code
seems also been rarely touched, so it seems the series is safe at least
in
On Mon, Feb 23, 2015 at 5:37 PM, Michal Hocko wrote:
> On Fri 20-02-15 17:39:42, Konstantin Khlebnikov wrote:
>> This makes show_mem() much less verbose at huge machines. Instead of
>> huge and almost useless dump of counters for each per-zone per-cpu
>> lists this patch prints sum of these counte
On Fri, 2015-02-20 at 19:54 +0100, Bastien Nocera wrote:
> Hey Dmitry,
>
> On Fri, 2015-02-20 at 10:40 -0800, Dmitry Torokhov wrote:
> > On Fri, Feb 20, 2015 at 10:04:04AM -0500, Benjamin Tissoires wrote:
> > > On Fri, Feb 20, 2015 at 9:44 AM, Bastien Nocera wrote:
> > > > Signed-off-by: Bastien
On 02/24/2015 05:33 PM, Arnd Bergmann wrote:
> On Tuesday 24 February 2015 14:16:45 Chanwoo Choi wrote:
>> This patch adds new Exynos5433 dtsi to support 64-bit Exynos5433 SoC based on
>> Octal core CPUs (quad Cortex-A57 and quad Cortex-A53). And Exynos5433
>> supports
>> PSCI (Power State Coordin
On Thu, Feb 19, 2015 at 01:02:03PM +, Srinivas Kandagatla wrote:
> The culprit was in my test code, which I eventually fixed. However I would
> have expected regmap to do some out of bound check before it tries to access
> the register space.
> If I try to do an out of bound access via regmap
Le 24/02/2015 08:45, Michal Simek a écrit :
> This driver is used on new Xilinx ZynqMP SoC.
>
> Signed-off-by: Michal Simek
> Acked-by: Sören Brinkmann
I see no objection on my side:
Acked-by: Nicolas Ferre
> ---
>
> drivers/net/ethernet/cadence/Kconfig | 4 ++--
> 1 file changed, 2 inserti
On Tuesday 24 February 2015 00:04:21 Ezequiel Garcia wrote:
> So, tried a different approach and removed pt_regs from the UAPI ptrace.h,
> replacing it with a new user_regs that describes how registers are passed
> to user. This however is also problematic, as pt_regs is already used
> by glibc (no
On Tue 2015-02-24 16:38:18, Masami Hiramatsu wrote:
> Hi Petr,
>
> Sorry I missed this mail.
Thanks a lot for answering it with many valuable information.
> (2015/01/27 1:14), Petr Mladek wrote:> On Fri 2014-11-21 05:25:30, Masami
> Hiramatsu wrote:
> >> Set FTRACE_OPS_FL_IPMODIFY flag only fo
On 02/24/2015 05:35 PM, Arnd Bergmann wrote:
> On Tuesday 24 February 2015 14:16:45 Chanwoo Choi wrote:
>> + aliases {
>> + pinctrl0 = &pinctrl_alive;
>> + pinctrl1 = &pinctrl_aud;
>> + pinctrl2 = &pinctrl_cpif;
>> + pinctrl3 = &pinctrl_
On 02/24/2015 10:34 AM, Ingo Molnar wrote:
>
> * Boaz Harrosh wrote:
>
>> On 02/24/2015 06:22 AM, Dan Williams wrote:
>> <>
By Popular demand An Extra WARNING message is printed if
an "UNKNOWN" is found. It will look like this:
e820: WARNING [mem 0x1-0x1] is unkn
On 02/18/2015 07:45 PM, Krzysztof Kozlowski wrote:
> On Exynos4412 boards (Trats2, Odroid U3) after enabling L2 cache in
> 56b60b8bce4a ("ARM: 8265/1: dts: exynos4: Add nodes for L2 cache
> controller") the second suspend to RAM failed. First suspend worked fine
> but the next one hang just after p
On 02/24/2015 04:59 PM, Krzysztof Kozlowski wrote:
> On wto, 2015-02-24 at 11:38 +0900, Chanwoo Choi wrote:
>> Hi Krzysztof,
>>
>> I tested this patch for suspend-to-ram on Exynos4412-based trats2 board.
>> When I tested suspend-to-ram repetitively, I faced on hang issue of
>> suspend-to-ram for Ex
On 02/24/2015 10:39 AM, Boaz Harrosh wrote:
>
> Resource providers set this flag if they want
> that request_region_XXX will print a warning in dmesg
> if this particular resource is locked by a driver.
>
> Thous acting as a Protocol Police about experimental
> devices that did not pass a comity
On 02/24/2015 05:21 PM, Krzysztof Kozlowski wrote:
> 2015-02-24 7:09 GMT+01:00 Chanwoo Choi :
>> This patch adds only the compatible string for S2MPS13 clock which is
>> identical
>> with S2MPS14 clock driver.
>
> If everything is identical then maybe use the same ID?
> { "s5m-rtc",
Hi Rafael,
On Tue, 24 Feb 2015 02:02:59 +0100
"Rafael J. Wysocki" wrote:
> On Friday, February 20, 2015 10:31:44 AM Mark Rutland wrote:
> > [...]
>
> [cut]
>
> > Given all of the above I'll go back to the IRQF_SHARED_TIMER_OK approach
> > you proposed, along with documentation updates and com
On Tue, Feb 24, 2015 at 09:30:21PM +1300, Felix Fietkau wrote:
> On 2015-02-24 21:27, Brian Norris wrote:
> > On Tue, Feb 24, 2015 at 09:20:31PM +1300, Felix Fietkau wrote:
> >> On 2015-02-24 21:07, Brian Norris wrote:
> >> > OK let's drop this patch from the series. At best, we could just do
> >>
Resource providers set this flag if they want
that request_region_XXX will print a warning in dmesg
if this particular resource is locked by a driver.
Thous acting as a Protocol Police about experimental
devices that did not pass a comity approval.
The Only user of this flag is x86/kernel/e820.
On Tuesday 24 February 2015 14:16:45 Chanwoo Choi wrote:
> + aliases {
> + pinctrl0 = &pinctrl_alive;
> + pinctrl1 = &pinctrl_aud;
> + pinctrl2 = &pinctrl_cpif;
> + pinctrl3 = &pinctrl_ese;
> + pinctrl4 = &pinctrl_finger;
>
* Boaz Harrosh wrote:
> On 02/24/2015 06:22 AM, Dan Williams wrote:
> <>
> >> By Popular demand An Extra WARNING message is printed if
> >> an "UNKNOWN" is found. It will look like this:
> >> e820: WARNING [mem 0x1-0x1] is unknown type 12
> >
> > I don't think we need to warn
On Tuesday 24 February 2015 14:16:45 Chanwoo Choi wrote:
> This patch adds new Exynos5433 dtsi to support 64-bit Exynos5433 SoC based on
> Octal core CPUs (quad Cortex-A57 and quad Cortex-A53). And Exynos5433 supports
> PSCI (Power State Coordination Interface) v0.1.
>
> This patch includes follow
Yannick Guerrini [mailto:yguerr...@tomshardware.fr]
> Sent: Tuesday, February 24, 2015 3:49 PM
> To: nic_swsd
> Cc: triv...@kernel.org; linux-kernel@vger.kernel.org; Yannick Guerrini
> Subject: [PATCH] drivers, realtek: Fix trivial typo in rtl_check_firmware
>
> Change 'firwmare' to 'firmware'
>
On Tuesday 24 February 2015 14:16:44 Chanwoo Choi wrote:
> diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
> index 1b8e973..d83cea0 100644
> --- a/arch/arm64/Kconfig
> +++ b/arch/arm64/Kconfig
> @@ -154,6 +154,17 @@ config ARCH_EXYNOS
> help
> This enables support for Samsung
On 2015-02-24 21:27, Brian Norris wrote:
> On Tue, Feb 24, 2015 at 09:20:31PM +1300, Felix Fietkau wrote:
>> On 2015-02-24 21:07, Brian Norris wrote:
>> > On Wed, Nov 26, 2014 at 08:19:32AM -0500, Rodrigo Freire wrote:
>> >> From: "Brian Norris"
>> >> Sent: Wednesday, November 26, 2014 5:21:47 AM
On Sun, Feb 15, 2015 at 11:11:43PM +0100, Maciej S. Szmigiero wrote:
> of_property_read_u32_array returns 0 on success, so the return value
> shouldn't be inverted twice,
> first on assignment then in condition expression.
This doesn't apply to current code, please check and resend. Please
also
On Sun, Feb 15, 2015 at 01:37:11AM -0800, Nicolin Chen wrote:
> According to i.MX6 Series Reference Manual, the formula to calculate
> the sys clock is
This doesn't apply against current code, pleae check and resend.
signature.asc
Description: Digital signature
On Tue, Feb 24, 2015 at 09:20:31PM +1300, Felix Fietkau wrote:
> On 2015-02-24 21:07, Brian Norris wrote:
> > On Wed, Nov 26, 2014 at 08:19:32AM -0500, Rodrigo Freire wrote:
> >> From: "Brian Norris"
> >> Sent: Wednesday, November 26, 2014 5:21:47 AM
> >> Subject: Re: [PATCH v3 3/3] mtd: block2mtd
On 02/24/2015 09:08 AM, Mark Brown wrote:
> On Tue, Feb 24, 2015 at 08:44:01AM +0100, Michal Simek wrote:
>> This driver is used on new Xilinx ZynqMP SoC.
>
> Why does this have an architecture dependence at all?
Let me push this to my repo and run Fenguang's system on it if there
is any build er
801 - 900 of 923 matches
Mail list logo
