On 04/01/2014 04:06 AM, Tejun Heo wrote:
> On Mon, Mar 31, 2014 at 10:40:47PM +0800, Lai Jiangshan wrote:
>> Ping
>
> Lai, I'll keep the mail tagged but can you pleaes ping me once -rc1
> drops? While it is an actual bug, given that it'd be pretty difficult
> to trigger, I don't think it's too ur
Hi Davidlohr,
Thanks for the information!
According to lspci output, device :02:00.2 is HP ILO
controller, device :03:00.0 is RAID controller. Both ILO and
RAID controllers need to access reserved memory range
[0x7f61e000 - 0x7f61] in physical mode.
According to
On Mon, Apr 14, 2014 at 12:19:14AM -0400, Steven Galgano wrote:
> On 04/13/2014 09:40 PM, David Miller wrote:
> > From: Steven Galgano
> > Date: Sun, 13 Apr 2014 21:30:27 -0400
> >
> >> Added optional per queue flow control support using IFF_FLOW_CONTROL. When
> >> the IFF_FLOW_CONTROL TUNSETIFF
op 11-04-14 21:30, Thomas Hellstrom schreef:
Hi!
On 04/11/2014 08:09 PM, Maarten Lankhorst wrote:
op 11-04-14 12:11, Thomas Hellstrom schreef:
On 04/11/2014 11:24 AM, Maarten Lankhorst wrote:
op 11-04-14 10:38, Thomas Hellstrom schreef:
Hi, Maarten.
Here I believe we encounter a lot of lock
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
Sign
There are no users of pci_enable_msi_block() function have
left. Obsolete it in favor of pci_enable_msi_range() and
pci_enable_msi_exact() functions.
Up until now, when enabling MSI mode for a device, a single
successful call to arch_msi_check_device() was followed by
a single call to arch_setup_m
Hello,
This series is against 3.15-rc1.
This update obsoletes pci_enable_msi_block() function in
favor of pci_enable_msi_range() and pci_enable_msi_exact().
Cc: Frank Haverkamp
Cc: Greg Kroah-Hartman
Cc: linux-m...@linux-mips.org
Cc: linuxppc-...@lists.ozlabs.org
Cc: linux-s...@vger.kernel.or
* Matt Fleming wrote:
> On Fri, 11 Apr, at 11:03:13AM, H. Peter Anvin wrote:
> > On 04/11/2014 10:59 AM, Thomas Bächler wrote:
> > > EFI stub support is only missing for a 64 bit kernel on 32-bit firmware,
> > > on 64-bit kernels, EFI stub works as usual.
> > > ---
> > >
> > > Matt, I don't kno
EXYNOS5410 is SoC in Samsung's Exynos5 SoC series.
Add initial support for this SoC.
Signed-off-by: Tarek Dakhran
Signed-off-by: Vyacheslav Tyrtov
Reviewed-by: Tomasz Figa
---
arch/arm/mach-exynos/Kconfig |8
arch/arm/mach-exynos/exynos.c| 12
The series of patches represent support of Exynos 5410 SoC
The Exynos 5410 is the first Samsung SoC based on bigLITTLE architecture
Patches add new platform description, support of clock controller and device
tree for Exynos 5410.
Has been build on Linux Kernel v3.15-rc1
Has been tested on: 1) E
The EXYNOS5410 clocks are statically listed and registered
using the Samsung specific common clock helper functions.
Signed-off-by: Tarek Dakhran
Signed-off-by: Vyacheslav Tyrtov
Acked-by: Tomasz Figa
---
.../devicetree/bindings/clock/exynos5410-clock.txt | 51 +
drivers/clk/samsung/Make
Add initial device tree nodes for EXYNOS5410 SoC and SMDK5410 board.
Signed-off-by: Tarek Dakhran
Signed-off-by: Vyacheslav Tyrtov
Reviewed-by: Tomasz Figa
---
arch/arm/boot/dts/Makefile|1 +
arch/arm/boot/dts/exynos5410-smdk5410.dts | 65 ++
arch/arm/boot/dts
* Borislav Petkov wrote:
> On Sat, Apr 12, 2014 at 05:13:40PM -0400, Brian Gerst wrote:
> > Performance is bad in general, running a 32-bit Fedora 20 guest.
>
> So this means you haven't tried the game in the guest yet, so that
> we can know for sure that a guest doesn't solve your problem or
Commit-ID: 60e69eed85bb7b5198ef70643b5895c26ad76ef7
Gitweb: http://git.kernel.org/tip/60e69eed85bb7b5198ef70643b5895c26ad76ef7
Author: Mike Galbraith
AuthorDate: Mon, 7 Apr 2014 10:55:15 +0200
Committer: Ingo Molnar
CommitDate: Fri, 11 Apr 2014 10:39:15 +0200
sched/numa: Fix task_numa_
Hi Tony,
On 04/01/2014 05:13 PM, Felipe Balbi wrote:
> On Tue, Apr 01, 2014 at 01:37:27PM +0300, Roger Quadros wrote:
>> The USB3 PHY driver (ti-pipe3) was updated so that the relevant
>> clock phandles are expected in the DT node.
>> Provide the necessary clocks.
>>
>> Reported-by: Kishon Vijay A
There is memleak in alloc_pid:
--
unreferenced object 0xd3453a80 (size 64):
comm "adbd", pid 1730, jiffies 66363 (age 6586.950s)
hex dump (first 32 bytes):
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 40 c2 f6 d5 00 d3 25 c1 5
On Fri, Apr 11, 2014 at 11:05:30PM +0200, Fabian Frederick wrote:
> Ok, that would mean 'older' filesystems -without barrier flag-
> to call generic_file_fsync would result in a flush but ext4 without journal
> also calls it ; maybe with nobarrier and I'm not sure it's the only case.
> How can I d
Commit-ID: f96364041ccda63ff4bed96fd06b267d8d841dc0
Gitweb: http://git.kernel.org/tip/f96364041ccda63ff4bed96fd06b267d8d841dc0
Author: Antonio Borneo
AuthorDate: Sun, 13 Apr 2014 16:26:08 +0800
Committer: Ingo Molnar
CommitDate: Mon, 14 Apr 2014 08:50:36 +0200
x86/platform: Fix "make O
Commit-ID: a227960fe0cafcc229a8d6bb8b454a3a0b33719d
Gitweb: http://git.kernel.org/tip/a227960fe0cafcc229a8d6bb8b454a3a0b33719d
Author: Peter Zijlstra
AuthorDate: Thu, 10 Apr 2014 16:15:59 +0200
Committer: Ingo Molnar
CommitDate: Fri, 11 Apr 2014 10:40:35 +0200
locking/mutex: Fix debug_
Commit-ID: 86e587623a0ca8426267dad8d3eaebd6fc2d00f1
Gitweb: http://git.kernel.org/tip/86e587623a0ca8426267dad8d3eaebd6fc2d00f1
Author: Ville Syrjälä
AuthorDate: Sun, 13 Apr 2014 12:45:03 +0300
Committer: Ingo Molnar
CommitDate: Mon, 14 Apr 2014 08:50:56 +0200
x86/gpu: Fix sign extensio
* H. Peter Anvin wrote:
> On 04/11/2014 11:41 AM, Linus Torvalds wrote:
> >
> > Ok, so you actually do this on x86-64, and it currently works? For
> > some reason I thought that 16-bit windows apps already didn't work.
> >
>
> Some will work, because not all 16-bit software care about the upp
On 12 April 2014 14:56, Dietmar Eggemann wrote:
> On 11/04/14 10:44, Vincent Guittot wrote:
>>
>> This patchset was previously part of the larger tasks packing patchset
>> [1].
>> I have splitted the latter in 3 different patchsets (at least) to make the
>> thing easier.
>> -configuration of sched
Clear explanation and implementation!
Reviewed-by: Zhang Yanfei
On 04/11/2014 01:58 AM, Luiz Capitulino wrote:
> [Full introduction right after the changelog]
>
> Changelog
> -
>
> v3
>
> - Dropped unnecessary WARN_ON() call [Kirill]
> - Always check if the pfn range lies within a zon
According to commit 5f16f3225b0624
ext4: atomically set inode->i_flags in ext4_set_inode_flags()
Inspired-by: "Theodore Ts'o"
Cc: Dave Kleikamp
Cc: "Theodore Ts'o"
Signed-off-by: Fabian Frederick
---
fs/jfs/jfs_inode.c | 16
1 file changed, 8 insertions(+), 8 deletions(-)
d
There are a lot of ways we could approach this, and I sat down and wrote
the simplest variant I could think of, so hopefully there are not silly
bugs that get overlooked.
The code move all cleanup from mntput that would do filesystem I/O into
work queues.
The code waits in mntput for that I/O to
Clock providers should be initialized before clocksource_of_init.
If not, Clock source initialization can be fail to get the clock.
Signed-off-by: Chanho Min
---
arch/arm64/kernel/setup.c |1 -
arch/arm64/kernel/time.c |3 ++-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
This patch adds a kernel configuration for VA_BITS.
It helps to prevent unnecessary #ifdef statements insertions
for VA_BITS when implementing different page sizes and level of
translation tables.
Signed-off-by: Jungseok Lee
Reviewed-by: Sungjinn Chung
---
arch/arm64/Kconfig |
Remove the extra reference added to mnt_count by the mnt_pinned code,
and stop jumping to the top of mntput_no_expire.
When fput synchronously called mntput that extra reference count and
the loop ensured that after acct_auto_close_mnt closed all of the
pinned references mntput_no_expire would th
This patch fixed the following checkpatch complaint as using pr_*
instead of printk.
WARNING: printk() should include KERN_ facility level
Signed-off-by: Jungseok Lee
Reviewed-by: Sungjinn Chung
---
arch/arm64/kernel/traps.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-
This patch deals with checkpatch complaint as fixing line length
exceeding 80 characters.
WARNING: line over 80 characters
Signed-off-by: Jungseok Lee
Reviewed-by: Sungjinn Chung
---
arch/arm/kvm/mmu.c |4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/arm/kvm/mmu.
On 04/12/2014 01:54 AM, Timur Tabi wrote:
On Tue, Jun 18, 2013 at 6:33 AM, Mathias Nyman
wrote:
Pins may be muxed to alternate function instead of gpio by firmware.
This driver does not touch the pin muxing and expect firmare
to set pin muxing and pullup/down properties properly.
Signed-off-b
This patch adds 4 levels of translation tables implementation for both
HYP and stage2. A combination of 4KB + 4 levels host and 4KB + 4 levels
guest can run on ARMv8 architecture as introducing this feature.
Signed-off-by: Jungseok Lee
Reviewed-by: Sungjinn Chung
---
arch/arm/kvm/mmu.c
mntput as part of path_put is called from all over the vfs sometimes
as in the case of symlink chasing from some rather deep call chains.
During lazy filesystem unmount with the right set of races those
innocuous little mntput calls (that take very little stack space) can
call deactivate_super and
The autoclose of BSD accounting writes a record to the BSD accounting
file. When mntput is called from moderaly deep within the stack the
(3KiB or so) generating I/O can be problemenatic as some I/O paths
require nearly 5KiB of stack on their own.
Avoid the possibility of stack overflow by movin
op 11-04-14 21:35, Thomas Hellstrom schreef:
On 04/11/2014 08:09 PM, Maarten Lankhorst wrote:
op 11-04-14 12:11, Thomas Hellstrom schreef:
On 04/11/2014 11:24 AM, Maarten Lankhorst wrote:
op 11-04-14 10:38, Thomas Hellstrom schreef:
Hi, Maarten.
Here I believe we encounter a lot of locking i
Have the mntput that started the BSD accounting files closing block
until the superblock has been succesfully freed. This is what used to
happen until fput started calling mntput assynchronously, and is arguably
the right thing to do in the case of umount.
Signed-off-by: "Eric W. Biederman"
---
This patch implements 4 levels of translation tables since 3 levels
of page tables with 4KB pages cannot support 40-bit physical address
space described in [1] due to the following issue.
It is a restriction that kernel logical memory map with 4KB + 3 levels
(0xffc0-0x)
This patch adds hardware definition and types for 4 levels of
translation tables with 4KB pages.
Signed-off-by: Jungseok Lee
Reviewed-by: Sungjinn Chung
---
arch/arm64/include/asm/pgtable-4level-hwdef.h | 50 +
arch/arm64/include/asm/pgtable-4level-types.h | 71 +
The rtc-s5m driver does not support all of S2M and S5M chipsets
supported by main MFD sec-core driver. For such chipsets unsupported by
rtc-s5m, the MFD sec-core driver initialized regmap with default config.
This config in such cases wouldn't work at all.
The main MFD sec-core driver shouldn't in
This patch adds memory layout and translation lookup information
about 48-bit address space with 4K pages. The description is based
on 4 levels of translation tables.
Signed-off-by: Jungseok Lee
Reviewed-by: Sungjinn Chung
---
Documentation/arm64/memory.txt | 59 ++
On 04/14/2014 09:42 AM, Maarten Lankhorst wrote:
> op 11-04-14 21:35, Thomas Hellstrom schreef:
>> On 04/11/2014 08:09 PM, Maarten Lankhorst wrote:
>>> op 11-04-14 12:11, Thomas Hellstrom schreef:
On 04/11/2014 11:24 AM, Maarten Lankhorst wrote:
> op 11-04-14 10:38, Thomas Hellstrom schree
This patch separates page size from level of translation tables in
configuration. It facilitates introduction of different options,
such as 4KB + 4 levels, 16KB + 4 levels and 64KB + 3 levels, easily.
Signed-off-by: Jungseok Lee
Reviewed-by: Sungjinn Chung
---
arch/arm64/Kconfig
Hi All,
This patchset supports 4 levels of tranlsation tables for ARM64.
Firstly, the patchset decouples page size from level of translation tables
as taking account into the comment from Catalin Marinas:
http://www.spinics.net/linux/lists/arm-kernel/msg319552.html
Then, it implements 4 levels o
I noticed following lockdep warning when trying acpi hot-remove cpus:
[84154.204080] ==
[84154.204080] [ INFO: possible circular locking dependency detected ]
[84154.204080] 3.14.0-next-20140408+ #24 Tainted: GW
[84154.204080] ---
There is memleak in alloc_pid:
--
unreferenced object 0xd3453a80 (size 64):
comm "adbd", pid 1730, jiffies 66363 (age 6586.950s)
hex dump (first 32 bytes):
01 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
00 00 00 00 40 c2 f6 d5 00 d3 25 c1 5
On April 14, 2014 2:51:22 AM GMT+01:00, Srinivas Pandruvada
wrote:
>
>On 04/12/2014 09:52 AM, Jonathan Cameron wrote:
>> On 09/04/14 01:56, Srinivas Pandruvada wrote:
>>> This callback is introduced to overcome some limitations of existing
>>> read_raw callback. The functionality of both existi
Hi,
This is a resend of third version of patchset adding support for
the S2MPS14 device to the s2mps11 clock driver.
Previous discusson can be found here:
http://thread.gmane.org/gmane.linux.kernel.samsung-soc/28039
Changes since v2:
=
1. Patch 2/3: Remove MFD cells of_compatible
This patch adds support for S2MPS14 PMIC clocks (BT and AP) to the
s2mps11 clock driver.
Signed-off-by: Krzysztof Kozlowski
Cc: Kyungmin Park
Reviewed-by: Yadwinder Singh Brar
Reviewed-by: Tomasz Figa
---
drivers/clk/Kconfig | 8 +++
drivers/clk/clk-s2mps11.c | 61 +
2014-04-14 15:50 GMT+09:00 Lai Jiangshan :
> On 04/14/2014 08:58 AM, Daeseok Youn wrote:
>>
>> mutex_unlock() and put_pwq_unlocked() do not need to be called
>> when alloc_unbound_pwq() is failed.
>>
>> Signed-off-by: Daeseok Youn
>> ---
>> kernel/workqueue.c |2 +-
>> 1 files changed, 1 inse
Rely on EV_SW and SW_LID bits to identify a LID device, and hook
up our filter to listen for SW_LID events to enable/disable touchpad when
LID is open/closed.
TEST=test on Chomebooks.
Signed-off-by: Du, Dudley
---
diff --git a/drivers/input/mouse/cyapa.c b/drivers/input/mouse/cyapa.c
index 6820b3
This patch set is made based on kernel 3.14.0. It's aimed to
re-architecture the cyapa driver to support the old gen3 trackpad
device and new gen5 trackpad device in one cyapa driver for
easily products support based on customers' requirements,
and add sysfs functions and interfaces supported that
In order to save power when the trackpad device is not used, the sleep power
mode and runtime power mode must be supported. And the enter sleep time can
be configured in the sysfs system.
TEST=test on Chomebooks.
Signed-off-by: Du, Dudley
---
diff --git a/drivers/input/mouse/cyapa.c b/drivers/inp
Hi Andi,
I would like to ask for your help.
Is there a central kernel function that enables/disables write-protection for
kernel memory?
I only know the place, where its write protected at booting for x86/x64.
If there is one place, it would be much easier, as to hook into many places
(e.g. ftra
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
Sign
Linus Torvalds writes:
> On Fri, Apr 11, 2014 at 11:45 AM, Brian Gerst wrote:
>>
>> I haven't tested it recently but I do know it has worked on 64-bit
>> kernels. There is no reason for it not to, the only thing not
>> supported in long mode is vm86. 16-bit protected mode is unchanged.
>
> Afa
Currently the driver falls back to INTx mode when MSI-X
initialization failed. This is a suboptimal behaviour
for chips that also support MSI. This update changes that
behaviour and falls back to MSI mode in case MSI-X mode
initialization failed.
Signed-off-by: Alexander Gordeev
Cc: "Stephen M. C
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
Sign
As usual, the executive friendly graph is at
http://neuling.org/linux-next-size.html :-)
(No merge commits counted, next-20140331 was the last linux-next before
v3.14. I neglected to publish the stats for v3.14-rc1, but they are
mentioned below.)
Commits in v3.15-rc1 (relative to v3.14): 12034
When a call to request_irq() failed pm8001_setup_msix()
still returns the success. This udate fixes the described
misbehaviour.
Signed-off-by: Alexander Gordeev
Cc: xjtu...@gmail.com
Cc: lindar_...@usish.com
Cc: linux-s...@vger.kernel.org
Cc: linux-...@vger.kernel.org
Acked-by: Jack Wang
---
dr
'make savedefconfig' doesn't generate defconfig properly due to
missing COMPAT default. So Add default and set to yes.
Signed-off-by: Chanho Min
---
arch/arm64/Kconfig |1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/Kconfig b/arch/arm64/Kconfig
index 4907b85..93b7531 100644
---
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
Sign
Change the binding for regulators external control to the same used in
s2mps11 driver to be consistent.
Signed-off-by: Krzysztof Kozlowski
Cc: Tomasz Figa
Cc: devicet...@vger.kernel.org
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
Cc: Ian Campbell
Cc: Kumar Gala
---
Documentation/device
Add support for external control over GPIO for LDO10, LDO11 and LDO12
S2MPS14 regulators. External control can be turned on by writing 0x0 to
control register which in case of other regulators is used for disabling
them. These LDO10-LDO12 regulators can be disabled only by I2C GPIO or
PWREN pin so
On Sat, Apr 12, 2014 at 09:58:51PM +0800, Chew Chiau Ee wrote:
> From: Alan Cox
>
> Not all systems enumerate the PWM devices via ACPI. They can also be exposed
> via the PCI interface.
>
> Signed-off-by: Alan Cox
> Signed-off-by: Chew, Chiau Ee
> ---
> drivers/pwm/pwm-lpss.c | 160 +
Hi,
This patchset adds external GPIO control to s2mps11 regulator driver
for some of the S2MPS14 regulators.
Additionally (patch 4/4) it changes the bindings in s5m8767 regulator driver
for external control to match these used here:
"samsung,ext-control-gpios"
Best regards,
Krzysztof
Kr
Johannes/Michal
What are your thoughts on this matter? Do you see this as a valid
requirement?
Regards,
Glyn
On 02/04/2014 19:00, Tejun Heo wrote:
(cc'ing memcg maintainers and cgroup ML)
On Wed, Apr 02, 2014 at 02:08:04PM +0100, Glyn Normington wrote:
Currently, a memory cgroup can hit it
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
Sign
Add documentation for new property for controlling (enable/disable) some
of the S2MPS14 regulators by GPIO.
Signed-off-by: Krzysztof Kozlowski
Cc: Tomasz Figa
Cc: devicet...@vger.kernel.org
Cc: Rob Herring
Cc: Pawel Moll
Cc: Mark Rutland
Cc: Ian Campbell
Cc: Kumar Gala
---
Documentation/de
Hi Felipe,
On Sat, Apr 12, 2014 at 9:07 AM, Felipe Balbi wrote:
> On Wed, Apr 09, 2014 at 05:24:45PM +0530, Vivek Gautam wrote:
>> Adding support to enable/disable VBUS hooked to a gpio
>> to enable vbus supply on the port.
>>
>> Signed-off-by: Vivek Gautam
>> ---
>>
>> Based on 'phy-exynos5-us
Signed-off-by: Alexander Gordeev
Cc: Anil Ravindranath
Cc: linux-s...@vger.kernel.org
Cc: linux-...@vger.kernel.org
---
drivers/scsi/pmcraid.c |1 -
1 files changed, 0 insertions(+), 1 deletions(-)
diff --git a/drivers/scsi/pmcraid.c b/drivers/scsi/pmcraid.c
index be8ce54..c06af7f 100644
--
Refactor code for parsing DTS to increase a little code readability. The
behaviour should not change.
Signed-off-by: Krzysztof Kozlowski
---
drivers/regulator/s2mps11.c | 35 +++
1 file changed, 23 insertions(+), 12 deletions(-)
diff --git a/drivers/regulator/s2m
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
Log
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
Sign
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
Sign
>>> On 12.04.14 at 07:56, wrote:
> --- a/arch/x86/kernel/i8259.c
> +++ b/arch/x86/kernel/i8259.c
> @@ -299,11 +299,30 @@ static void unmask_8259A(void)
> static void init_8259A(int auto_eoi)
> {
> unsigned long flags;
> + unsigned char probe_val = ~(1 << PIC_CASCADE_IR);
> + unsign
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
Sign
This patch encloses sam9n12 old clk registration in
"#if defined(CONFIG_OLD_CLK_AT91) #endif" sections.
Signed-off-by: Boris BREZILLON
---
arch/arm/mach-at91/at91sam9n12.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/arch/arm/mach-at91/at91sam9n12.c b/arch/arm/mach-at
Define sam9n12 clocks and make use of them in peripheral definitions.
Signed-off-by: Boris BREZILLON
---
arch/arm/boot/dts/at91sam9n12.dtsi | 350 -
1 file changed, 348 insertions(+), 2 deletions(-)
diff --git a/arch/arm/boot/dts/at91sam9n12.dtsi
b/arch/arm/
Define sam9n12ek's main and slow crystal frequencies.
Signed-off-by: Boris BREZILLON
---
arch/arm/boot/dts/at91sam9n12ek.dts | 8
1 file changed, 8 insertions(+)
diff --git a/arch/arm/boot/dts/at91sam9n12ek.dts
b/arch/arm/boot/dts/at91sam9n12ek.dts
index 924a6a6..6132769 100644
--- a/
This patch removes the selection of AT91_USE_OLD_CLK when selecting
sam9n12 SoC support. This will automatically enable COMMON_CLK_AT91 option
and add support for at91 common clk implementation.
Signed-off-by: Boris BREZILLON
---
arch/arm/mach-at91/Kconfig | 1 -
1 file changed, 1 deletion(-)
d
Hello,
This series moves the at91sam9n12 SoC and the at91sam9n12-ek board to
the Common Clock Framework.
It depends on this series [1], which introduces new slow clock and main
clock implementation (and DT bindings) for at91 SoCs.
Best Regards,
Boris
[1] http://lkml.iu.edu/hypermail/linux/kern
hi
i'm unsuccessfully trying to boot a linux kernel on an intel atom z2760 right
now but somehow the boot up process appears to be crashing the cpu right at
the beginning of the load process.
not even the uefi early_printk's appear to be reached, so it must be the
setup.S or something like this.
s
Hi Courtney,
On 04/09/2014 01:00 AM, Courtney Cavin wrote:
> On Tue, Apr 08, 2014 at 06:26:44PM +0200, Stanimir Varbanov wrote:
>> On 04/04/2014 02:38 AM, Courtney Cavin wrote:
>>> On Thu, Apr 03, 2014 at 06:17:58PM +0200, Stanimir Varbanov wrote:
This adds core driver files. The core part is
Hi Jonathan,
I realise you didn't send any pull request for 3.15 yet, do you intend
to send it soon. As you know, I have a patch set depending on a few
patches and I'd like to rebase and resend it soon.
Regards,
--
Alexandre Belloni, Free Electrons
Embedded Linux, Kernel and Android engineering
* Rik van Riel wrote:
> On 04/11/2014 01:46 PM, Joe Perches wrote:
> > On Fri, 2014-04-11 at 13:00 -0400, r...@redhat.com wrote:
> >> This patch reduces the interval at which migration is retried,
> >> when the task's numa_scan_period is small.
> >
> > More style trivia and a question.
[...]
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
Sign
This adds support for GPIO controlled reset pins on peripheral ICs to the reset
controller framework. Currently there is no support for specifying a delay
between assertion and de-assertion of the reset signal, so this has to be
handled by the drivers.
Signed-off-by: Philipp Zabel
---
Changes sin
Currently the driver fails to analize MSI-X re-enablement
status on resuming and always assumes the success. This
update checks the MSI-X initialization result and fails
to resume if MSI-Xs re-enablement failed.
Signed-off-by: Alexander Gordeev
---
drivers/scsi/megaraid/megaraid_sas_base.c |
This patch adds documentation clarifying the reset GPIO bindings most
commonly in use (reset-gpios and -reset-gpios properties).
Signed-off-by: Philipp Zabel
---
Documentation/devicetree/bindings/reset/reset.txt | 26 +--
1 file changed, 24 insertions(+), 2 deletions(-)
diff
There is no need to call pci_disable_msix() in case
the previous call to pci_enable_msix() failed
Signed-off-by: Alexander Gordeev
Cc: James Smart
Cc: linux-s...@vger.kernel.org
Cc: linux-...@vger.kernel.org
Acked-by: James Smart
---
drivers/scsi/lpfc/lpfc_init.c |9 ++---
1 files chan
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
Sign
Hi Stephen,
On 04/11/2014 11:12 PM, Stephen Boyd wrote:
> On 04/10, Stanimir Varbanov wrote:
>> On 04/09/2014 03:09 AM, Stephen Boyd wrote:
>>> On 04/03, Stanimir Varbanov wrote:
>>>
+
+ return 0;
+}
+
+static int qce_ahash_import(struct ahash_request *req, const void *in
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
Sign
There is no need to call pci_disable_msix() in case
the previous call to pci_enable_msix() failed
Signed-off-by: Alexander Gordeev
Cc: Naresh Kumar Inna
Cc: Arvind Bhushan
Cc: linux-s...@vger.kernel.org
Cc: linux-...@vger.kernel.org
---
drivers/scsi/csiostor/csio_isr.c |4 +---
1 files cha
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
Sign
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
Sign
Function pci_enable_msix() should not be called in case
it threw a negative errno from a previous call.
Signed-off-by: Alexander Gordeev
Cc: Anil Gurumurthy
Cc: Vijaya Mohan Guvva
Cc: linux-s...@vger.kernel.org
Cc: linux-...@vger.kernel.org
Acked-by: Anil Gurumurthy
---
drivers/scsi/bfa/bfad.
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
Sign
As result of deprecation of MSI-X/MSI enablement functions
pci_enable_msix() and pci_enable_msi_block() all drivers
using these two interfaces need to be updated to use the
new pci_enable_msi_range() or pci_enable_msi_exact()
and pci_enable_msix_range() or pci_enable_msix_exact()
interfaces.
Sign
This is the majority of the blk-mq work still required for switching
over SCSI. There are a few more bits for I/O completion and requeueing
pending, but they will need further work.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vg
1 - 100 of 1035 matches
Mail list logo
