On Wed, May 11, 2016 at 12:27:14PM -0400, Prarit Bhargava wrote:
> commit b894157145e4 ("x86/PCI: Mark Broadwell-EP Home Agent & PCU as having
> non-compliant BARs") marks Home Agent 0 & PCU has having non-compliant
> BARs. commit b84106b4e229 ("PCI: Disable IO/MEM decoding for devices with
>
On Wed, May 11, 2016 at 12:27:14PM -0400, Prarit Bhargava wrote:
> commit b894157145e4 ("x86/PCI: Mark Broadwell-EP Home Agent & PCU as having
> non-compliant BARs") marks Home Agent 0 & PCU has having non-compliant
> BARs. commit b84106b4e229 ("PCI: Disable IO/MEM decoding for devices with
>
The following changes since commit 1993b176a8224e371e0732ffada7ab9eb3b0912b:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/ide (2016-03-28
15:17:02 -0500)
are available in the git repository at:
git://github.com/kleikamp/linux-shaggy.git tags/jfs-4.7
for you to fetch changes
The following changes since commit 1993b176a8224e371e0732ffada7ab9eb3b0912b:
Merge git://git.kernel.org/pub/scm/linux/kernel/git/davem/ide (2016-03-28
15:17:02 -0500)
are available in the git repository at:
git://github.com/kleikamp/linux-shaggy.git tags/jfs-4.7
for you to fetch changes
On 5/16/16, Jeff Merkey wrote:
> On 5/15/16, OenHan wrote:
>> Maybe you should install kexec-tools or uncheck kdump options in .config:
>>
>> rpm -qf /lib/kdump/kdump-lib.sh
>> kexec-tools-2.0.7-38.el7_2.1.x86_64
>>
The problem here is that Centos 7 has
On 5/16/16, Jeff Merkey wrote:
> On 5/15/16, OenHan wrote:
>> Maybe you should install kexec-tools or uncheck kdump options in .config:
>>
>> rpm -qf /lib/kdump/kdump-lib.sh
>> kexec-tools-2.0.7-38.el7_2.1.x86_64
>>
The problem here is that Centos 7 has the script at /usr/lib/kdump
instead of
On Fri, 2016-05-13 at 14:56 +0900, Ethan Zhao wrote:
> Allocating 64 Tx/Rx as default doesn't benefit perfomrnace when less
> CPUs were assigned. especially when DCB is enabled, so we should take
> num_online_cpus() as top limit, and aslo to make sure every TC has
> at least one queue, take the
On Fri, 2016-05-13 at 14:56 +0900, Ethan Zhao wrote:
> Allocating 64 Tx/Rx as default doesn't benefit perfomrnace when less
> CPUs were assigned. especially when DCB is enabled, so we should take
> num_online_cpus() as top limit, and aslo to make sure every TC has
> at least one queue, take the
From: Daniel Hung-yu Wu
Add I2C driver for Atmel Capacitive Touch Button device.
Signed-off-by: Hung-yu Wu
Signed-off-by: Grant Grundler
---
drivers/input/misc/Kconfig | 13 ++
drivers/input/misc/Makefile | 1 +
From: Daniel Hung-yu Wu
Add I2C driver for Atmel Capacitive Touch Button device.
Signed-off-by: Hung-yu Wu
Signed-off-by: Grant Grundler
---
drivers/input/misc/Kconfig | 13 ++
drivers/input/misc/Makefile | 1 +
drivers/input/misc/atmel_captouch.c | 287
From: Daniel Hung-yu Wu
Add binding for Atmel Capacitive Touch Button device.
Signed-off-by: Daniel Hung-yu Wu
Signed-off-by: Grant Grundler
---
.../devicetree/bindings/input/atmel,captouch.txt | 36 ++
1 file
From: Daniel Hung-yu Wu
Add binding for Atmel Capacitive Touch Button device.
Signed-off-by: Daniel Hung-yu Wu
Signed-off-by: Grant Grundler
---
.../devicetree/bindings/input/atmel,captouch.txt | 36 ++
1 file changed, 34 insertions(+)
create mode 100644
On 05/14/2016 09:16 PM, Tadeusz Struk wrote:
> First four patches are a resend of the v3 algif_akcipher from
> Stephan Mueller, with minor changes after rebase on top of 4.6-rc1.
>
> The next three patches add support for keys stored in system
> keyring subsystem.
>
> First patch adds
On 05/14/2016 09:16 PM, Tadeusz Struk wrote:
> First four patches are a resend of the v3 algif_akcipher from
> Stephan Mueller, with minor changes after rebase on top of 4.6-rc1.
>
> The next three patches add support for keys stored in system
> keyring subsystem.
>
> First patch adds
On Thu, 12 May 2016 16:08:34 +0200
Daniel Wagner wrote:
> In short, I haven't figured out yet why the kernel builds get slightly
> slower.
You're doing make -j 200, right? How many cores do you have? Couldn't it
be that you're saturating your CPUs?
You could try make -j, or
On Thu, 12 May 2016 16:08:34 +0200
Daniel Wagner wrote:
> In short, I haven't figured out yet why the kernel builds get slightly
> slower.
You're doing make -j 200, right? How many cores do you have? Couldn't it
be that you're saturating your CPUs?
You could try make -j, or some process
On Thu, 28 Apr 2016 14:57:24 +0200
Daniel Wagner wrote:
> From: Daniel Wagner
>
> Completions have no long lasting callbacks and therefore do not need
> the complex waitqueue variant. Use simple waitqueues which reduces
> the contention on the
On Thu, 28 Apr 2016 14:57:24 +0200
Daniel Wagner wrote:
> From: Daniel Wagner
>
> Completions have no long lasting callbacks and therefore do not need
> the complex waitqueue variant. Use simple waitqueues which reduces
> the contention on the waitqueue lock.
>
> This was a carry forward
Replying to thread:
https://lkml.org/lkml/2016/2/26/1090
> -Original Message-
> From: James Bottomley [mailto:james.bottom...@hansenpartnership.com]
> Sent: Thursday, January 28, 2016 7:37 AM
> To: Olaf Hering
> Cc: KY Srinivasan ; Haiyang Zhang
>
Replying to thread:
https://lkml.org/lkml/2016/2/26/1090
> -Original Message-
> From: James Bottomley [mailto:james.bottom...@hansenpartnership.com]
> Sent: Thursday, January 28, 2016 7:37 AM
> To: Olaf Hering
> Cc: KY Srinivasan ; Haiyang Zhang
> ; linux-kernel@vger.kernel.org; linux-
From: Jan Beulich
The switch to elf_getshdr{num,strndx} post-dates the oldest tool chain
the kernel is supposed to be able to build with, so try to cope with
such an environment.
Signed-off-by: Jan Beulich
Signed-off-by: Josh Poimboeuf
On Mon, May 16, 2016 at 7:55 AM, Ingo Molnar wrote:
>
> This tree, by Michal Hocko, implements down_write_killable(). The main usecase
> will be to update mm_sem usage sites to use this new API,
Hmm. Is somebody (Michal?) looking at down_read_killable() too?
The VFS layer will
From: Jan Beulich
The switch to elf_getshdr{num,strndx} post-dates the oldest tool chain
the kernel is supposed to be able to build with, so try to cope with
such an environment.
Signed-off-by: Jan Beulich
Signed-off-by: Josh Poimboeuf
---
tools/objtool/Makefile | 4
tools/objtool/elf.h
On Mon, May 16, 2016 at 7:55 AM, Ingo Molnar wrote:
>
> This tree, by Michal Hocko, implements down_write_killable(). The main usecase
> will be to update mm_sem usage sites to use this new API,
Hmm. Is somebody (Michal?) looking at down_read_killable() too?
The VFS layer will want it with the
On 05/16/2016 01:52 PM, Alexander Graf wrote:
> If you compile without OF_MDIO support in an RGMII configuration, we fail
> to configure the dp83867 phy today by writing garbage into its configuration
> registers.
>
> On the other hand if you do compile with OF_MDIO and the phy gets loaded via
>
Signed-off-by: David Mosberger
---
.../devicetree/bindings/nvmem/atmel-secumod.txt| 46
drivers/nvmem/atmel-secumod.c | 125 +
2 files changed, 171 insertions(+)
create mode 100644
On 05/16/2016 01:52 PM, Alexander Graf wrote:
> If you compile without OF_MDIO support in an RGMII configuration, we fail
> to configure the dp83867 phy today by writing garbage into its configuration
> registers.
>
> On the other hand if you do compile with OF_MDIO and the phy gets loaded via
>
Signed-off-by: David Mosberger
---
.../devicetree/bindings/nvmem/atmel-secumod.txt| 46
drivers/nvmem/atmel-secumod.c | 125 +
2 files changed, 171 insertions(+)
create mode 100644 Documentation/devicetree/bindings/nvmem/atmel-secumod.txt
On Friday 05/13 at 21:17 +, Elliott, Robert (Persistent Memory) wrote:
>
>
> > -Original Message-
> > From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> > ow...@vger.kernel.org] On Behalf Of Calvin Owens
> > Sent: Friday, May 13, 2016 3:28 PM
> ...
> > Subject: [PATCH]
On Friday 05/13 at 21:17 +, Elliott, Robert (Persistent Memory) wrote:
>
>
> > -Original Message-
> > From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> > ow...@vger.kernel.org] On Behalf Of Calvin Owens
> > Sent: Friday, May 13, 2016 3:28 PM
> ...
> > Subject: [PATCH]
On Mon, May 16, 2016 at 01:05:45PM -0700, Linus Torvalds wrote:
> On Mon, May 16, 2016 at 7:46 AM, Ingo Molnar wrote:
> >
> > Please pull the latest efi-urgent-for-linus git tree from:
> >
> >git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> > efi-urgent-for-linus
On Mon, May 16, 2016 at 01:05:45PM -0700, Linus Torvalds wrote:
> On Mon, May 16, 2016 at 7:46 AM, Ingo Molnar wrote:
> >
> > Please pull the latest efi-urgent-for-linus git tree from:
> >
> >git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> > efi-urgent-for-linus
> >
> >#
Add a description of the target root overlay method to the overlay
documention file.
Signed-off-by: Pantelis Antoniou
---
Documentation/devicetree/overlay-notes.txt | 8
1 file changed, 8 insertions(+)
diff --git
Add a description of the target root overlay method to the overlay
documention file.
Signed-off-by: Pantelis Antoniou
---
Documentation/devicetree/overlay-notes.txt | 8
1 file changed, 8 insertions(+)
diff --git a/Documentation/devicetree/overlay-notes.txt
This patchset implements two new target methods.
A target index method which allows selecting different
targets according to an argument using an extended API and
a target root method that fences the target only
to a specific given root.
Documentation and unit-tests are included.
Changes since
Add unittests for target-root based overlays.
Signed-off-by: Pantelis Antoniou
---
drivers/of/unittest-data/testcases.dts | 5 +
drivers/of/unittest-data/tests-overlay.dtsi | 48 +++
drivers/of/unittest.c | 213
This patchset implements two new target methods.
A target index method which allows selecting different
targets according to an argument using an extended API and
a target root method that fences the target only
to a specific given root.
Documentation and unit-tests are included.
Changes since
Add unittests for target-root based overlays.
Signed-off-by: Pantelis Antoniou
---
drivers/of/unittest-data/testcases.dts | 5 +
drivers/of/unittest-data/tests-overlay.dtsi | 48 +++
drivers/of/unittest.c | 213
3 files changed, 266
Some applications require applying the same overlay to a different
target according to some external condition (for instance depending
on the slot a card has been inserted, the overlay target is different).
The target index functionality use requires using the new
of_overlay_create_target_index()
The target facility of an overlay allows the target to be any point
in the live kernel tree, since it usually that's required when
creating overlays for internal SoC devices. The target ends up
to be a single node in the tree.
However when we're dealing with probeable busses this is a problem
Some applications require applying the same overlay to a different
target according to some external condition (for instance depending
on the slot a card has been inserted, the overlay target is different).
The target index functionality use requires using the new
of_overlay_create_target_index()
The target facility of an overlay allows the target to be any point
in the live kernel tree, since it usually that's required when
creating overlays for internal SoC devices. The target ends up
to be a single node in the tree.
However when we're dealing with probeable busses this is a problem
Add a unittest for the indirect overlay target case.
Signed-off-by: Pantelis Antoniou
---
drivers/of/unittest-data/testcases.dts | 5 +++
drivers/of/unittest-data/tests-overlay.dtsi | 15
drivers/of/unittest.c | 60
Add a description of the target index overlay method to the overlay
documention file.
Signed-off-by: Pantelis Antoniou
---
Documentation/devicetree/overlay-notes.txt | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git
Add a unittest for the indirect overlay target case.
Signed-off-by: Pantelis Antoniou
---
drivers/of/unittest-data/testcases.dts | 5 +++
drivers/of/unittest-data/tests-overlay.dtsi | 15
drivers/of/unittest.c | 60 +
3 files
Add a description of the target index overlay method to the overlay
documention file.
Signed-off-by: Pantelis Antoniou
---
Documentation/devicetree/overlay-notes.txt | 14 --
1 file changed, 12 insertions(+), 2 deletions(-)
diff --git a/Documentation/devicetree/overlay-notes.txt
Hi,
On Mon, May 16, 2016 at 6:57 AM, David Wu wrote:
> There are three points differert from others:
> - new method to caculate i2c timings for rk3399
> - pclk and function clk are separated at rk3399
> - add fast-plus mode supported for rk3399
>
> David Wu (8):
>
Hi,
On Mon, May 16, 2016 at 6:57 AM, David Wu wrote:
> There are three points differert from others:
> - new method to caculate i2c timings for rk3399
> - pclk and function clk are separated at rk3399
> - add fast-plus mode supported for rk3399
>
> David Wu (8):
> i2c: rk3x: add
On Mon, May 16, 2016 at 11:31:12AM -0700, Megha Dey wrote:
> On Mon, 2016-05-16 at 09:44 -0500, Josh Poimboeuf wrote:
> > On Fri, May 13, 2016 at 10:32:26AM -0700, Megha Dey wrote:
> > > On Fri, 2016-05-13 at 07:51 +0200, Ingo Molnar wrote:
> > > > * Herbert Xu wrote:
On Mon, May 16, 2016 at 11:31:12AM -0700, Megha Dey wrote:
> On Mon, 2016-05-16 at 09:44 -0500, Josh Poimboeuf wrote:
> > On Fri, May 13, 2016 at 10:32:26AM -0700, Megha Dey wrote:
> > > On Fri, 2016-05-13 at 07:51 +0200, Ingo Molnar wrote:
> > > > * Herbert Xu wrote:
> > > >
> > > > > On Thu,
On Mon, May 16, 2016 at 08:52:43PM +0200, Alexander Graf wrote:
> If you compile without OF_MDIO support in an RGMII configuration, we fail
> to configure the dp83867 phy today by writing garbage into its configuration
> registers.
>
> On the other hand if you do compile with OF_MDIO and the phy
On Mon, May 16, 2016 at 08:52:43PM +0200, Alexander Graf wrote:
> If you compile without OF_MDIO support in an RGMII configuration, we fail
> to configure the dp83867 phy today by writing garbage into its configuration
> registers.
>
> On the other hand if you do compile with OF_MDIO and the phy
Hi Rob,
> On May 16, 2016, at 22:37 , Rob Herring wrote:
>
> On Mon, May 16, 2016 at 11:52 AM, Pantelis Antoniou
> wrote:
>> When a device tree contains a lot of phandles, resolving one
>> takes time because the original method uses a
Hi Rob,
> On May 16, 2016, at 22:37 , Rob Herring wrote:
>
> On Mon, May 16, 2016 at 11:52 AM, Pantelis Antoniou
> wrote:
>> When a device tree contains a lot of phandles, resolving one
>> takes time because the original method uses a search against
>> all nodes (not just the ones with
Hi
In the kernel 4.6 I get crashes in the tty layer. I can reproduce the
crash by logging into the machine with ssh and typing before the prompt
appears.
The crash is caused by the pointer tty->disc_data being NULL in the
function n_tty_receive_buf_common. The crash happens on the statement
Hi
In the kernel 4.6 I get crashes in the tty layer. I can reproduce the
crash by logging into the machine with ssh and typing before the prompt
appears.
The crash is caused by the pointer tty->disc_data being NULL in the
function n_tty_receive_buf_common. The crash happens on the statement
When acquiring the rwsem write lock in the slowpath, we first try
to set count to RWSEM_WAITING_BIAS. When that is successful,
we then atomically add the RWSEM_WAITING_BIAS in cases where
there are other tasks on the wait list. This causes write lock
operations to often issue multiple atomic
When acquiring the rwsem write lock in the slowpath, we first try
to set count to RWSEM_WAITING_BIAS. When that is successful,
we then atomically add the RWSEM_WAITING_BIAS in cases where
there are other tasks on the wait list. This causes write lock
operations to often issue multiple atomic
From: David Wu
We've got 9 (count em!) i2c controllers on rk3399, some of which are in
the PMU power domain and some of which are normal peripherals. Add them
all to the main rk3399 dtsi file so future patches can turn them on in
the board dts files.
Note: by default
From: David Wu
We've got 9 (count em!) i2c controllers on rk3399, some of which are in
the PMU power domain and some of which are normal peripherals. Add them
all to the main rk3399 dtsi file so future patches can turn them on in
the board dts files.
Note: by default we try to set the i2c
On Mon, May 16, 2016 at 7:46 AM, Ingo Molnar wrote:
>
> Please pull the latest efi-urgent-for-linus git tree from:
>
>git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> efi-urgent-for-linus
>
># HEAD: bea23c757f66d91dac8fdadd94da0cba6b0b66bc x86/efi: Fix 7th
On Mon, May 16, 2016 at 7:46 AM, Ingo Molnar wrote:
>
> Please pull the latest efi-urgent-for-linus git tree from:
>
>git://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git
> efi-urgent-for-linus
>
># HEAD: bea23c757f66d91dac8fdadd94da0cba6b0b66bc x86/efi: Fix 7th argument
> to
On Mon, 16 May, at 09:58:33AM, Steven Rostedt wrote:
>
> Can we solve this by doing the same thing it did for the kernel?
>
> -- Steve
>
> diff --git a/arch/x86/kernel/mcount_64.S b/arch/x86/kernel/mcount_64.S
> index ed48a9f465f8..e13a695c3084 100644
> --- a/arch/x86/kernel/mcount_64.S
> +++
On Mon, 16 May, at 09:58:33AM, Steven Rostedt wrote:
>
> Can we solve this by doing the same thing it did for the kernel?
>
> -- Steve
>
> diff --git a/arch/x86/kernel/mcount_64.S b/arch/x86/kernel/mcount_64.S
> index ed48a9f465f8..e13a695c3084 100644
> --- a/arch/x86/kernel/mcount_64.S
> +++
On Fri, May 13, 2016 at 05:37:06PM +0200, Benjamin Tissoires wrote:
> This is a basic driver for the Surface 3. I am not so sure it will work
> with any firmwares as most values are encoded, but given that I only have
> access to my current device with its firmware and I don't have the
>
On Fri, May 13, 2016 at 05:37:06PM +0200, Benjamin Tissoires wrote:
> This is a basic driver for the Surface 3. I am not so sure it will work
> with any firmwares as most values are encoded, but given that I only have
> access to my current device with its firmware and I don't have the
>
On 5/16/2016 10:34 AM, Paul E. McKenney wrote:
On Mon, May 16, 2016 at 09:33:57AM -0700, Santosh Shilimkar wrote:
On 5/16/2016 5:03 AM, Paul E. McKenney wrote:
On Sun, May 15, 2016 at 09:35:40PM -0700, santosh.shilim...@oracle.com wrote:
On 5/15/16 2:18 PM, Santosh Shilimkar wrote:
Hi Paul,
On 5/16/2016 10:34 AM, Paul E. McKenney wrote:
On Mon, May 16, 2016 at 09:33:57AM -0700, Santosh Shilimkar wrote:
On 5/16/2016 5:03 AM, Paul E. McKenney wrote:
On Sun, May 15, 2016 at 09:35:40PM -0700, santosh.shilim...@oracle.com wrote:
On 5/15/16 2:18 PM, Santosh Shilimkar wrote:
Hi Paul,
Hello,
On 6 May 2016 at 02:31, Brian Norris wrote:
> Hi,
>
> I'm picking up Michal's patch set, since he dropped it on the floor, and it's
> useful for others. My additions:
>
> * rebased on latest
> * added fixes for drivers that have been merged in the meantime
>
Hello,
On 6 May 2016 at 02:31, Brian Norris wrote:
> Hi,
>
> I'm picking up Michal's patch set, since he dropped it on the floor, and it's
> useful for others. My additions:
>
> * rebased on latest
> * added fixes for drivers that have been merged in the meantime
> * addressed most of
On Mon, May 16, 2016 at 04:56:22PM +0530, Vignesh R wrote:
> On AM335x, ti_am335x_tsc can wake up the system from suspend, mark the
> IRQ as wakeup capable, so that device irq is not disabled during system
> suspend.
I would love for platform core to do this for us, like I2C core does.
>
>
On Mon, May 16, 2016 at 04:56:22PM +0530, Vignesh R wrote:
> On AM335x, ti_am335x_tsc can wake up the system from suspend, mark the
> IRQ as wakeup capable, so that device irq is not disabled during system
> suspend.
I would love for platform core to do this for us, like I2C core does.
>
>
On Mon, May 16, 2016 at 04:56:24PM +0530, Vignesh R wrote:
> From: Grygorii Strashko
>
> It is seen that just enabling the TSC module triggers a HW_PEN IRQ
> without any interaction with touchscreen by user. This results in first
> suspend/resume sequence to fail as
On Mon, May 16, 2016 at 04:56:24PM +0530, Vignesh R wrote:
> From: Grygorii Strashko
>
> It is seen that just enabling the TSC module triggers a HW_PEN IRQ
> without any interaction with touchscreen by user. This results in first
> suspend/resume sequence to fail as system immediately wakes up
Hey James,
I probably did something wrong - but i applied your patch onto 4.6,
compiled in shiftfs, did
mount -t shiftfs -o uidmap=0:10:65536,gidmap=0:10:65536 /home/ubuntu
/mnt
and ls segfaults and gives me kernel syslog msgs like:
[ 1089.744726] ===
[
Hey James,
I probably did something wrong - but i applied your patch onto 4.6,
compiled in shiftfs, did
mount -t shiftfs -o uidmap=0:10:65536,gidmap=0:10:65536 /home/ubuntu
/mnt
and ls segfaults and gives me kernel syslog msgs like:
[ 1089.744726] ===
[
Commit-ID: e8df1a95b685af84a81698199ee206e0e66a8b44
Gitweb: http://git.kernel.org/tip/e8df1a95b685af84a81698199ee206e0e66a8b44
Author: Dave Hansen
AuthorDate: Fri, 13 May 2016 15:13:28 -0700
Committer: Ingo Molnar
CommitDate: Mon, 16 May
Commit-ID: e8df1a95b685af84a81698199ee206e0e66a8b44
Gitweb: http://git.kernel.org/tip/e8df1a95b685af84a81698199ee206e0e66a8b44
Author: Dave Hansen
AuthorDate: Fri, 13 May 2016 15:13:28 -0700
Committer: Ingo Molnar
CommitDate: Mon, 16 May 2016 12:59:23 +0200
x86/cpufeature,
Hi Pantelis,
On Mon, May 16, 2016 at 9:27 PM, Pantelis Antoniou
wrote:
>> On May 16, 2016, at 22:06 , Geert Uytterhoeven wrote:
>> On Mon, May 16, 2016 at 6:52 PM, Pantelis Antoniou
>> wrote:
>>> Insert
Hi Pantelis,
On Mon, May 16, 2016 at 9:27 PM, Pantelis Antoniou
wrote:
>> On May 16, 2016, at 22:06 , Geert Uytterhoeven wrote:
>> On Mon, May 16, 2016 at 6:52 PM, Pantelis Antoniou
>> wrote:
>>> Insert overlay symbols to the base tree when applied.
>>> This makes it possible to apply an
On Wed, May 11, 2016 at 04:34:06PM +0300, Ville Syrjälä wrote:
> On Wed, May 11, 2016 at 08:44:45AM -0400, Steven Rostedt wrote:
> > On Wed, 11 May 2016 15:21:16 +0300
> > Ville Syrjälä wrote:
> >
> > > Yeah can't get anything from the machine at that point.
On Wed, May 11, 2016 at 04:34:06PM +0300, Ville Syrjälä wrote:
> On Wed, May 11, 2016 at 08:44:45AM -0400, Steven Rostedt wrote:
> > On Wed, 11 May 2016 15:21:16 +0300
> > Ville Syrjälä wrote:
> >
> > > Yeah can't get anything from the machine at that point. netconsole
> > > didn't help either,
On Mon, May 16, 2016 at 11:52 AM, Pantelis Antoniou
wrote:
> Add a benchmarking hashed phandles unittest which report what kind
> of speed up we get switching to hashed phandle lookups.
>
> ### dt-test ### the hash method is 8.2 times faster than the original
>
>
On Mon, May 16, 2016 at 11:52 AM, Pantelis Antoniou
wrote:
> Add a benchmarking hashed phandles unittest which report what kind
> of speed up we get switching to hashed phandle lookups.
>
> ### dt-test ### the hash method is 8.2 times faster than the original
>
> On the beaglebone we perform
On Mon, May 16, 2016 at 11:52 AM, Pantelis Antoniou
wrote:
> When a device tree contains a lot of phandles, resolving one
> takes time because the original method uses a search against
> all nodes (not just the ones with phandles).
>
> Signed-off-by: Pantelis
On Mon, May 16, 2016 at 11:52 AM, Pantelis Antoniou
wrote:
> When a device tree contains a lot of phandles, resolving one
> takes time because the original method uses a search against
> all nodes (not just the ones with phandles).
>
> Signed-off-by: Pantelis Antoniou
> ---
> drivers/of/base.c
With the upcoming removal of legacy boot, lets add support to one of the
last N900 drivers remaining without it. As the driver still uses omap
dmtimer, add auxdata as well.
Signed-off-by: Ivaylo Dimitrov
---
.../devicetree/bindings/media/nokia,n900-ir | 20
From: Tony Lindgren
The ir-rx51 driver for n900 has been disabled since the multiarch
changes as plat include directory no longer is SoC specific.
Let's fix it with minimal changes to pass the dmtimer calls in
pdata. Then the following changes can be done while things can
be
With the upcoming removal of legacy boot, lets add support to one of the
last N900 drivers remaining without it. As the driver still uses omap
dmtimer, add auxdata as well.
Signed-off-by: Ivaylo Dimitrov
---
.../devicetree/bindings/media/nokia,n900-ir | 20
From: Tony Lindgren
The ir-rx51 driver for n900 has been disabled since the multiarch
changes as plat include directory no longer is SoC specific.
Let's fix it with minimal changes to pass the dmtimer calls in
pdata. Then the following changes can be done while things can
be tested to be
ir-rx51 is a driver for Nokia N900 IR transmitter. The current series
fixes the remaining problems in the driver:
- replace GP timer 9 with PWM framework usage
- replace pulse width timer dmtimer usage with hrtimer
- add DT support to the driver
- add driver to the board DTS
Pathe 2 is
Hi,
[auto build test ERROR on next-20160506]
[cannot apply to v4.6-rc7 v4.6-rc6 v4.6-rc5 v4.6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Convert driver to use PWM framework instead of calling dmtimer functions
directly for PWM timer. Remove paragraph about writing to the Free Software
Foundation's mailing address while at it.
Signed-off-by: Ivaylo Dimitrov
---
Add the needed DT data to enable IR TX driver
Signed-off-by: Ivaylo Dimitrov
---
arch/arm/boot/dts/omap3-n900.dts | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/boot/dts/omap3-n900.dts
index
ir-rx51 is a driver for Nokia N900 IR transmitter. The current series
fixes the remaining problems in the driver:
- replace GP timer 9 with PWM framework usage
- replace pulse width timer dmtimer usage with hrtimer
- add DT support to the driver
- add driver to the board DTS
Pathe 2 is
Hi,
[auto build test ERROR on next-20160506]
[cannot apply to v4.6-rc7 v4.6-rc6 v4.6-rc5 v4.6]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Convert driver to use PWM framework instead of calling dmtimer functions
directly for PWM timer. Remove paragraph about writing to the Free Software
Foundation's mailing address while at it.
Signed-off-by: Ivaylo Dimitrov
---
arch/arm/mach-omap2/board-rx51-peripherals.c | 1 -
Add the needed DT data to enable IR TX driver
Signed-off-by: Ivaylo Dimitrov
---
arch/arm/boot/dts/omap3-n900.dts | 12
1 file changed, 12 insertions(+)
diff --git a/arch/arm/boot/dts/omap3-n900.dts b/arch/arm/boot/dts/omap3-n900.dts
index b3c26a9..cb3878a 100644
---
Drop dmtimer usage for pulse timer in favor of hrtimer. That allows
removing PWM dmitimer platform data usage.
Signed-off-by: Ivaylo Dimitrov
---
arch/arm/mach-omap2/board-rx51-peripherals.c | 4 -
arch/arm/mach-omap2/pdata-quirks.c | 3 -
OMAP GP timers can have different input clocks that allow different PWM
frequencies. However, there is no other way of setting the clock source but
through clocks or clock-names properties of the timer itself. This limits
PWM functionality to only the frequencies allowed by the particular clock
701 - 800 of 1620 matches
Mail list logo