On 08/11/2014 10:27 PM, Amit Shah wrote:
On (Mon) 11 Aug 2014 [15:11:03], H. Peter Anvin wrote:
On 08/11/2014 11:49 AM, Amit Shah wrote:
The khwrngd thread is started when a hwrng device of sufficient
quality is registered. The virtio-rng device is backed by the
hypervisor, and we trust the
Commit-ID: aaecac4ad46b35ad308245384d019633fb9bc21b
Gitweb: http://git.kernel.org/tip/aaecac4ad46b35ad308245384d019633fb9bc21b
Author: Zhihui Zhang zzhs...@gmail.com
AuthorDate: Fri, 1 Aug 2014 21:18:03 -0400
Committer: Ingo Molnar mi...@kernel.org
CommitDate: Tue, 12 Aug 2014 12:48:21
On Tue, Aug 12, 2014 at 05:28:52AM -0700, Eric Dumazet wrote:
On Tue, 2014-08-12 at 09:07 +0300, Kirill A. Shutemov wrote:
On Tue, Aug 12, 2014 at 08:00:54AM +0300, Oren Twaig wrote:
If not, is there any fast way to change this behavior ? Maybe by
changing the granularity/alignment of such
On Tue, Aug 12, 2014 at 4:02 AM, Matthias Brugger
matthias@gmail.com wrote:
2014-08-11 9:15 GMT+02:00 Linus Walleij linus.wall...@linaro.org:
On Thu, Jul 31, 2014 at 6:42 PM, Matthias Brugger
matthias@gmail.com wrote:
We enable GTP6 which ungates the arch timer clock. Apart we write
When doing a system-wide trace with Intel PT, the jump label
set up as a result of probing CLOEXEC gets reset while the
trace is running. That causes an Intel PT decoding error
because the object code (obtained from /proc/kcore) does
not match the running code at that point. While we can't
Fall back to probing with the current pid if cpu-wide
probing fails. This primarily affects the setting of
comm_exec flag when the user is un-privileged and
/proc/sys/kernel/perf_event_paranoid 0. The change
to comm_exec can be observed by using -vv with
perf record and a kernel that supports
Hi
Here are some fixes for API probing issues that I have run into,
and a second attempt at the jump-label problem.
Patches apply to your tmp.perf/core branch.
Adrian Hunter (4):
perf tools: Fix CLOEXEC probe for perf_event_paranoid == 2
perf tools: Fix one of the probe events to
When probing the kernel API the kernel should be excluded
otherwise the probe will fail for users with insufficient
privilege to profile the kernel.
Signed-off-by: Adrian Hunter adrian.hun...@intel.com
---
tools/perf/util/record.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
With /proc/sys/kernel/perf_event_paranoid set to 2, the
probe of PERF_FLAG_FD_CLOEXEC would fail. Fix by excluding
kernel profiling from the probe event.
Signed-off-by: Adrian Hunter adrian.hun...@intel.com
---
tools/perf/util/cloexec.c | 1 +
1 file changed, 1 insertion(+)
diff --git
The khwrngd thread is started when a hwrng device of sufficient
quality is registered. The virtio-rng device is backed by the
hypervisor, and we trust the hypervisor to provide real entropy.
A malicious hypervisor is a scenario that's irrelevant -- such a setup
is bound to cause all sorts of
On Tue, Aug 12, 2014 at 04:49:35PM +0200, Richard Weinberger wrote:
Am 12.08.2014 16:46, schrieb Vivek Goyal:
Richard and Daniel reported that UML is broken due to changes to resource
traversal functions. Problem is that iomem_resource.child can be null
and new code does not consider that
Fix building of exynos_defconfig with disabled CONFIG_PM_SLEEP by
adding checking whether Exynos cpuidle support is enabled before
accessing exynos_enter_aftr.
The build error message:
arch/arm/mach-exynos/built-in.o:(.data+0x74): undefined reference to
`exynos_enter_aftr'
make: *** [vmlinux]
Hi,
This patch series fixes builds with CONFIG_PM_SLEEP config option
disabled. It has been runtime tested on Exynos4210 based Origen
board.
Depends on:
- next-20140811 branch of linux-next kernel
Changes since v1:
(http://www.mail-archive.com/linux-samsung-soc@vger.kernel.org/msg34079.html)
-
Hello Linus,
could you please pull from
git://git.kernel.org/pub/scm/linux/kernel/git/jack/linux-fs.git for_linus
to get scalability improvements for quota, a few reiserfs fixes, and couple
of misc cleanups (udf, ext2).
Top of the tree is 01777836c870. The full shortlog is:
Andy
(2014/08/12 22:03), Wang Nan wrote:
Hi Masami and everyone,
When checking my code I found a problem: if we replace a stack operatinon
instruction,
it is possible that the emulate execution of such instruction destroy the
stack used
by kprobeopt:
+
+asm (
+.global
Fix building of exynos_defconfig with CONFIG_PM_SLEEP disabled and
CONFIG_ARM_EXYNOS_CPUIDLE enabled by:
* adding EXYNOS_CPU_SUSPEND config option
* building pm.o and sleep.o if EXYNOS_CPU_SUSPEND is enabled
* moving suspend specific code from pm.c to suspend.c
* enabling pm-common.o build also
Ifdef around cpu_\name\()_do_suspend and cpu_\name\()_do_resume
ops in proc-macros.S should check for CONFIG_ARM_CPU_SUSPEND and
not CONFIG_PM_SLEEP. Fix it.
[ Please note that cpu_v7_do_[suspend,resume] code in proc-v7.S
already correctly checks for CONFIG_ARM_CPU_SUSPEND, same is
true for
Hi,
On Mon, Aug 11, 2014 at 5:46 AM, Ulf Hansson ulf.hans...@linaro.org wrote:
On 11 August 2014 09:44, Linus Walleij linus.wall...@linaro.org wrote:
On Mon, Aug 4, 2014 at 12:18 AM, Heiko Stübner he...@sntech.de wrote:
[Adding Ulf Hansson to this discussion...]
Hi Mark, Linus,
I'd like
On Mon, Aug 11, 2014 at 01:19:12PM +0100, Mark Brown wrote:
On Mon, Aug 11, 2014 at 11:54:29AM +0530, Vinod Koul wrote:
On Thu, Aug 07, 2014 at 06:13:24PM +0100, Mark Brown wrote:
On Thu, Aug 07, 2014 at 07:46:05PM +0530, Vinod Koul wrote:
I was thinking about this as well a while
On Tue, Aug 12, 2014 at 07:15:41AM -0700, Alexandre Courbot wrote:
On Tue, Aug 12, 2014 at 3:01 AM, Mika Westerberg
mika.westerb...@linux.intel.com wrote:
On Fri, Aug 08, 2014 at 02:36:02PM +0200, Linus Walleij wrote:
On Thu, Jul 24, 2014 at 5:51 PM, Tomasz Nowicki
Em Tue, Aug 12, 2014 at 04:58:19PM +0200, Ingo Molnar escreveu:
* Arnaldo Carvalho de Melo a...@kernel.org wrote:
Em Tue, Aug 05, 2014 at 08:08:56AM +0200, Ingo Molnar escreveu:
This patch looks dangerous and misleading to me.
I took it more from the angle: hey, it fixes a regression,
On 08/10/2014 09:19 PM, Benjamin Herrenschmidt wrote:
On Wed, 2014-07-30 at 00:31 -0700, tip-bot for John Stultz wrote:
Commit-ID: 953dec21aed4038464fec02f96a2f1b8701a5bce
Gitweb:
http://git.kernel.org/tip/953dec21aed4038464fec02f96a2f1b8701a5bce
Author: John Stultz
Hi Suman,
On Thu, Jul 3, 2014 at 11:53 PM, Suman Anna s-a...@ti.com wrote:
The buffers to be used for communication are allocated during
the rpmsg virtio driver's probe, and the number of buffers is
currently hard-coded to 512. Remove this hard-coded value, as
this can vary from one platform
Btw, I might be missing something here, but wouldn't it be better
to reference count the file_lock structure and grab a reference to
it where we currently call (__)locks_copy_lock?
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to
Michal Hocko mho...@suse.cz writes:
spin_lock may be an empty struct for !SMP configurations and so
arch_spin_is_locked may return unconditional 0 and trigger the VM_BUG_ON
even when the lock is held.
Replace spin_is_locked by lockdep_assert_held. We will not BUG anymore
but it is
Section 4 intro was still describing the old interface. Rewrite it.
Signed-off-by: Juri Lelli juri.le...@arm.com
Signed-off-by: Luca Abeni luca.ab...@unitn.it
Cc: Randy Dunlap rdun...@infradead.org
Cc: Peter Zijlstra pet...@infradead.org
Cc: Ingo Molnar mi...@redhat.com
Cc: Henrik Austad
From: Luca Abeni luca.ab...@unitn.it
Several small changes regarding SCHED_DEADLINE documentation that fix
terminology and improve clarity and readability:
- current runtime becomes remaining runtime
- readablity of an equation is improved by introducing more spacing
- clarify when
Hello everyone,
This small patchset fixes and improves SCHED_DEADLINE documentation.
Patch 1/4 fixes and clarifies terminology; patch 2/4 aligns Section 4 to
the current interface; patch 3/4 improves and clarifies what admission
control means on UP an SMP systems; patch 4/4 introduces an
From: Luca Abeni luca.ab...@unitn.it
Admission control is of key importance for SCHED_DEADLINE, since it guarantees
system schedulability (or tells us something about the degree of guarantees
we can provide to the user).
This patch improves and clarifies bits and pieces regarding AC, both for UP
Add an appendix briefly describing tools that can be used to test SCHED_DEADLINE
(and the scheduler in general). Links to where source code of the tools is
hosted
are also provided.
Signed-off-by: Juri Lelli juri.le...@arm.com
Cc: Randy Dunlap rdun...@infradead.org
Cc: Peter Zijlstra
Benjamin Herrenschmidt pointed out that I firuther missed
modifying update_vsyscall after the wall_to_mono value was
changed to a timespec64. This causes issues on powerpc32,
which expects a 32bit timespec.
This patch fixes the problem my properly converting from
a timespec64 to a timespec before
On Tue, Aug 12, 2014 at 02:34:58PM +0100, Charles Keepax wrote:
On Fri, Aug 08, 2014 at 02:35:10PM +0100, Richard Fitzgerald wrote:
From: Richard Fitzgerald r...@opensource.wolfsonmicro.com
Some codecs need to boost DVFS for higher sample rates.
Signed-off-by: Richard Fitzgerald
Added DT maintainers as we have here quite fundamental DT question:
How shall we model hardware connected to multiple buses, in DT?
Here we have panel connected to two MIPI-DSI buses.
Below is the summary of our propositions, followed by lengthly detailed
discussion,
including proposed
On Tue, Aug 12, 2014 at 11:03:21AM +0530, Amit Shah wrote:
On (Mon) 11 Aug 2014 [20:45:31], Paul E. McKenney wrote:
[ . . . ]
That is a bit surprising. Is it possible that the system is OOMing
quickly due to grace periods not proceeding? If so, maybe giving the
VM more memory would
On Tue, Aug 12, 2014 at 10:57:26AM +0530, Amit Shah wrote:
On (Mon) 11 Aug 2014 [13:34:21], Paul E. McKenney wrote:
On Tue, Aug 12, 2014 at 01:48:45AM +0530, Amit Shah wrote:
[ . . . ]
In addition sendkey alt-sysrq-t at the (qemu) prompt dumps all
tasks'
stacks, which would also
As I said earlier in this thread, echo'ing devices into pm_test
does not result in a crash; but doing so for platform does.
Markus
On Aug 12, 2014 1:26 AM, Zhang Rui rui.zh...@intel.com wrote:
On Sat, 2014-08-09 at 03:14 -0700, Markus Gutschke wrote:
I am back and have physical access to the
On Aug 11, 2014, at 9:42 PM, Stepan Moskovchenko step...@codeaurora.org wrote:
When we parse the device tree and allocate platform
devices, the 'name' of the newly-created platform_device
is set to point to the 'name' field of the 'struct device'
embedded within the platform_device. This is
This patch removes the superflous .owner field for drivers which
use the module_platform_driver API, as this is overriden in
platform_driver_register anyway.
Signed-off-by: Peter Griffin peter.grif...@linaro.org
---
drivers/mmc/host/jz4740_mmc.c | 1 -
drivers/mmc/host/moxart-mmc.c | 1
As the code is using SIMPLE_DEV_PM_OPS helper, this compiles away to
nothing if CONFIG_PM_SLEEP is disabled. Thus we don't need to #define
the suspend/resume callbacks to NULL.
Signed-off-by: Peter Griffin peter.grif...@linaro.org
---
drivers/mmc/host/dw_mmc-pltfm.c | 3 ---
1 file changed, 3
This allows us to get rid of the #else condition, as the macro compiles
away to nothing if not enabled.
Signed-off-by: Peter Griffin peter.grif...@linaro.org
---
drivers/mmc/host/sdhci-acpi.c | 11 ++-
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git
As the code is using SIMPLE_DEV_PM_OPS helper, this compiles away to
nothing if CONFIG_PM_SLEEP is disabled. Thus we don't need to #define
the suspend/resume callbacks to NULL.
Signed-off-by: Peter Griffin peter.grif...@linaro.org
---
drivers/mmc/host/dw_mmc-pci.c | 3 ---
1 file changed, 3
This allows us to get rid of the #else condition, as the macro compiles
away to nothing if not enabled.
Signed-off-by: Peter Griffin peter.grif...@linaro.org
---
drivers/mmc/host/sdhci-pci.c | 11 ++-
1 file changed, 2 insertions(+), 9 deletions(-)
diff --git
This series cleans up a few platform drivers in how they are declaring there
dev_pm_ops structs, and gets rid of a few now redundant #else conditions.
Also it removes the .owner field of drivers which use module_platform_driver
api to register themselves, as this field gets overwritten.
Peter
Hi Greg,
These patches fix checkpatch warning.
Apply for staging-next branch.
Regards,
Phong.
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please
This patch fix coding style
- Replace kzalloc() by kcalloc()
- Remove return of void function
Tested by compilation
Signed-off-by: Phong Tran tranmanph...@gmail.com
---
drivers/staging/android/ion/ion_dummy_driver.c | 4 +---
1 file changed, 1 insertion(+), 3 deletions(-)
diff --git
This patch fix coding rule
- Remove return of void function
Tested by compilation
Signed-off-by: Phong Tran tranmanph...@gmail.com
---
drivers/staging/android/ion/ion_system_heap.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/android/ion/ion_system_heap.c
This patch fix coding style
- Remove return of void function
Tested by compilation
Signed-off-by: Phong Tran tranmanph...@gmail.com
---
drivers/staging/android/ion/ion_carveout_heap.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/android/ion/ion_carveout_heap.c
Hi Ohad,
On 08/12/2014 10:30 AM, Ohad Ben-Cohen wrote:
Hi Suman,
On Thu, Jul 3, 2014 at 11:53 PM, Suman Anna s-a...@ti.com wrote:
The buffers to be used for communication are allocated during
the rpmsg virtio driver's probe, and the number of buffers is
currently hard-coded to 512. Remove
This patch fix the coding style
- Add a new line after variable declaration
- Remove return of void fuction
Tested by compilation
Signed-off-by: Phong Tran tranmanph...@gmail.com
---
drivers/staging/android/ion/ion.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This patch fix coding style
- Remove return of void function
Tested by compilation
Signed-off-by: Phong Tran tranmanph...@gmail.com
---
drivers/staging/android/ion/ion_chunk_heap.c | 1 -
1 file changed, 1 deletion(-)
diff --git a/drivers/staging/android/ion/ion_chunk_heap.c
On 21 July 2014 06:37, Apelete Seketeli apel...@seketeli.net wrote:
Until now the MMC driver for JZ4740 SoC was relying on PIO mode only
for data transfers.
This patch allows the use of DMA for data trasnfers in addition to PIO
mode by relying on DMA Engine.
DMA tranfers performance might be
Hi Kirill,
I saw the thread has developed nicely :), still - wanted to answer your
question
below.
On 8/12/2014 9:07 AM, Kirill A. Shutemov wrote:
On Tue, Aug 12, 2014 at 08:00:54AM +0300, Oren Twaig wrote:
html style=direction: ltr;
plain/text, please.
Yes - noticed the html, sent again
On Tue, 12 Aug 2014 08:32:29 -0700
Christoph Hellwig h...@infradead.org wrote:
Btw, I might be missing something here, but wouldn't it be better
to reference count the file_lock structure and grab a reference to
it where we currently call (__)locks_copy_lock?
It's not really possible with
On 21 July 2014 06:37, Apelete Seketeli apel...@seketeli.net wrote:
Make use of the MMC asynchronous request capability to prepare the
next DMA transfer request in parallel with the current transfer.
This is done by adding pre-request and post-request callbacks that are
used by the MMC
The last user of the deprecated struct ahci_platform_data has been
cleaned up recently (SPEAr1340 got a proper PHY driver).
Cc: Hans de Goede hdego...@redhat.com
Signed-off-by: Bartlomiej Zolnierkiewicz b.zolnier...@samsung.com
---
drivers/ata/ahci_platform.c| 18 +-
On Mon, Aug 11, 2014 at 1:07 PM, Geert Uytterhoeven
ge...@linux-m68k.org wrote:
Hi Kees,
v3.17 is gonna get a lot of new syscalls...
4 so far! :P
On Wed, Aug 6, 2014 at 6:27 PM, Linux Kernel Mailing List
linux-kernel@vger.kernel.org wrote:
Gitweb:
Hi Hugh,
Typically, on our setup we observed, 10% less power consumption with some
use-cases in which CPU goes to power collapse frequently. For example,
playing audio while typically CPU remains idle.
I'm probably stupid, but I don't quite get your scenario from that
description: please
Before commit 7b5436635800 the pci_host_bridge was created before the root bus.
As that commit has added a needless dependency on the bus for
pci_alloc_host_bridge()
the creation order has been changed for no good reason. Revert the order of
creation as we are going to depend on the
The inline version of ioport_map() that gets used when !CONFIG_GENERIC_IOMAP
is wrong. It returns a mapped (i.e. virtual) address that can start from
zero and completely ignores the PCI_IOBASE and IO_SPACE_LIMIT that most
architectures that use !CONFIG_GENERIC_MAP define.
Signed-off-by: Liviu
The ranges property for a host bridge controller in DT describes
the mapping between the PCI bus address and the CPU physical address.
The resources framework however expects that the IO resources start
at a pseudo port address 0 (zero) and have a maximum size of IO_SPACE_LIMIT.
The conversion
The handling of PCI domains (or PCI segments in ACPI speak) is
usually a straightforward affair but its implementation is
currently left to the architectural code, with pci_domain_nr(b)
querying the value of the domain associated with bus b.
This patch introduces CONFIG_PCI_DOMAINS_GENERIC as an
This is needed for calls into OF code that parses PCI ranges.
It signals support for memory mapped PCI I/O accesses that
are described be device trees.
Cc: Russell King li...@arm.linux.org.uk
Cc: Catalin Marinas catalin.mari...@arm.com
Cc: Arnd Bergmann a...@arndb.de
Cc: Rob Herring
From: Shawn Bohrer sboh...@rgmadvisors.com
In debugging an application that receives -ENOMEM from ib_reg_mr() I
found that ib_umem_get() can fail because the pinned_vm count has
wrapped causing it to always be larger than the lock limit even with
RLIMIT_MEMLOCK set to RLIM_INFINITY.
The wrapping
Introduce a default implementation for remapping PCI bus I/O resources
onto the CPU address space. Architectures with special needs may
provide their own version, but most should be able to use this one.
Cc: Bjorn Helgaas bhelg...@google.com
Cc: Arnd Bergmann a...@arndb.de
Cc: Rob Herring
Enhance the default implementation of pcibios_add_device() to
parse and map the IRQ of the device if a DT binding is available.
Cc: Bjorn Helgaas bhelg...@google.com
Cc: Grant Likely grant.lik...@linaro.org
Cc: Rob Herring robh...@kernel.org
Signed-off-by: Liviu Dudau liviu.du...@arm.com
---
Provide a function to parse the PCI DT ranges and use it to
create a pci_host_bridge structure together with its associated
bus. Scan all the child busses and add the devices found.
This is the OF equivalent of pci_scan_root_bus() where all the
resources needed for creating the root bus are
This is my updated attempt at adding support for generic PCI host
bridge controllers that make use of device tree information to
configure themselves. This version incorporates Catalin's proposal
for managing domain numbers that got Bjorn's approval. I am now requesting
ACKs from the relevant
Previously, of_pci_range_to_resource() would return a resource
that contained physical addresses of the IO space even if the
IORESOURCE_IO flags mandate a logical port set of values. Now
that the function has been fixed we need to update the drivers
that were taking advantage of the old behaviour.
Add of_pci_get_domain_nr() to retrieve the PCI domain number
of a given device from DT. If the information is not present,
the function can be requested to allocate a new domain number.
Cc: Bjorn Helgaas bhelg...@google.com
Cc: Arnd Bergmann a...@arndb.de
Cc: Grant Likely grant.lik...@linaro.org
Some architectures do not have a simple view of the PCI I/O space
and instead use a range of CPU addresses that map to bus addresses.
For some architectures these ranges will be expressed by OF bindings
in a device tree file.
This patch introduces a pci_register_io_range() helper function with
a
Add pgprot_device(). It will be aliased to pgprot_noncached for
architectures that do not support special attributes for device
mapping. Used by arm64 to define new attributes for devices.
Cc: Arnd Bergmann a...@arndb.de
Cc: Catalin Marinas catalin.mari...@arm.com
Signed-off-by: Liviu Dudau
I think patch subject lines with checkpatch in
them are almost never really useful.
Maybe a new checkpatch test to see if a subject line
is perhaps less than informational should be added.
Something like:
---
scripts/checkpatch.pl | 7 +++
1 file changed, 7 insertions(+)
diff --git
On 11/08/14 19:03, Dmitry Torokhov wrote:
This should fix the following issues reported by Coverity:
*** CID 1230625: Logically dead code (DEADCODE)
/drivers/input/touchscreen/atmel_mxt_ts.c: 1692 in mxt_initialize()
*** CID 1230627: Missing break in switch (MISSING_BREAK)
On 08/12/2014 10:38 AM, Nick Dyer wrote:
On 11/08/14 19:03, Dmitry Torokhov wrote:
This should fix the following issues reported by Coverity:
*** CID 1230625: Logically dead code (DEADCODE)
/drivers/input/touchscreen/atmel_mxt_ts.c: 1692 in mxt_initialize()
*** CID 1230627: Missing break
On 07/31/14 11:20, Rahul Bedarkar wrote:
Signed-off-by: Rahul Bedarkar rahulbedarka...@gmail.com
Acked-by: Randy Dunlap rdun...@infradead.org
Jiri, please add to trivial. Thanks.
---
Documentation/kmemleak.txt | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
Use the generic PCI domain and host bridge functions
to provide support for PCI Express on arm64.
Signed-off-by: Liviu Dudau liviu.du...@arm.com
[Generic PCI domain support]
Signed-off-by: Catalin Marinas catalin.mari...@arm.com
---
arch/arm64/Kconfig| 22 +++-
Peach Pit and Pi machines have the same regulators connection
and regulator name so the cros-tps65090 dtsi file can be used
to remove duplicated code.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/boot/dts/exynos5420-peach-pit.dts | 95
The DeviceTree files for the Peach Pit and Pi machines have
a simplistic model of the connections between the different
regulators since not all the tps65090 regulators get their
input supply voltage from the VDC. DCDC1-3, LD0-1 and fet7
parent supply is indded VDC but the fet1-6 get their input
The tps65090 PMU data manual [0] has a table that list the
Recommended operating conditions for each regulator. Add
the information about the FET constraints to its dtsi file.
[0]: http://www.ti.com/lit/ds/symlink/tps65090.pdf
Signed-off-by: Javier Martinez Canillas
The tps65090 PMU is a component used in many ChromeOS devices
so instead of having the same device tree definitions in many
files, create a .dtsi fragment that can be included in DTS.
This fragment is based on the DT definitions for Peach boards.
Signed-off-by: Javier Martinez Canillas
Now that there is a .dtsi fragment file for the tps65090 PMU,
include it in the Exynos Snow DTS file to reduce duplication.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/boot/dts/exynos5250-snow.dts | 108 +-
1 file changed,
The tps65090 is a Power Management Unit (PMU) used in several
boards so the same information is described on different DTS.
It is better to create a .dtsi fragment that can be included.
Signed-off-by: Javier Martinez Canillas javier.marti...@collabora.co.uk
---
arch/arm/boot/dts/tps65090.dtsi |
This series does a refactoring by creating dtsi files for the
tps65090 PMU that can be included by DT board files that have
this component. This not only allow to remove duplicated code
but also makes it easier to maintain the tps65090 information.
So the series also improve the tps65090
Somehow, my cover letter went AWOL. Here it is:
Hi,
This patch adds support for PCI to AArch64. It is based on my v9 patch
that adds support for creating generic host bridge structure from
device tree. With that in place, I was able to boot a platform that
has PCIe host bridge support and use a
From: Lorenzo Pieralisi lorenzo.pieral...@arm.com
In order to consolidate DT configuration for PCI host controllers in the
kernel, a new API was introduced that allows creating a host bridge
and its PCI bus from DT, removing duplicated code present in the
majority of pci host driver
On Tue, Aug 12, 2014 at 06:44:23PM +0200, Javier Martinez Canillas wrote:
The tps65090 is a Power Management Unit (PMU) used in several
boards so the same information is described on different DTS.
It is better to create a .dtsi fragment that can be included.
Why is it better to do this?
+
On Mon, Aug 11, 2014 at 10:42:38AM -0400, Benjamin Tissoires wrote:
On Aug 09 2014 or thereabouts, Jiri Kosina wrote:
On Sat, 9 Aug 2014, Geert Uytterhoeven wrote:
If CONFIG_PM is not set:
drivers/hid/wacom_sys.c:1436: warning: ‘wacom_reset_resume’ defined but
not used
On 08/08/14 08:23, Geert Uytterhoeven wrote:
- singular versus plural,
- by versus of,
- missing if, it, the,
- consistent use of xxx-specific versus xxx specific.
Signed-off-by: Geert Uytterhoeven ge...@linux-m68k.org
---
Documentation/kbuild/makefiles.txt | 58
Updated changelog regarding the removed comment about the implied barrier
provided by wake_up() logic.
--
Pranith
The rcu_gp_kthread_wake() function checks for three conditions before waking up
grace period kthreads:
* Is the thread we are trying to wake up the current thread?
* Are the
docproc: .//drivers/gpu/drm/drm_stub.c: No such file or directory
make[1]: *** [Documentation/DocBook/drm.xml] Error 1
make: *** [mandocs] Error 2
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at
On 08/12/14 10:12, Jim Davis wrote:
docproc: .//drivers/gpu/drm/drm_stub.c: No such file or directory
make[1]: *** [Documentation/DocBook/drm.xml] Error 1
make: *** [mandocs] Error 2
--
Known and patch has been submitted. I'll try to get it merged.
--
~Randy
--
To unsubscribe from this
From: Alexander Usyskin alexander.usys...@intel.com
We cannot handle user interrupt in context of hw initialization
so we only wait for time out which is reasonably short
Also we don't need to check error from wait, only flag value.
Signed-off-by: Alexander Usyskin alexander.usys...@intel.com
Remove duplicate definition of arch_gnttab_init.
Signed-off-by: Andreas Schwab sch...@linux-m68k.org
---
arch/arm/xen/grant-table.c | 5 -
1 file changed, 5 deletions(-)
diff --git a/arch/arm/xen/grant-table.c b/arch/arm/xen/grant-table.c
index 2c4041c..e437918 100644
---
Hello Mark,
On 08/12/2014 06:58 PM, Mark Brown wrote:
On Tue, Aug 12, 2014 at 06:44:23PM +0200, Javier Martinez Canillas wrote:
The tps65090 is a Power Management Unit (PMU) used in several
boards so the same information is described on different DTS.
It is better to create a .dtsi fragment
Javier,
On Tue, Aug 12, 2014 at 9:44 AM, Javier Martinez Canillas
javier.marti...@collabora.co.uk wrote:
The tps65090 PMU is a component used in many ChromeOS devices
so instead of having the same device tree definitions in many
files, create a .dtsi fragment that can be included in DTS.
On Tue, Aug 12, 2014 at 06:44:28PM +0200, Javier Martinez Canillas wrote:
The tps65090 PMU data manual [0] has a table that list the
Recommended operating conditions for each regulator. Add
the information about the FET constraints to its dtsi file.
tps65090_fet1: fet1 {
+
Hi,
This patch adds support for PCI to AArch64. It is based on my v9 patch
that adds support for creating generic host bridge structure from
device tree. With that in place, I was able to boot a platform that
has PCIe host bridge support and use a PCIe network card.
Changes from v8:
- Added
On Fri, Aug 8, 2014 at 7:35 AM, Stefan Bader stefan.ba...@canonical.com wrote:
On 08.08.2014 14:43, David Vrabel wrote:
On 08/08/14 12:20, Stefan Bader wrote:
Unfortunately I have not yet figured out why this happens, but can confirm
by
compiling with or without CONFIG_RANDOMIZE_BASE being
On 08/07/2014 01:16 AM, Dmitry Torokhov wrote:
On Wed, Aug 06, 2014 at 07:47:25PM +, Murphy, Dan wrote:
Bump
On 07/31/2014 02:14 PM, Murphy, Dan wrote:
Add the TI drv260x haptics/vibrator driver.
This device uses the input force feedback
to produce a wave form to driver an
ERM or LRA
This patch fixed 'make xmldocs' failed on linus's tree and
linux-next as of 8th/Aug,2014.
When drm merge for 3.17-rc1 happen, a file was renamed from
drm_stub.c to drm_drv.c.
But Documentation/DocBook/drm.tmpl still have an old file name.
Signed-off-by: Masanari Iida standby2...@gmail.com
901 - 1000 of 1270 matches
Mail list logo
