Remove leftover from the previous cleanup
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/generic.h | 7 ---
1 file changed, 7 deletions(-)
diff --git a/arch/arm/mach-at91/generic.h b/arch/arm/mach-at91/generic.h
index d224e195706a..28ca57a2060f 100644
---
From: Boris Brezillon
Use the regmap coming from syscon to access the registers instead of using
pmc_read/pmc_write. This allows to avoid passing the at91_pmc structure to
the child nodes of the PMC.
The final benefit is to have each clock register itself instead of having
to iterate over the
On giovedì 8 ottobre 2015 12:28:16 CEST, Mika Westerberg wrote:
On Thu, Oct 08, 2015 at 12:17:39PM +0200, Niccolò Belli wrote:
Il giovedì 8 ottobre 2015 12:06:15 CEST, Mika Westerberg ha scritto: ...
You may want to try another distro if it reproduces.
It seems that only Arch triggers the
Use regmap to access the PMC to avoid using at91_pmc_read and
at91_pmc_write.
Signed-off-by: Alexandre Belloni
Acked-by: Felipe Balbi
---
drivers/usb/gadget/udc/atmel_usba_udc.c | 20 ++--
drivers/usb/gadget/udc/atmel_usba_udc.h | 2 ++
2 files changed, 12 insertions(+), 10
The at24 driver is now capable of reading the serial number from at24cs
EEPROM chips. Export the serial number through sysfs.
Signed-off-by: Bartosz Golaszewski
---
drivers/misc/eeprom/at24.c | 44
1 file changed, 40 insertions(+), 4 deletions(-)
Commit-ID: 85c9306d44f757d2fb3b0e3e399080a025315c7f
Gitweb: http://git.kernel.org/tip/85c9306d44f757d2fb3b0e3e399080a025315c7f
Author: Aravind Gopalakrishnan
AuthorDate: Mon, 12 Oct 2015 11:22:38 +0200
Committer: Ingo Molnar
CommitDate: Mon, 12 Oct 2015 16:15:47 +0200
Commit-ID: a1300e50529795cd605da6a015d4944a18921db0
Gitweb: http://git.kernel.org/tip/a1300e50529795cd605da6a015d4944a18921db0
Author: Aravind Gopalakrishnan
AuthorDate: Mon, 12 Oct 2015 11:22:39 +0200
Committer: Ingo Molnar
CommitDate: Mon, 12 Oct 2015 16:15:47 +0200
Hi Krzysztof,
On 12 October 2015 at 17:43, Krzysztof Kozlowski
wrote:
> W dniu 12.10.2015 o 20:08, Anand Moon pisze:
>> Hi Krzysztof,
>>
>> On 12 October 2015 at 11:19, Krzysztof Kozlowski
>> wrote:
>>> On 12.10.2015 13:42, Krzysztof Kozlowski wrote:
On 12.10.2015 00:46, Anand Moon wrote:
Move the macro definitions above the struct definitions and add some
tabs for better readability.
Signed-off-by: Bartosz Golaszewski
---
drivers/misc/eeprom/at24.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
diff --git a/drivers/misc/eeprom/at24.c
Commit-ID: 0399f73299f1b7e04de329050f7111b362b7eeb5
Gitweb: http://git.kernel.org/tip/0399f73299f1b7e04de329050f7111b362b7eeb5
Author: Borislav Petkov
AuthorDate: Mon, 12 Oct 2015 11:22:42 +0200
Committer: Ingo Molnar
CommitDate: Mon, 12 Oct 2015 16:15:48 +0200
x86/microcode/amd: Do
Commit-ID: 2eff73c0a11f19ff082a566e3429fbaaca7b8e7b
Gitweb: http://git.kernel.org/tip/2eff73c0a11f19ff082a566e3429fbaaca7b8e7b
Author: Borislav Petkov
AuthorDate: Mon, 12 Oct 2015 11:22:41 +0200
Committer: Ingo Molnar
CommitDate: Mon, 12 Oct 2015 16:15:48 +0200
x86/microcode/amd:
On Fri, Oct 02, 2015 at 03:58:49PM +0900, Namhyung Kim wrote:
> The util/event.h includes util/build-id.h only for BUILD_ID_SIZE.
> This is a problem when I include util/event.h from util/tool.h which
> is also included by util/build-id.h since it now makes a circular
> dependency resulting in
Chips from the at24cs EEPROM series have an additional read-only memory area
containing a factory pre-programmed serial number. In order to access it, a
dummy write must be executed before reading the serial number bytes.
This series adds support for reading the serial number through a sysfs
In preparation for supporting the at24cs EEPROM series add a new flag to
platform data. When set, it should tell the driver that the chip has an
additional read-only memory area that holds a factory pre-programmed serial
number.
Signed-off-by: Bartosz Golaszewski
---
Commit-ID: 7e0abcd6b7ec1452bf4a850fccbae44043c05806
Gitweb: http://git.kernel.org/tip/7e0abcd6b7ec1452bf4a850fccbae44043c05806
Author: Gabriel Laskar
AuthorDate: Tue, 6 Oct 2015 16:27:35 +0200
Committer: Thomas Gleixner
CommitDate: Sun, 11 Oct 2015 21:24:27 +0200
x86/mce: Include
Use BIT() macro to replace the 0xXX constants in platform_data flags
definitions.
Signed-off-by: Bartosz Golaszewski
---
include/linux/platform_data/at24.h | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/include/linux/platform_data/at24.h
It seems as if the second check for I2C_FUNC_I2C functionality had been
introduced accidentally during a merge. Tt's reduntant, so remove it.
Signed-off-by: Bartosz Golaszewski
---
drivers/misc/eeprom/at24.c | 3 ---
1 file changed, 3 deletions(-)
diff --git a/drivers/misc/eeprom/at24.c
Improve the readability of the device table by separating columns with
tabs.
Signed-off-by: Bartosz Golaszewski
---
drivers/misc/eeprom/at24.c | 28 ++--
1 file changed, 14 insertions(+), 14 deletions(-)
diff --git a/drivers/misc/eeprom/at24.c
Commit-ID: fa20a2ed6fff717839ec03b6574ea0affcb58841
Gitweb: http://git.kernel.org/tip/fa20a2ed6fff717839ec03b6574ea0affcb58841
Author: Aravind Gopalakrishnan
AuthorDate: Mon, 12 Oct 2015 11:22:40 +0200
Committer: Ingo Molnar
CommitDate: Mon, 12 Oct 2015 16:15:48 +0200
The infrastructure for reading of the factory-programmed serial number
for at24cs EEPROM series is now in place. Add the chips that are actually
equipped with the serial number memory area to the list of supported
devices.
Signed-off-by: Bartosz Golaszewski
---
drivers/misc/eeprom/at24.c | 9
The at24cs series EEPROM chips have an additional read-only memory area
containing a factory pre-programmed serial number. In order to access
it, one has to perform a dummy write before reading the serial number
bytes.
Add a function that allows to access the serial number.
Signed-off-by:
Avoid using code from clk/at91 for PM.
This also has the bonus effect of setting arm_pm_idle for sama5 platforms.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/at91rm9200.c | 2 --
arch/arm/mach-at91/at91sam9.c | 2 --
arch/arm/mach-at91/generic.h| 6 ++
According to memory-barriers.txt, xchg, cmpxchg and their atomic{,64}_
versions all need to imply a full barrier, however they are now just
RELEASE+ACQUIRE, which is not a full barrier.
So replace PPC_RELEASE_BARRIER and PPC_ACQUIRE_BARRIER with
PPC_ATOMIC_ENTRY_BARRIER and
From: Boris Brezillon
Only disable available IRQs in case writing to a reserved bit has a harmful
effect.
Signed-off-by: Boris Brezillon
Signed-off-by: Alexandre Belloni
---
drivers/clk/at91/pmc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clk/at91/pmc.c
On Fri, Oct 09, 2015 at 09:53:32AM -0700, Drew Richardson wrote:
> On Fri, Oct 09, 2015 at 11:13:38AM +0100, Will Deacon wrote:
> > On Wed, Oct 07, 2015 at 11:28:18AM -0700, Drew Richardson wrote:
> > > diff --git a/arch/arm/kernel/perf_event_v7.c
> > > b/arch/arm/kernel/perf_event_v7.c
> > >
The AT91 clock drivers make use of IRQs to avoid polling when waiting for
some clocks to be enabled. Unfortunately, this leads to a crash when those
IRQs are threaded (which happens when using preempt-rt) because they are
registered before thread creation is possible.
Use polling on those clocks
at91_pmc_base is not used anymore, remove it along with at91_pmc_read and
at91_pmc_write.
Signed-off-by: Alexandre Belloni
---
drivers/clk/at91/pmc.c | 5 -
include/linux/clk/at91_pmc.h | 12
2 files changed, 17 deletions(-)
diff --git a/drivers/clk/at91/pmc.c
at91_pm_init() doesn't return a value, as is the case for its callers,
simply call it instead of returning its non-existent return value.
Signed-off-by: Alexandre Belloni
---
arch/arm/mach-at91/pm.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git
From: Boris Brezillon
The PMC block is providing several functionnalities:
- system clk management
- cpuidle
- platform suspend
Replace the void __iomem *regs field by a regmap (retrieved using syscon)
so that we can later share the regmap across several drivers without
exporting a new
The three different irq handlers are doing the same thing, factorize their
code in a generic irq handler.
Signed-off-by: Alexandre Belloni
---
drivers/clk/at91/clk-main.c | 144 +++-
1 file changed, 63 insertions(+), 81 deletions(-)
diff --git
On Sat, Oct 10, 2015 at 12:10:39AM +0200, Arnaud Ebalard wrote:
>
> This cosmetic patch reorder nodes under internal-regs by increasing
> address order, as epxected.
expected.
Gregory, can you fix that as you commit?
Acked-by: Andrew Lunn
Andrew
>
> Signed-off-by: Arnaud Ebalard
Oops.. sorry. I will resend this one with correct address list.
On Mon, Oct 12, 2015 at 10:14:01PM +0800, Boqun Feng wrote:
> According to memory-barriers.txt, xchg, cmpxchg and their atomic{,64}_
> versions all need to imply a full barrier, however they are now just
> RELEASE+ACQUIRE, which is
On Mon, Oct 12, 2015 at 09:41:11AM +0200, Ingo Molnar wrote:
>
> * Josh Poimboeuf wrote:
>
> > Hi Ingo,
> >
> > Do you have any more objections to these patches? Would you be willing
> > to apply them?
>
> So I still don't like the tool namespace you picked: Git-alike generic
> naming plus
On Sat, Oct 10, 2015 at 12:10:24AM +0200, Arnaud Ebalard wrote:
>
> By default, armada-370-xp.dtsi file has internal RTC enabled.
> NETGEAR ReadyNAS 102, 104 and 2120 all use an Intersil ISL12057
> I2C RTC chip. The internal RTC not being disabled in the .dts
> files of those devices result in
On Mon, 2015-10-12 at 11:29 +0200, Paul Osmialowski wrote:
> From: Marcin Niesluchowski
>
> Preparation commit for future changes purpose.
>
> Moves some code responsible for storing log messages in proper format.
Perhaps better still would be to move the code into
a separate file to reduce
On Mon, Oct 12, 2015 at 04:14:16PM +0200, Arnd Bergmann wrote:
> Most samples have their own Kconfig option, but for some reason
> the configfs sample does not have one and gets built unconditionally
> when CONFIG_SAMPLES is enabled, which fails if CONFIG_CONFIGFS_FS
> is not:
>
> ERROR:
On Fri, Oct 09, 2015 at 10:08:32PM +0530, Rameshwar Sahu wrote:
> Hi Vinod,
>
> On Fri, Oct 9, 2015 at 9:42 PM, Vinod Koul wrote:
> > On Thu, Oct 08, 2015 at 02:36:57PM +0530, Rameshwar Prasad Sahu wrote:
> >> The DMA engine supports memory copy, RAID5 XOR, RAID6 PQ, and other
> >> computations.
Fix musb_platform_get_vbus_status return value in case of platform
implementation is not defined, bringing expected behaviour of
musb_platform_get wrapper. Add musb_vbus_show default method to determine
VBUS status in case platform method is not defined.
Signed-off-by: Roman Alyautdin
---
* Matt Fleming wrote:
> On Mon, 12 Oct, at 02:49:36PM, Ingo Molnar wrote:
> >
> >
> > So why not unmap them after bootup? Is there any reason to call into EFI
> > code
> > while the system is up and running?
>
> That's where the runtime services code lives. So if you want things like EFI
/20151012-170616
config: m68k-allyesconfig (attached as .config)
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
-O ~/bin/make.cross
chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
On powerpc, acquire and release semantics can be achieved with
lightweight barriers("lwsync" and "ctrl+isync"), which can be used to
implement __atomic_op_{acquire,release}.
For release semantics, since we only need to ensure all memory accesses
that issue before must take effects before the
Implement xchg_relaxed and atomic{,64}_xchg_relaxed, based on these
_relaxed variants, release/acquire variants and fully ordered versions
can be built.
Note that xchg_relaxed and atomic_{,64}_xchg_relaxed are not compiler
barriers.
Signed-off-by: Boqun Feng
---
Implement cmpxchg{,64}_relaxed and atomic{,64}_cmpxchg_relaxed, based on
which _release variants can be built.
To avoid superfluous barriers in _acquire variants, we implement these
operations with assembly code rather use __atomic_op_acquire() to build
them automatically.
For the same reason,
Some atomic operations now have _{relaxed, acquire, release} variants,
this patch then adds some trivial tests for two purpose:
1. test the behavior of these new operations in single-CPU
environment.
2. make their code generated before we actually use them somewhere,
so
Some architectures may have their special barriers for acquire, release
and fence semantics, so that general memory barriers(smp_mb__*_atomic())
in the default __atomic_op_*() may be too strong, so allow architectures
to define their own helpers which can overwrite the default helpers.
Hi,
This is v3 of the series.
Link for v1: https://lkml.org/lkml/2015/8/27/798
Link for v2: https://lkml.org/lkml/2015/9/16/527
Paul, Peter and Will, thank you all for the comments and suggestions,
that's really a lot of fun to discuss these with you and very
enlightening to me ;-)
Changes
From: Kővágó, Zoltán
When multiple GOP devices exists, but none of them implements ConOut,
the code should just choose the first GOP (according to the comments).
But currently fb_base will refer to the last GOP, while other parameters
to the first GOP, which will likely result in a garbled
Most samples have their own Kconfig option, but for some reason
the configfs sample does not have one and gets built unconditionally
when CONFIG_SAMPLES is enabled, which fails if CONFIG_CONFIGFS_FS
is not:
ERROR: "configfs_unregister_subsystem" [samples/configfs/configfs_sample.ko]
undefined!
On 12/10/15 16:59, Roman Alyautdin wrote:
Fix musb_platform_get_vbus_status return value in case of platform
implementation is not defined, bringing expected behaviour of
musb_platform_get wrapper. Add musb_vbus_show default method to determine
VBUS status in case platform method is not defined.
From: Matt Fleming
Please pull the following fix from Zoltán which addresses a bug that
resulted in the the secondary GOP display being garbled when booting
using the EFI boot stub.
The following changes since commit 825fcfce81921c9cc4ef801d844793815721e458:
MAINTAINERS: Change Matt
On Mon, Oct 12, 2015 at 01:42:59PM +0200, Sascha Hauer wrote:
> On Fri, Oct 02, 2015 at 06:32:56PM +0100, Mark Brown wrote:
> > One change I think we need here is only doing the propagation if either
> > the device lacks a set_voltage() operation (in which case it's just a
> > switch passing
On Sat, Oct 10, 2015 at 06:15:05PM +0800, Shengjiu Wang wrote:
> Shengjiu Wang (2):
> clk: imx6: Add SPDIF_GCLK clock in clock tree
> ARM: dts: imx6: change the core clock of spdif
Applied both, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of
On Monday, October 12, 2015 at 03:52:34 PM, Arnd Bergmann wrote:
> The mxs-dcp driver relies on the stmp_reset_block() helper function, which
> is provided by CONFIG_STMP_DEVICE. This symbol is always set on MXS,
> but the driver can now also be built for MXC (i.MX6)
That is correct.
> , which
Fix musb_platform_get_vbus_status return value in case of platform
implementation is not defined, bringing expected behaviour of
musb_platform_get wrapper. Add musb_vbus_show default method to determine
VBUS status in case platform method is not defined.
Signed-off-by: Roman Alyautdin
---
From: Leif Lindholm
Now that we have an efi=debug command line option in the core code, use
this instead of the arm64-specific uefi_debug option.
Signed-off-by: Leif Lindholm
Acked-by: Ard Biesheuvel
Tested-by: Ard Biesheuvel
Cc: Mark Salter
Cc: Catalin Marinas
Cc: Will Deacon
From: Leif Lindholm
As we now have a common debug infrastructure between core and arm64 efi,
drop the bit of the interface passing verbose output flags around.
Signed-off-by: Leif Lindholm
Acked-by: Ard Biesheuvel
Tested-by: Ard Biesheuvel
Cc: Mark Salter
Cc: Catalin Marinas
Cc: Will
From: Paul Gortmaker
The Kconfig for this driver is currently hidden with:
config EFI_ESRT
bool
...meaning that it currently is not being built as a module by anyone.
Lets remove the modular code that is essentially orphaned, so that
when reading the driver there is no doubt it is
From: Ard Biesheuvel
Version 2.5 of the UEFI spec introduces a new configuration table
called the 'EFI Properties table'. Currently, it is only used to
convey whether the Memory Protection feature is enabled, which splits
PE/COFF images into separate code and data memory regions.
Signed-off-by:
From: Ard Biesheuvel
UEFI v2.5 introduces a runtime memory protection feature that splits
PE/COFF runtime images into separate code and data regions. Since this
may require special handling by the OS, allocate a EFI_xxx bit to
keep track of whether this feature is currently active or not.
From: Matt Fleming
The EFI Graphics Output Protocol uses 64-bit frame buffer addresses
but these get truncated to 32-bit by the EFI boot stub when storing
the address in the 'lfb_base' field of 'struct screen_info'.
Add a 'ext_lfb_base' field for the upper 32-bits of the frame buffer
address
From: Ben Hutchings
efi-pstore should be auto-loaded on EFI systems, same as efivars.
Signed-off-by: Ben Hutchings
Cc: Matthew Garrett
Cc: "Lee, Chun-Yi"
Cc: Ard Biesheuvel
Signed-off-by: Matt Fleming
---
drivers/firmware/efi/efi-pstore.c | 1 +
1 file changed, 1 insertion(+)
diff --git
From: Taku Izumi
This patch renames print_efi_memmap() to efi_print_memmap() and
make it global function so that we can invoke it outside of
arch/x86/platform/efi/efi.c
Signed-off-by: Taku Izumi
Cc: Tony Luck
Cc: Xishi Qiu
Cc: Kamezawa Hiroyuki
Cc: Ard Biesheuvel
Signed-off-by: Matt
Hi Wenyou,
On Mon, Oct 12, 2015 at 08:12:42AM +, Yang, Wenyou wrote:
> > -Original Message-
> > From: Alexandre Belloni [mailto:alexandre.bell...@free-electrons.com]
> > Sent: 2015年10月12日 15:50
> > To: Sylvain Rochet
> > Cc: Guenter Roeck; Boris BREZILLON;
From: Taku Izumi
This patch introduces new boot option named "efi_fake_mem".
By specifying this parameter, you can add arbitrary attribute
to specific memory range.
This is useful for debugging of Address Range Mirroring feature.
For example, if
From: Taku Izumi
UEFI spec 2.5 introduces new Memory Attribute Definition named
EFI_MEMORY_MORE_RELIABLE. This patch adds this new attribute
support to efi_md_typeattr_format().
Signed-off-by: Taku Izumi
Cc: Tony Luck
Cc: Ard Biesheuvel
Cc: Xishi Qiu
Cc: KAMEZAWA Hiroyuki
Signed-off-by:
From: Matt Fleming
Folks, please pull the below patches. The largest thing is probably
the introduction of Taku's "efi_fake_mem" kernel option which allows
the EFI memory map passed from the firmware to the kernel to be
modified with additional memory map attributes.
There's also the ground
From: Leif Lindholm
fed6cefe3b6e ("x86/efi: Add a "debug" option to the efi= cmdline")
adds the DBG flag, but does so for x86 only. Move this early param
parsing to core code.
Signed-off-by: Leif Lindholm
Acked-by: Ard Biesheuvel
Tested-by: Ard Biesheuvel
Cc: Mark Salter
Cc: Borislav Petkov
On 09/10/15 16:26, Stephen Warren wrote:
> On 10/09/2015 04:20 AM, Jon Hunter wrote:
>>
>> On 08/10/15 15:27, Stephen Warren wrote:
>>> On 10/08/2015 03:58 AM, Jon Hunter wrote:
>>
>> [snip]
>>
That's fine. From my perspective I don't have a strong objection either
way, however, I can
On Mon, Oct 12, 2015 at 03:49:08AM -0400, George Spelvin wrote:
>
> Suppose CPU 0 has an offset of 0, and CPU 1 has an offset of 12.
> (I'll also use a count-up index even though I know it's actually
> count-down in the code.)
>
> CPU0 writes 5 words at 0..4, leaving add_ptr = 5.
> Then CPU 1
The mxs-dcp driver relies on the stmp_reset_block() helper function, which
is provided by CONFIG_STMP_DEVICE. This symbol is always set on MXS,
but the driver can now also be built for MXC (i.MX6), which results
in a built error if no other driver selects STMP_DEVICE:
drivers/built-in.o: In
On Fri, Oct 09, 2015 at 10:41:43AM +0200, Arnd Bergmann wrote:
> On Tuesday 06 October 2015 12:51:24 Arnd Bergmann wrote:
> >
> > I think it makes sense to stick with the traditional definition
> > of MINSIGSTKSZ == "the minimum amount that you will always need,
> > add whatever you require
On Mon, Oct 12, 2015 at 10:40:06AM +0800, yalin wang wrote:
> Remove unlikely(order), because we are sure order is not zero if
> code reach here, also add if (page == NULL), only allocate page again if
> __rmqueue_smallest() failed or alloc_flags & ALLOC_HARDER == 0
>
> Signed-off-by: yalin wang
Some recently added code to avoid a bug introduced a build error
when CONFIG_PM is disabled and a macro is hidden:
arch/arm/mach-pxa/pxa3xx.c: In function 'pxa3xx_init':
arch/arm/mach-pxa/pxa3xx.c:439:3: error: 'NDCR' undeclared (first use in this
function)
NDCR = (NDCR & ~NDCR_ND_ARB_EN) |
On Wed, Oct 07, 2015 at 02:23:23PM +0200, Alban Crequy wrote:
> Hi,
>
> I'm reporting an issue in overlay fs that was introduced in v4.2 (it
> worked on v4.1): when overlay fs is mounted inside a overlay fs, I get
> a "no such device or address" error (ENXIO) during open(). After
> adding some
On Fri, Oct 09, 2015 at 11:35:30PM +0800, Bai Ping wrote:
> Add cpufreq device for i.MX6UL. Using the common
> cpufreq of i.MX6 SOC.
>
> Signed-off-by: Bai Ping
Applied, thanks.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
This patch maintains the number of oom victims kill count in
/proc/vmstat.
Currently, we are dependent upon kernel logs when the kernel OOM occurs.
But kernel OOM can went passed unnoticed by the developer as it can
silently kill some background applications/services.
In some small embedded
The z2 machine calls pxa27x_set_pwrmode() in order to power off
the machine, but this function gets discarded early at boot because
it is marked __init, as pointed out by kbuild:
WARNING: vmlinux.o(.text+0x145c4): Section mismatch in reference from the
function z2_power_off() to the function
On Thu 08-10-15 17:07:20, Ross Zwisler wrote:
> On Tue, Sep 08, 2015 at 04:59:20PM -0600, Ross Zwisler wrote:
> > The big warning comment that is currently at the end of struct
> > inode_operations was added as part of this commit:
> >
> > 4aa7c6346be3 ("vfs: add i_op->dentry_open()")
> >
> > It
On Mon, Oct 12, 2015 at 09:45:54AM +0100, Charles Keepax wrote:
> On Wed, Oct 07, 2015 at 01:26:42PM +0100, Lee Jones wrote:
> > On Wed, 07 Oct 2015, Mark Brown wrote:
> > > This all seems pretty much fine to me - the things it is controlling are
> > > fairly specific to the way the former
Dear Arnd Bergmann,
On Mon, 12 Oct 2015 15:34:55 +0200, Arnd Bergmann wrote:
> The newly added suspend/resume implementation for ahci_mvebu causes
> a link error when CONFIG_PM_SUSPEND is disabled:
>
> ERROR: "ahci_platform_suspend_host" [drivers/ata/ahci_mvebu.ko] undefined!
> ERROR:
On Fri 09-10-15 11:03:30, Nikolay Borisov wrote:
> On 10/09/2015 10:37 AM, Hillf Danton wrote:
> @@ -109,8 +109,8 @@ static void ext4_finish_bio(struct bio *bio)
> if (bio->bi_error)
> buffer_io_error(bh);
>
On Mon, 2015-10-12 at 13:54 +0100, Rainer Weikusat wrote:
> David Miller writes:
> > From: Jason Baron
> > Date: Fri, 9 Oct 2015 00:15:59 -0400
> >
> >> These patches are against mainline, I can re-base to net-next, please
> >> let me know.
> >>
> >> They have been tested against:
On Fri, Oct 02, 2015 at 02:18:59PM +0900, Namhyung Kim wrote:
SNIP
> +void thread__find_addr_map(struct thread *thread, u8 cpumode,
> +enum map_type type, u64 addr,
> +struct addr_location *al)
> +{
> + al->thread = thread;
> +
The newly added suspend/resume implementation for ahci_mvebu causes
a link error when CONFIG_PM_SUSPEND is disabled:
ERROR: "ahci_platform_suspend_host" [drivers/ata/ahci_mvebu.ko] undefined!
ERROR: "ahci_platform_resume_host" [drivers/ata/ahci_mvebu.ko] undefined!
This adds the same #ifdef here
Hi, Ingi.
Merged. Thanks for your first patch to drm world. :)
This patch isn't trivial so will go to next.
Thanks,
Inki Dae
2015년 10월 02일 17:59에 Ingi Kim 이(가) 쓴 글:
> This patch fixes spelling errors in drm fimc/gsc
> inavild -> invaild
>
> Signed-off-by: Ingi Kim
> ---
>
I got a report about unkillable task eating CPU. Further
investigation shows, that the problem is in the fuse_fill_write_pages()
function. If iov's first segment has zero length, we get an infinite
loop, because we never reach iov_iter_advance() call.
Fix this by calling iov_iter_advance() before
On Monday 12 October 2015 15:27:03 Thomas Petazzoni wrote:
> Arnd,
>
> On Mon, 12 Oct 2015 15:05:27 +0200, Arnd Bergmann wrote:
>
> > +#ifdef CONFIG_PM_SUSPEND
>
> Shouldn't this be CONFIG_PM_SLEEP ?
>
> The generic suspend/resume function in libahci_platform.c are defined
> when
On 29/05/15 06:38, AKASHI Takahiro wrote:
> The current kvm implementation on arm64 does cpu-specific initialization
> at system boot, and has no way to gracefully shutdown a core in terms of
> kvm. This prevents, especially, kexec from rebooting the system on a boot
> core in EL2.
>
> This patch
Arnd,
On Mon, 12 Oct 2015 15:05:27 +0200, Arnd Bergmann wrote:
> +#ifdef CONFIG_PM_SUSPEND
Shouldn't this be CONFIG_PM_SLEEP ?
The generic suspend/resume function in libahci_platform.c are defined
when CONFIG_PM_SLEEP is enabled.
Thomas
--
Thomas Petazzoni, CTO, Free Electrons
Embedded
On 08/10/15 10:23, Jon Medhurst (Tixy) wrote:
[...]
diff --git a/drivers/cpufreq/arm_big_little.c b/drivers/cpufreq/arm_big_little.c
index f1e42f8..59115a4 100644
--- a/drivers/cpufreq/arm_big_little.c
+++ b/drivers/cpufreq/arm_big_little.c
@@ -149,6 +149,18 @@ bL_cpufreq_set_rate(u32 cpu,
W dniu 12.10.2015 o 22:04, Jaehoon Chung pisze:
> On 10/12/2015 09:42 PM, Krzysztof Kozlowski wrote:
>> W dniu 12.10.2015 o 19:46, Anand Moon pisze:
>>> Hi Krzysztof,
>>>
>>> On 12 October 2015 at 11:14, Krzysztof Kozlowski
>>> wrote:
On 12.10.2015 00:46, Anand Moon wrote:
> Added
The davinci rtc driver uses the module_platform_driver_probe()
helper to call the probe function and mark it as __init, but
it also puts a reference into its davinci_rtc_driver function.
This will crash if we ever get a deferred probe and the probe
function is called again after the init section
This patch adds rt5033-led sub device to support it.
Signed-off-by: Ingi Kim
---
drivers/mfd/rt5033.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/mfd/rt5033.c b/drivers/mfd/rt5033.c
index d60f916..b7f374b 100644
--- a/drivers/mfd/rt5033.c
+++
This patch adds device driver of Richtek RT5033 PMIC.
The driver supports a current regulated output to drive
white LEDs for camera flash.
Signed-off-by: Ingi Kim
---
drivers/leds/Kconfig | 8 ++
drivers/leds/Makefile | 1 +
drivers/leds/leds-rt5033.c |
This patch adds the device tree bindings for RT5033 flash LEDs.
Signed-off-by: Ingi Kim
Acked-by: Rob Herring
---
.../devicetree/bindings/leds/leds-rt5033.txt | 38 ++
1 file changed, 38 insertions(+)
create mode 100644
This patch supports flash led of RT5033 PMIC.
Changes since v2:
- Split MFC code from rt5033 flash led patch
- Fix typo error
- Change naming of mfd register back again
- Fix compile error
Ingi Kim (3):
leds: rt5033: Add DT binding for RT5033
mfd: rt5033: Add RT5033 Flash led sub device
On Fri, 2015-10-09 at 19:55 +0200, Karsten Merker wrote:
> Implement support for the following device-tree properties
> in the goodix touchscreen driver:
>
> - touchscreen-inverted-x: X axis is inverted (boolean)
> - touchscreen-inverted-y: Y axis is inverted (boolean)
> -
On Fri, 2015-10-09 at 19:55 +0200, Karsten Merker wrote:
> The goodix touchscreen driver uses a "rotated_screen" flag for
> systems on which the touchscreen is mounted rotated by 180
> degrees with respect to the display. With the addition of
> support for the dt properties
On Fri, 2015-10-09 at 19:55 +0200, Karsten Merker wrote:
> Hello,
>
> this is v2 of my "Input: goodix - add axis swapping and axis
> inversion
> support" patchset.
> The goodix touchscreen driver has gained device-tree support in
> kernel
> 4.1, but doesn't currently support the
On Mon, Oct 12, 2015 at 01:54:38PM +0200, Peter Zijlstra wrote:
> On Mon, Oct 12, 2015 at 05:06:36PM +0800, Boqun Feng wrote:
> > Understood.
> >
> > But, IMO, the position of this section is already misleading:
> >
> > (*) Implicit kernel memory barriers.
> > - Locking functions.
> >
601 - 700 of 1976 matches
Mail list logo
