A recent change in kernel/acct.c added a new warning for many
configurations on ARM:
kernel/acct.c: In function 'acct_pin_kill':
arch/arm/include/asm/cmpxchg.h:122:3: warning: value computed is not used
[-Wunused-value]
((__typeof__(*(ptr)))__cmpxchg_local_generic((ptr), (unsigned long)(o),\
T
This patch set cleans up the system timer driver.
The main goal is to get rid of the mach/ headers dependency. At the same time,
it introduces proper probing and locking (using a regmap) for the watchdog
driver.
This is based on 4.0-rc1 and will have two merge conflicts with my cleanup #1 in
mach
Now that a proper driver is available, remove at91rm9200_restart.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/at91rm9200.c | 12
1 file changed, 12 deletions(-)
diff --git a/arch/arm/mach-at91/at91rm9200.c b/arch/arm/mach-at91/at91rm9200.c
index 8fcfb70f7124..2386d08d65
, CONFIG_LIBFC=m, CONFIG_LIBFCOE=m,
CONFIG_SCSI_BNX2X_FCOE=m
Patch is against 4.0-rc2 (localversion-next is -next-20150304)
drivers/scsi/bnx2fc/bnx2fc_io.c |9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/drivers/scsi/bnx2fc/bnx2fc_io.c b/drivers/scsi/bnx2fc/bnx2fc_io.c
AT91RM920 has a memory range reserved for timer and watchdog configuration.
Expose those registers so that drivers can make use of the system timer syscon
declared in at91 DTs.
Signed-off-by: Alexandre Belloni
---
include/linux/mfd/syscon/atmel-st.h | 47 +
1
On Wed, 2015-03-04 at 14:19 +, David Vrabel wrote:
> On 04/03/15 14:09, Juergen Gross wrote:
> >
> > The main question whether it is worth to consider this alternative is
> > the performance aspect. Does anyone have an idea which USB devices would
> > typically be used via pvusb? I'd suspect m
AT91RM9200 uses the watchdog from the system timer to reset.
Signed-off-by: Alexandre Belloni
---
drivers/power/reset/Kconfig| 7
drivers/power/reset/Makefile | 1 +
drivers/power/reset/at91rm9200-reset.c | 70 ++
3 files changed, 78 i
regcache_sync() spews warnings when a value was cached for a read-only
register as it tries to write all registers no matter whether they are
writable or not. This patch adds regmap_wrtieable() checks for
avoiding it in regcache_sync_block_single() and regcache_block_raw().
Signed-off-by: Takashi
Use clocksource_of_init to initialize the system timer instead of relying on a
custom function.
Signed-off-by: Alexandre Belloni
Acked-by: Boris Brezillon
---
arch/arm/mach-at91/at91rm9200.c | 7 ---
arch/arm/mach-at91/generic.h | 3 ---
drivers/clocksource/timer-atmel-st.c | 4
On Tue, Mar 03, 2015 at 02:31:51PM -0800, Paul E. McKenney wrote:
> On Tue, Mar 03, 2015 at 05:06:50PM -0500, Boris Ostrovsky wrote:
> > On 03/03/2015 04:26 PM, Paul E. McKenney wrote:
> > >On Tue, Mar 03, 2015 at 03:13:07PM -0500, Boris Ostrovsky wrote:
> > >>On 03/03/2015 02:42 PM, Paul E. McKenn
Hi Peter,
On 02/25/2015 02:36 PM, Peter Griffin wrote:
Now that both usb2 and usb3 phy drivers, and also the ST dwc3 glue code
are all present upstream, we can add the dwc3 DT node and have a working
usb3 controller on stih407-b2120 and stih410-b2020.
Signed-off-by: Peter Griffin
---
arch/ar
On 03/03/2015 07:02 PM, Konrad Rzeszutek Wilk wrote:
> On Tue, Mar 03, 2015 at 06:38:20PM +0300, Andrey Ryabinin wrote:
>> On 03/03/2015 05:16 PM, Konrad Rzeszutek Wilk wrote:
>>> On Tue, Mar 03, 2015 at 04:15:06PM +0300, Andrey Ryabinin wrote:
On 03/03/2015 12:40 PM, Luis R. Rodriguez wrote:
Jim Davis writes:
> Building with the attached random configuration file,
>
> drivers/bcma/driver_pcie2.c: In function 'bcma_core_pcie2_up':
> drivers/bcma/driver_pcie2.c:196:2: error: implicit declaration of
> function 'pcie_set_readrq' [-Werror=implicit-function-declaration]
> err = pcie_set_
On 03/03/2015 10:12 PM, Greg Kroah-Hartman wrote:
This is the start of the stable review cycle for the 3.19.1 release.
There are 175 patches in this series, all will be posted as a response
to this one. If anyone has any issues with these being applied, please
let me know.
Responses should be m
, CONFIG_LIBFC=m, CONFIG_LIBFCOE=m,
CONFIG_SCSI_BNX2X_FCOE=m
Patch is against 4.0-rc2 (localversion-next is -next-20150304)
drivers/scsi/bnx2fc/bnx2fc_fcoe.c |6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/scsi/bnx2fc/bnx2fc_fcoe.c
b/drivers/scsi/bnx2fc/bnx2fc_fcoe.c
Use a syscon regmap to access the systemr timer registers.
Signed-off-by: Alexandre Belloni
---
drivers/watchdog/Kconfig | 2 +-
drivers/watchdog/at91rm9200_wdt.c | 21 +++--
2 files changed, 16 insertions(+), 7 deletions(-)
diff --git a/drivers/watchdog/Kconfig b/driv
On Monday, March 02, 2015 11:24:28 AM Kevin Hilman wrote:
> From: Kevin Hilman
>
> To keep consisitency with the rest of the file, use 'genpd' as the
> name of the 'struct generic_pm_domain' pointer instead of 'gpd'.
>
> This is just a rename, no functional changes.
>
> Signed-off-by: Kevin Hil
, CONFIG_LIBFC=m, CONFIG_LIBFCOE=m,
CONFIG_SCSI_BNX2X_FCOE=m
Patch is against 4.0-rc2 (localversion-next is -next-20150304)
drivers/scsi/bnx2fc/bnx2fc_io.c |9 +
1 file changed, 5 insertions(+), 4 deletions(-)
diff --git a/drivers/scsi/bnx2fc/bnx2fc_io.c b/drivers/scsi/bnx2fc/bnx2fc_io.c
Commit 2473238eac95 ("ihex: add support for CS:IP/EIP records") removes
the "default:" statement in the switch block, making the "return
usage();" line dead code and ihex2fw silently ignoring unknown options.
Restore this statement.
This bug was found by building with HOSTCC=clang and adding
-Wunr
On Wed, Mar 04, 2015 at 12:40:34PM +0100, sanfilippo wrote:
> On 03.03.2015 15:41, Dave Martin wrote:
>
> Dave,
>
> thanks for your response.
>
> >For the element _size_ issue, I'm confused. On 32-bit, that
> >structure is clearly 196 bytes in size, with the alignment requirement
> >of void * (
On Tue, 03 Mar 2015, Vlastimil Babka wrote:
>
> No, you were correct and thanks for the hint. It's only ISOLATE_UNEVICTABLE
> from
> isolate_migratepages_range(), which is CMA, not regular compaction.
> But I wonder, can we change this even after VM_PINNED is introduced, if
> existing
> code d
Linux may be used without MMU on atmel SoCs, fix debug in this configuration.
Signed-off-by: Alexandre Belloni
---
arch/arm/include/debug/at91.S | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/arm/include/debug/at91.S b/arch/arm/include/debug/at91.S
index 80a6501b4d5
On 03/04/2015 03:29 PM, Ian Campbell wrote:
On Wed, 2015-03-04 at 14:19 +, David Vrabel wrote:
On 04/03/15 14:09, Juergen Gross wrote:
The main question whether it is worth to consider this alternative is
the performance aspect. Does anyone have an idea which USB devices would
typically be
Commit 41c9e95d641a ("MAINTAINERS: add Android driver entries")
introduced non-UTF8 characters in MAINTAINERS file. This breaks tools
like grep when using an UTF-8 locale:
$ grep -n drivers/android MAINTAINERS
Binary file MAINTAINERS matches
Replacing the characters by their UTF-8 counte
On Wed 04 Mar 02:41 PST 2015, Stanimir Varbanov wrote:
> This enables support of 'input-enable' pinconf generic property in
> the pinctrl driver.
>
> Signed-off-by: Stanimir Varbanov
> ---
> drivers/pinctrl/qcom/pinctrl-msm.c | 11 +++
> 1 files changed, 11 insertions(+), 0 deletions(
On Wed 04 Mar 02:41 PST 2015, Stanimir Varbanov wrote:
> This makes the pinctrl driver to use the generic pinconf
> interface. Mainly it gives us a way to use debugfs to dump
> group configurations.
>
> Signed-off-by: Stanimir Varbanov
> Reviewed-by: Linus Walleij
Acked-by: Bjorn Andersson
--
On 3/4/2015 1:50 AM, Borislav Petkov wrote:
On Wed, Mar 04, 2015 at 12:43:08AM -0800, Arjan van de Ven wrote:
Using 'acpi_gbl_reduced_hardware' flag outside the ACPI code
is a mistake.
ideally, the presence of that flag in the firmware table will clear/set more
global settings,
for example,
On Wed, 2015-03-04 at 15:41 +0100, Juergen Gross wrote:
> On 03/04/2015 03:29 PM, Ian Campbell wrote:
> > On Wed, 2015-03-04 at 14:19 +, David Vrabel wrote:
> >> On 04/03/15 14:09, Juergen Gross wrote:
> >>>
> >>> The main question whether it is worth to consider this alternative is
> >>> the p
From: Axel Lin [mailto:axel@ingics.com]
Sent: Tuesday, March 03, 2015 2:09 AM
>
> Current code uses num_phys settings to tell the number of entries in
> phys.
> Thus remove the NULL terminating entry from phys array which is not
> necessary.
The patch looks good.
> Signed-off-by: Axel Lin
Following the switch to multiplatform, uncompress.h is not used anymore. Remove
it.
at91_dbgu.h is also not used anymore
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/include/mach/at91_dbgu.h | 63
arch/arm/mach-at91/include/mach/uncompress.h | 218 --
hardware.h is mostly unused, move the remaining definitions to sama5.c and
remove it.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/include/mach/hardware.h | 123 -
arch/arm/mach-at91/pm.c| 11 ++-
arch/arm/mach-at91/pm_slowclock.S
Move the remaining defines from sama5d4.h to sama5.c and remove the now useless
SoC headers.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/include/mach/at91rm9200.h | 103 ---
arch/arm/mach-at91/include/mach/at91sam9260.h | 129 ---
arch/arm/mach-at
AT91 is now ready to switch to multiplatform. Do it and clean the remaining mach
includes
Alexandre Belloni (6):
ARM: at91: switch to multiplatform
ARM: at91: switch at91_dt_defconfig to multiplatform
ARM: at91: remove unused headers
ARM: at91: remove useless mach/cpu.h
ARM: at91: remove
Signed-off-by: Alexandre Belloni
---
arch/arm/configs/at91_dt_defconfig | 5 -
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git a/arch/arm/configs/at91_dt_defconfig
b/arch/arm/configs/at91_dt_defconfig
index f2670f638e97..c944fb6e1ece 100644
--- a/arch/arm/configs/at91_dt_defconfig
Switch AT91 to multiplatform as all SoCs are properly handled.
Signed-off-by: Alexandre Belloni
---
arch/arm/Kconfig| 13 -
arch/arm/mach-at91/Kconfig | 117 +++-
arch/arm/mach-at91/Makefile | 2 +
3 files changed, 62 insertions(+), 70
mach/cpu.h is not used anymore, remove it.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/include/mach/at91sam9_smc.h | 2 -
arch/arm/mach-at91/include/mach/cpu.h | 216 -
arch/arm/mach-at91/pm.c| 1 -
3 files changed, 219 del
Juergen Gross wrote:
> Do you have another feeling about the probability of a need to do usb 3?
> If it is already on the horizon I wouldn't want to do the user space
> backend now and the kernel one next year. :-)
One year is pretty long in kernel time.
//Peter
--
To unsubscribe from this list:
On Wed, Mar 4, 2015 at 6:39 AM, Brian Gerst wrote:
>
> On Wed, Mar 4, 2015 at 12:14 AM, Ingo Molnar wrote:
> >
> > * Brian Gerst wrote:
> >
> >> Use the generic compat syscall audit code instead of an x86 specific
> >> implementation.
> >>
> >> Signed-off-by: Brian Gerst
> >> ---
> >> arch/x86
On 03/04/2015 06:21 AM, Alexandre Belloni wrote:
Use a syscon regmap to access the systemr timer registers.
s/systemr/system/
Signed-off-by: Alexandre Belloni
---
...
static const struct of_device_id at91_wdt_dt_ids[] = {
+ { .compatible = "atmel,at91rm9200-st" },
{ .compa
On 03/04/2015 09:43 AM, Paul E. McKenney wrote:
On Tue, Mar 03, 2015 at 02:31:51PM -0800, Paul E. McKenney wrote:
On Tue, Mar 03, 2015 at 05:06:50PM -0500, Boris Ostrovsky wrote:
On 03/03/2015 04:26 PM, Paul E. McKenney wrote:
On Tue, Mar 03, 2015 at 03:13:07PM -0500, Boris Ostrovsky wrote:
O
On Tue, Mar 03, 2015 at 12:07:15PM +0900, Namhyung Kim wrote:
> The copyfile_offset() function is to copy source data from given
> offset to a destination file with an offset. It'll be used to build
> an indexed data file.
>
> Signed-off-by: Namhyung Kim
Acked-by: Jiri Olsa
thanks,
jirka
--
T
On Wed, Mar 04, 2015 at 11:54:37AM +0100, Paul Bolle wrote:
> All I spotted is a silly typo.
>
> Paul E. McKenney schreef op di 03-03-2015 om 09:43 [-0800]:
> > --- a/lib/Kconfig.debug
> > +++ b/lib/Kconfig.debug
> > @@ -1257,6 +1257,30 @@ config RCU_TORTURE_TEST_RUNNABLE
> > Say N here if y
On 03/04/2015 04:20 PM, Daniel Wagner wrote:
> On 03/03/2015 01:55 AM, Jeff Layton wrote:
>> On Mon, 2 Mar 2015 15:25:12 +0100
>> Daniel Wagner wrote:
>>
<>
> I have fixed that stuff and now I am testing it. Though it seems
> that there is a memory leak which can be triggered with
>
> whi
On Wed, 4 Mar 2015, Nicolas Iooss wrote:
> Commit 41c9e95d641a ("MAINTAINERS: add Android driver entries")
> introduced non-UTF8 characters in MAINTAINERS file. This breaks tools
> like grep when using an UTF-8 locale:
>
> $ grep -n drivers/android MAINTAINERS
> Binary file MAINTAINERS m
On Tue 03-03-15 14:17:19, Konstantin Khlebnikov wrote:
> Release references to buffer-heads if ext4_journal_start() fails.
Looks good. You can add:
Reviewed-by: Jan Kara
Honza
>
> Signed-off-by: Konstantin Khlebnikov
> Fixes: 5
On Wed, Mar 4, 2015 at 7:37 AM, Chen Gang wrote:
> They need several symbols which are in I2C and I2C_MUX, the related
> error:
>
> drivers/built-in.o: In function `selftest_i2c_mux_remove':
> unittest.c:(.text+0xb0ce4): undefined reference to `i2c_del_mux_adapter'
> unittest.c:(.text+0xb0ce
On 2015-02-13 12:03, Jianwei Wang wrote:
> This patch add support for Two Dimensional Animation and Compositing
> Engine (2D-ACE) on the Freescale LS102x SoCs.
>
> 2D-ACE is a Freescale display controller. It supports at most four
> plane and provide an hardware cursor.
>
> This is a simplified v
The system timer register range is also used for the watchdog. Declare it as a
syscon to be able to get a regmap early enough in the boot process
Signed-off-by: Alexandre Belloni
Acked-by: Boris Brezillon
---
Documentation/devicetree/bindings/arm/atmel-at91.txt | 2 +-
arch/arm/boot/dts/at91rm9
On 04/03/2015 at 06:51:51 -0800, Guenter Roeck wrote :
> >@@ -267,7 +276,7 @@ static struct platform_driver at91wdt_driver = {
> > .suspend= at91wdt_suspend,
> > .resume = at91wdt_resume,
> > .driver = {
> >-.name = "at91_wdt",
> >+.name
On Mon, Mar 2, 2015 at 7:38 AM, Mateusz Guzik wrote:
> As explained below, this one task name is already very useful and likely
> covers majority of real life use cases.
>
> While working in support we were getting a lot of vmcores where hung task
> detector panicked the kernel because a lot of t
* NeilBrown [150303 21:29]:
> On Tue, 3 Mar 2015 14:53:55 -0800 Tony Lindgren wrote:
> >
> > --- a/arch/arm/boot/dts/omap3-gta04.dtsi
> > +++ b/arch/arm/boot/dts/omap3-gta04.dtsi
> > @@ -367,6 +367,7 @@
> > };
> >
> > &mmc2 {
> > + interrupts-extended = <&intc 86 &omap3_pmx_core 0x12e>;
>
On Wed, Mar 4, 2015 at 5:06 AM, Clemens Ladisch wrote:
> Lucas De Marchi wrote:
>> I was debugging my application and noticed that a timerfd event was being
>> triggered *before* the timer expires.
>>
>> I reduced the scope of the program to test a single timerfd and measure the
>> difference in t
This will avoid warning during async device registration.
Signed-off-by: Stanimir Varbanov
---
drivers/dma/qcom_bam_dma.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/drivers/dma/qcom_bam_dma.c b/drivers/dma/qcom_bam_dma.c
index c3113e3..cc9e5ee 100644
--- a/drivers/d
Hi Wang,
(2015/03/04 20:22), Wang Nan wrote:
> Hi Masami,
>
> Following your advise, I adjusted early kprobe patches, added a
> kprobes_init_stage var to indicate the initiaization progress of
> kprobes. It has following avaliable values:
>
> typedef enum {
> /* kprobe initialization is e
On Wed, Mar 4, 2015 at 4:02 PM, Jiri Kosina wrote:
>> --- a/MAINTAINERS
>> +++ b/MAINTAINERS
>> @@ -725,7 +725,7 @@ F:staging/iio/trigger/iio-trig-bfin-timer.c
>>
>> ANDROID DRIVERS
>> M: Greg Kroah-Hartman
>> -M: Arve Hj?nnev?g
>> +M: Arve Hj??nnev??g
>
> I don't really call th
global_update_bandwidth() uses static variable update_time as the
timestamp for the last update but forgets to initialize it to
INITIALIZE_JIFFIES.
This means that global_dirty_limit will be 5 mins into the future on
32bit and some large amount jiffies into the past on 64bit. This
isn't critical
On Wed, Mar 04, 2015 at 09:55:11AM -0500, Boris Ostrovsky wrote:
> On 03/04/2015 09:43 AM, Paul E. McKenney wrote:
> >On Tue, Mar 03, 2015 at 02:31:51PM -0800, Paul E. McKenney wrote:
> >>On Tue, Mar 03, 2015 at 05:06:50PM -0500, Boris Ostrovsky wrote:
> >>>On 03/03/2015 04:26 PM, Paul E. McKenney
On Tue, Mar 03, 2015 at 11:54:46PM +, Laurent Pinchart wrote:
> Hello,
Hi Laurent,
> I haven't seen any reply to this e-mail. I know that the combination of
> IOMMU,
> DMA mapping and DT doesn't exactly sound like fun, but I think we still need
> to move on :-)
Yup, and thanks for taking
On Wed 04-03-15 10:22:43, Tejun Heo wrote:
> global_update_bandwidth() uses static variable update_time as the
> timestamp for the last update but forgets to initialize it to
> INITIALIZE_JIFFIES.
>
> This means that global_dirty_limit will be 5 mins into the future on
> 32bit and some large amoun
On Wed, Mar 04, 2015 at 02:31:08PM +0100, Juergen Gross wrote:
> On 03/02/2015 12:39 PM, David Vrabel wrote:
> >On 26/02/15 13:35, Juergen Gross wrote:
> >>Introduces the Xen pvUSB backend. With pvUSB it is possible for a Xen
> >>domU to communicate with a USB device assigned to that domU. The
> >>
On Tue, 3 Mar 2015, Al Viro wrote:
> On Tue, Mar 03, 2015 at 10:47:14AM -0500, Alan Stern wrote:
> > On Tue, 3 Mar 2015, Al Viro wrote:
> >
> > > Looking at that thing again... why do they need to be dummy? After all,
> > > those methods start with get_ready_ep(), which will fail unless we have
On 03/04/2015 08:30 AM, Jan Kara wrote:
On Wed 04-03-15 10:22:43, Tejun Heo wrote:
global_update_bandwidth() uses static variable update_time as the
timestamp for the last update but forgets to initialize it to
INITIALIZE_JIFFIES.
This means that global_dirty_limit will be 5 mins into the futur
On Wed, Mar 04, 2015 at 02:17:52PM +0100, Petr Mladek wrote:
> On Tue 2015-03-03 17:02:22, Josh Poimboeuf wrote:
> > It's possible for klp_register_patch() to see a module before the COMING
> > notifier is called, or after the GOING notifier is called.
> >
> > That can cause all kinds of ugly race
On 03/04/2015 04:27 PM, Greg KH wrote:
On Wed, Mar 04, 2015 at 02:31:08PM +0100, Juergen Gross wrote:
On 03/02/2015 12:39 PM, David Vrabel wrote:
On 26/02/15 13:35, Juergen Gross wrote:
Introduces the Xen pvUSB backend. With pvUSB it is possible for a Xen
domU to communicate with a USB device
On 03/04/2015 11:21 PM, Geert Uytterhoeven wrote:
> On Wed, Mar 4, 2015 at 4:02 PM, Jiri Kosina wrote:
>>> --- a/MAINTAINERS
>>> +++ b/MAINTAINERS
>>> @@ -725,7 +725,7 @@ F:staging/iio/trigger/iio-trig-bfin-timer.c
>>>
>>> ANDROID DRIVERS
>>> M: Greg Kroah-Hartman
>>> -M: Arve Hj?nn
On 03/04/2015 04:00 PM, Boaz Harrosh wrote:
> On 03/04/2015 04:20 PM, Daniel Wagner wrote:
>> On 03/03/2015 01:55 AM, Jeff Layton wrote:
>>> On Mon, 2 Mar 2015 15:25:12 +0100
>>> Daniel Wagner wrote:
>>>
> <>
>> I have fixed that stuff and now I am testing it. Though it seems
>> that there is a m
Subject: writeback: add missing INITIAL_JIFFIES init in
global_update_bandwidth()
global_update_bandwidth() uses static variable update_time as the
timestamp for the last update but forgets to initialize it to
INITIALIZE_JIFFIES.
This means that global_dirty_limit will be 5 mins into the future
Hi,
Here we have 5 patches that add a DRM driver for the LCD
controller in the Ingenic JZ4780 SoC.
The HDMI Controller in the JZ4780 is by Synopsys
and the dw_hdmi driver is used.
These patches are based on 4.0-rc2
Feedback welcome
Thank-you
ZubairLK
Zubair Lutfullah Kakakhel (5):
dt-bindin
On 03/04/2015 08:37 AM, Tejun Heo wrote:
Subject: writeback: add missing INITIAL_JIFFIES init in
global_update_bandwidth()
global_update_bandwidth() uses static variable update_time as the
timestamp for the last update but forgets to initialize it to
INITIALIZE_JIFFIES.
This means that global_
This patch adds a display susbsytem for the Ingenic JZ4780 SoC
Signed-off-by: Zubair Lutfullah Kakakhel
---
.../devicetree/bindings/video/ingenic-jz4780-drm.txt| 17 +
1 file changed, 17 insertions(+)
create mode 100644
Documentation/devicetree/bindings/video/ingenic-jz4780
Hi Yinghai,
I got the reason and made a debug patch to fix it. Could you please
apply it on top of this patchset and try again? Then it will behave well
and just return 0x13c00 since no random is got.
Please check the attachment.
Thanks
Baoquan
On 03/03/15 at 12:45am, Yinghai Lu wrote:
> a
Hi David
02.03.2015, 03:17, "David Fries" :
> You are correct, it would be a race condition if it doesn't increment
> the refcnt before unlocking the mutex, and it should get the mutex
> before unref. Here's an updated version, I haven't even tried to
> compile it.
>
> What do you think Evgeniy?
Add drm driver for the Ingenic JZ4780 SoC.
Signed-off-by: Zubair Lutfullah Kakakhel
---
drivers/gpu/drm/Kconfig | 2 +
drivers/gpu/drm/Makefile | 1 +
drivers/gpu/drm/jz4780/Kconfig | 12 +
drivers/gpu/drm/jz4780/Makefile | 10 +
drivers/gpu/drm/jz4780/j
Commit 41c9e95d641a ("MAINTAINERS: add Android driver entries")
introduced non-UTF8 characters in MAINTAINERS file. This breaks tools
like grep when using an UTF-8 locale:
$ grep -n drivers/android MAINTAINERS
Binary file MAINTAINERS matches
Replacing the characters by their UTF-8 counte
Ingenic JZ4780 hdmi is compatible with dw_hdmi.
Signed-off-by: Zubair Lutfullah Kakakhel
---
drivers/gpu/drm/jz4780/Kconfig | 10 ++
drivers/gpu/drm/jz4780/Makefile | 1 +
drivers/gpu/drm/jz4780/dw_hdmi-jz4780.c | 234
include/drm/bridge/dw_hd
Add DT bindings for the hdmi driver for the Ingenic JZ4780 SoC.
Signed-off-by: Zubair Lutfullah Kakakhel
---
.../bindings/video/ingenic-jz4780-hdmi.txt | 41 ++
1 file changed, 41 insertions(+)
create mode 100644
Documentation/devicetree/bindings/video/ingenic-jz478
Add DT bindings for the LCD controller on the jz4780 SoC
Signed-off-by: Zubair Lutfullah Kakakhel
---
.../bindings/video/ingenic-jz4780-lcd.txt | 39 ++
1 file changed, 39 insertions(+)
create mode 100644
Documentation/devicetree/bindings/video/ingenic-jz4780-lcd.t
Hi Will,
(CC'ing Thierry Reding who was missing. Thierry, you'll have to look at the
archive for the discussion, but here's at least a start pointer)
On Wednesday 04 March 2015 15:25:05 Will Deacon wrote:
> On Tue, Mar 03, 2015 at 11:54:46PM +, Laurent Pinchart wrote:
> > Hello,
>
> Hi Laur
On Wed, 04 Mar 2015, Alexandre Belloni wrote:
> AT91RM920 has a memory range reserved for timer and watchdog configuration.
> Expose those registers so that drivers can make use of the system timer syscon
> declared in at91 DTs.
>
> Signed-off-by: Alexandre Belloni
> ---
> include/linux/mfd/sys
On Wed, 4 Mar 2015, Nicolas Iooss wrote:
> Should I send the patch again with proper encoding?
If you want it to be applied, then yes :)
Thanks,
--
Jiri Kosina
SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel
On Tue, 3 Mar 2015, Benjamin Tissoires wrote:
> From: Nikolai Kondrashov
>
> Merge the hid-huion driver into hid-uclogic as all the devices supported
> by hid-huion are in fact UC-Logic devices.
>
> Signed-off-by: Nikolai Kondrashov
> Signed-off-by: Benjamin Tissoires
> ---
>
> no changes in
Hi Leif,
On 11/27/2014 12:56 PM, Leif Lindholm wrote:
> Update of_find_node_by_path():
> 1) Rename function to of_find_node_opts_by_path(), adding an optional
>pointer argument. Provide a static inline wrapper version of
>of_find_node_by_path() which calls the new function with NULL as
>
Am Mittwoch, 4. März 2015, 15:18:19 schrieb Marian Marinov:
Hi Marian,
>Hello,
>we are running hundreds of containers and we got some valid requests
>from customers that want to be able to change their container's
>hostname using the sysctl command.
>
>The current implementation does not allow ea
> Hi,
Hi Archit,
>
> On 03/04/2015 12:06 AM, Stephane Viau wrote:
>> Up until now, we assume that eDP is tight to intf_0 and HDMI to
>> intf_3. This information shall actually come from the mdp5_cfg
>> module since it can change from one chip to another.
>>
>> Signed-off-by: Stephane Viau
>> ---
On 03/03/15 at 10:32am, Yinghai Lu wrote:
> On Mon, Mar 2, 2015 at 6:58 AM, Baoquan He wrote:
> > static void mem_avoid_init(unsigned long input, unsigned long input_size,
> > - unsigned long output, unsigned long output_size)
> > + unsigned long
This patch is a fix to "iommu/arm-smmu: add support for iova_to_phys
through ATS1PR".
According to ARM documentation, translation registers are optional even
in SMMUv1, so ID0_S1TS needs to be checked to verify their presence.
Also, we check that the domain is a stage-1 domain.
Signed-off-by: Bapt
On Wed, 4 Mar 2015, Josh Poimboeuf wrote:
> > CPU0CPU1
> >
> > delete_module() #SYSCALL
> >
> >try_stop_module()
> > mod->state = MODULE_STATE_GOING;
> >
> >mutex_unlock(&module_mutex);
> >
> > klp_regist
On 04/03/15 14:55, Boris Ostrovsky wrote:
>
> In the meantime, it turned out that HVM guests are broken by this patch
> (with our without changes that we've been discussing), because HVM CPUs
> die with
>
> static void xen_hvm_cpu_die(unsigned int cpu)
> {
> xen_cpu_die(cpu);
> na
From: Leilei Zhao
Signed-off-by: Leilei Zhao
Signed-off-by: Ludovic Desroches
Signed-off-by: Nicolas Ferre
---
arch/arm/boot/dts/sama5d4.dtsi | 40
1 file changed, 40 insertions(+)
diff --git a/arch/arm/boot/dts/sama5d4.dtsi b/arch/arm/boot/dts/sama5d
Dear Arend,
as followup to my last inquiry, since it's passed more than 2 weeks, I'm
afraid I didn't receive any answer.
As from subject, I finally discovered that brcmsmac is not compliant to
802.11 regulations for BCM4313.
So, as purchasing customer, and member of Linux users community, I try
to
From: Bo Shen
Signed-off-by: Bo Shen
Signed-off-by: Nicolas Ferre
---
arch/arm/boot/dts/sama5d4.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/sama5d4.dtsi b/arch/arm/boot/dts/sama5d4.dtsi
index 93dc4e374b64..3041baaa19a1 100644
--- a/arch/arm/boot/dts/s
On Wed, 4 Mar 2015, Borislav Petkov wrote:
> On Wed, Mar 04, 2015 at 12:00:37AM -0800, Yinghai Lu wrote:
> > commit f47233c2d34f ("x86/mm/ASLR: Propagate base load address calculation")
> > is using address as value for kaslr_enabled.
> >
> > That will random kaslr_enabled get that set or cleared
On 03/04/2015 05:48 PM, Stephan Mueller wrote:
> Am Mittwoch, 4. März 2015, 15:18:19 schrieb Marian Marinov:
>
> Hi Marian,
>
>> Hello,
>> we are running hundreds of containers and we got some valid requests
> >from customers that want to be able to change their container's
>> hostname using the sy
(2015/03/04 22:52), Namhyung Kim wrote:
> It currently prevents adding probes in weak symbols. But there're cases
> that given name is an only weak symbol so that we cannot add probe.
>
> $ perf probe -x /usr/lib/libc.so.6 -a calloc
> Failed to find symbol calloc in /usr/lib/libc-2.21.so
>
On 26/02/15 18:53, Laurent Pinchart wrote:
Hi Sudeep,
Thank you for the patch.
On Thursday 26 February 2015 11:47:57 Sudeep Holla wrote:
As per the SAF1761 data sheet[0], the DcChipID register represents
the hardware version number (0001h) and the chip ID (1582h) for the
Peripheral Controlle
Hi Wincy,
Wincy Van writes:
> In commit 3af18d9c5fe9 ("KVM: nVMX: Prepare for using hardware MSR bitmap"),
> we are setting MSR_BITMAP in prepare_vmcs02 if we should use hardware. This
> is not enough since the field will be modified by following vmx_set_efer.
>
> Fix this by setting vmx_msr_bit
On Mar 03 2015 or thereabouts, Jason Gerecke wrote:
> On 3/3/2015 9:20 AM, Benjamin Tissoires wrote:
> >If noone listens to the input device when a tool comes in proximity,
> >the tablet does not send the in-prox event when a client becomes available.
> >That means that no events will be sent until
Hi Mark,
On Wed, Mar 04, 2015 at 12:05:39PM +, Mark Brown wrote:
> Commit ddd4dd8ddf784 (thermal: extend the cooling device API to include
> power information) added stubs for newly introduced functions when
> !CONFIG_THERMAL but did not provide names for the parameters which is
> a syntax err
From: Antonios Motakis
Replace the function vfio_domains_have_iommu_cache() with a more generic
function vfio_domains_have_iommu_cap() which allows to check all domains
of an vfio_iommu structure for a given cached capability.
Signed-off-by: Antonios Motakis
Signed-off-by: Baptiste Reynal
---
On Wed, Mar 04, 2015 at 05:25:10PM +0200, Stanimir Varbanov wrote:
> This will avoid warning during async device registration.
>
> Signed-off-by: Stanimir Varbanov
> ---
> drivers/dma/qcom_bam_dma.c |1 +
> 1 files changed, 1 insertions(+), 0 deletions(-)
>
> diff --git a/drivers/dma/qcom_b
701 - 800 of 1215 matches
Mail list logo
