Hi,
Am 26.03.2015 um 06:56 schrieb Pavel Machek :
> Hi!
>
> Main reason is, that I would need to go
> through the UART to “communicate" with the w2sg0004.
You can always "communicate” through the UART. Even without DT. As long as
the connected chip is powered up by any me
> > diff --git a/drivers/phy/phy-twl4030-usb.c
b/drivers/phy/phy-twl4030-usb.c
> > index 8e87f54671f3..1a244f34b748 100644
> > --- a/drivers/phy/phy-twl4030-usb.c
> > +++ b/drivers/phy/phy-twl4030-usb.c
> > @@ -144,6 +144,16 @@
> > #define PMBR1 0x0D
> > #define G
Hi all,
Today's linux-next merge of the xen-tip tree got a conflict in
drivers/xen/Kconfig between commit 94ccae47e02d ("XEN / ACPI: Make XEN
ACPI depend on X86") from the arm64-acpi tree and commit 628c28eefd6f
("xen: unify foreign GFN map/unmap for auto-xlated physmap guests")
from the xen-tip t
On Thu, 2015-03-26 at 06:23 +0100, Mike Galbraith wrote:
> I plan on taking a poke at getting "don't raise timer unconditionally"
> working again when I get myself unburied, and see if I can come up with
> a somewhat less icky way to work around take rtmutex in irq naughtiness.
Hm.. like maybe on
On Wed, Mar 25, 2015 at 12:09:03PM +0800, w...@redhat.com wrote:
> From: Fu Wei
>
> This is a Chinese translated version of
> Documentation/arm64/legacy_instructions.txt
>
> It is based on the modifications of
> Documentation/arm64/legacy_instructions.txt in submission:
> "587064b6", "bd35a4ad
On 2015/3/26 13:19, Daniel Axtens wrote:
> Hi Yijing,
>
> Pulled.
>
> I'm now getting build errors:
>
> /scratch/dja/linux-patches/arch/powerpc/kernel/pci-common.c: In function
> 'pcibios_scan_phb':
> /scratch/dja/linux-patches/arch/powerpc/kernel/pci-common.c:1638:14: error:
> 'bus' undeclare
The perf kmem command records and analyze kernel memory allocation
only for SLAB objects. This patch implement a simple page allocator
analyzer using kmem:mm_page_alloc and kmem:mm_page_free events.
It adds two new options of --slab and --page. The --slab option is
for analyzing SLAB allocator a
It perf kmem support caller statistics for page. Unlike slab case,
the tracepoints in page allocator don't provide callsite info. So
it records with callchain and extracts callsite info.
Note that the callchain contains several memory allocation functions
which has no meaning for users. So skip
The struct page is opaque for userspace tools, so it'd be better to save
pfn in order to identify page frames.
The textual output of $debugfs/tracing/trace file remains unchanged and
only raw (binary) data format is changed - but thanks to libtraceevent,
userspace tools which deal with the raw dat
Hi Ivan,
On 03/25/2015 06:40 PM, Ivan T. Ivanov wrote:
Hi Sricharan,
On Fri, 2015-03-13 at 23:19 +0530, Sricharan R wrote:
#define QUP_I2C_MASTER_GEN 0x408
+#define QUP_I2C_MASTER_CONFIG 0x408
Unused.
Ok, will remove it
#define QUP_READ_LIMIT 256
+#define MX_T
Currently perf kmem shows total (page) allocation stat by default, but
sometimes one might want to see live (total alloc-only) requests/pages
only. The new --live option does this by subtracting freed allocation
from the stat.
Signed-off-by: Namhyung Kim
---
tools/perf/Documentation/perf-kmem.t
Add new sort keys for page: page, order, mtype, gfp - existing
'bytes', 'hit' and 'callsite' sort keys also work for page. Note that
-s/--sort option should be preceded by either of --slab or --page
option to determine where the sort keys applies.
Now it properly groups and sorts allocation stats
Save libtraceevent output and print it in the header.
# perf kmem stat --page --caller
# GFP flags
# -
# 0010: GFP_NOIO
# 00d0: GFP_KERNEL
# 0200: GFP_NOWARN
# 84d0: GFP_KERNEL|GFP_REPEAT|GFP_ZERO
# 000200d2: GFP_HIGHUSER
# 000200da: GFP_HIGHUSER_MOVABLE
Hello,
Currently perf kmem command only analyzes SLAB memory allocation. And
I'd like to introduce page allocation analysis also. Users can use
--slab and/or --page option to select it. If none of these options
are used, it does slab allocation analysis for backward compatibility.
* changes
Hi Kame-san,
On 03/26/2015 11:12 AM, Kamezawa Hiroyuki wrote:
> On 2015/03/26 11:17, Gu Zheng wrote:
>> Yasuaki Ishimatsu found that with node online/offline, cpu<->node
>> relationship is established. Because workqueue uses a info which was
>> established at boot time, but it may be changed by n
On Thu, 2015-03-26 at 06:23 +0100, Mike Galbraith wrote:
> On Wed, 2015-03-25 at 20:17 -0600, Thavatchai Makphaibulchoke wrote:
> >
> > On 03/22/2015 10:42 PM, Mike Galbraith wrote:
> > >> Why can't we just Let swapper be the owner when in irq with no dummy?
> > >>
> >
> > Thanks Mike for the sug
Hi Stefan,
I have tested recently, this driver also works on Vybrid twr board. I
send V3 patches just now, Please help test it on Vybrid board if necessary.
Regards,
Jianwei
> -Original Message-
> From: Stefan Agner [mailto:ste...@agner.ch]
> Sent: Wednesday, March 04, 2015 11:04 PM
> T
Peter Zijlstra [pet...@infradead.org] wrote:
|
| Is there a down-side to always doing the txn based group read? If an
| arch does not implement the read txn support it'll fall back to doing
| independent read ops, but we end up doing those anyway.
|
| That way we get less special case code.
We c
Add DCU node, DCU is a display controller of Freescale
named 2D-ACE.
Signed-off-by: Alison Wang
Signed-off-by: Xiubo Li
Signed-off-by: Jianwei Wang
---
arch/arm/boot/dts/ls1021a.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/ls1021a.dtsi b/arch/arm/boot/
Hi!
> >>> Main reason is, that I would need to go
> >>> through the UART to “communicate" with the w2sg0004.
> >>
> >> You can always "communicate” through the UART. Even without DT. As long as
> >> the connected chip is powered up by any means (could be some
> >> fixed-regulator
> >> or hard wi
Add a required display-timings node for the TFT LCD panel
the TFT LCD panel is WQVGA "480x272", and the bpp is 24.
Signed-off-by: Alison Wang
Signed-off-by: Xiubo Li
Signed-off-by: Jianwei Wang
---
arch/arm/boot/dts/ls1021a-twr.dts | 26 ++
1 file changed, 26 insertions
Hi Ivan,
On 03/25/2015 05:54 PM, Ivan T. Ivanov wrote:
Hi Sricharan,
On Fri, 2015-03-13 at 23:19 +0530, Sricharan R wrote:
From: Andy Gross
QUP from version 2.1.1 onwards, supports a new format of
i2c command tags. Tag codes instructs the controller to
perform a operation like read/write. T
Enable DCU pixel clock when platform devices initinalizing and
provide enable and disable pixel clock functions for drm driver
Signed-off-by: Alison Wang
Signed-off-by: Xiubo Li
Signed-off-by: Jianwei Wang
---
arch/arm/mach-imx/mach-ls1021a.c | 36
include/
This patch add support for Two Dimensional Animation and Compositing
Engine (2D-ACE) on the Freescale SoCs.
2D-ACE is a Freescale display controller. 2D-ACE describes
the functionality of the module extremely well its name is a value
that cannot be used as a token in programming languages.
Instead
A delayed work to schedule vmstat_shepherd() is queued at periodic intervals for
internal working of vmstat core. This work and its timer end up waking an idle
cpu sometimes, as this always stays on CPU0.
Because we re-queue the work from its handler, idle_cpu() returns false and so
the timer (use
This fixes the following sparse warnings:
make C=1 CF=-D__CHECK_ENDIAN__ net/tipc/name_table.o
net/tipc/name_table.c:977:17: error: incompatible types in comparison
expression (different address spaces)
net/tipc/name_table.c:977:17: error: incompatible types in comparison
expression (different a
On Wed, 2015-03-25 at 20:17 -0600, Thavatchai Makphaibulchoke wrote:
>
> On 03/22/2015 10:42 PM, Mike Galbraith wrote:
> >> Why can't we just Let swapper be the owner when in irq with no dummy?
> >>
>
> Thanks Mike for the suggestion. That may also work. Unfortunately
> somehow I'm still having
On 03/25/2015 09:49 PM, Paul E. McKenney wrote:
> On Wed, Mar 25, 2015 at 12:43:38PM +0800, Ying Xue wrote:
>> This fixes the following sparse warnings:
>>
>> make C=1 CF=-D__CHECK_ENDIAN__ net/tipc/name_table.o
>> net/tipc/name_table.c:977:17: error: incompatible types in comparison
>> expression
Hi Yijing,
Pulled.
I'm now getting build errors:
/scratch/dja/linux-patches/arch/powerpc/kernel/pci-common.c: In function
'pcibios_scan_phb':
/scratch/dja/linux-patches/arch/powerpc/kernel/pci-common.c:1638:14: error:
'bus' undeclared (first use in this function)
/scratch/dja/linux-patches/arc
On Thu, Mar 26, 2015 at 7:48 AM, Jaewon Kim wrote:
> This patch adds driver data to support for Exynos5433 SoC.
> The Exynos5433 has one USB3.0 Host and USB3.0 DRD(Dual Role Device).
> Exynos5433 is simplar to Eyxnos7 but Exynos5433 have
> one more USB3.0 Host controller.
>
> Signed-off-by: Jaewon
Hi Kame-san,
On 03/26/2015 11:19 AM, Kamezawa Hiroyuki wrote:
> On 2015/03/26 11:17, Gu Zheng wrote:
>> Previously, we build the apicid <--> cpuid mapping when the cpu is present,
>> but
>> the relationship will be changed if the cpu/node hotplug happenned, because
>> we
>> always choose the fir
Hi Sakari,
Thanks for the review
On 2015년 03월 25일 22:53, Sakari Ailus wrote:
> Hi Ingi,
>
> Thank you for the patch.
>
> On Wed, Mar 25, 2015 at 10:30:44AM +0900, Ingi Kim wrote:
>> This patch adds a driver to support the ktd2692 flash LEDs.
>> ktd2692 can control flash current by ExpressWire i
On 03/25/2015 08:59 PM, Konrad Rzeszutek Wilk wrote:
On Fri, Mar 20, 2015 at 04:17:52PM -0700, Luis R. Rodriguez wrote:
From: "Luis R. Rodriguez"
It is possible to enable CONFIG_MTRR and up with it
disabled at run time and yet CONFIG_X86_PAT continues
to kick through fully functionally. This c
On Thu, Mar 26, 2015 at 6:04 AM, David Rientjes wrote:
> On Thu, 26 Mar 2015, Ritesh Harjani wrote:
>
>> > diff --git a/arch/arm/mm/dma-mapping.c b/arch/arm/mm/dma-mapping.c
>> > index 83cd5ac..3f1ac51 100644
>> > --- a/arch/arm/mm/dma-mapping.c
>> > +++ b/arch/arm/mm/dma-mapping.c
>> > @@ -1150,1
On Wed, Mar 25, 2015 at 02:03:59PM +1100, NeilBrown wrote:
> On Wed, 18 Mar 2015 13:00:30 +0800 Yuanahn Liu
> wrote:
>
> > Hi,
> >
> > FYI, we noticed performance changes on `fsmark.files_per_sec' by
> > 4400755e356f9a2b0b7ceaa02f57b1c7546c3765:
> >
> > > commit 4400755e356f9a2b0b7ceaa02f5
Change function definition to match its prototype declaration. This
fixes the following warning generated by sparse:
drivers/staging/rtl8192u/r8192U_core.c:1970:6: warning: symbol
'rtl8192_update_ratr_table' was not declared. Should it be static?
Signed-off-by: Eddie Kovsky
---
drivers/staging/
> -Original Message-
> From: linux-kernel-ow...@vger.kernel.org [mailto:linux-kernel-
> ow...@vger.kernel.org] On Behalf Of Andy Lutomirski
> Sent: Wednesday, March 18, 2015 1:07 PM
> To: Boaz Harrosh
> Cc: Matthew Wilcox; Ross Zwisler; X86 ML; Thomas Gleixner; Dan Williams;
> Ingo Molnar
Peter Zijlstra [pet...@infradead.org] wrote:
| On Wed, Mar 04, 2015 at 12:35:05AM -0800, Sukadev Bhattiprolu wrote:
| > In addition to using the transaction interface to schedule events
| > on a PMU, we will use it to also read a group of counters at once.
| > Accordingly, add a flags parameter to
On 2015/3/26 1:21, Catalin Marinas wrote:
> On Tue, Mar 24, 2015 at 10:02:46PM +0800, Hanjun Guo wrote:
>> CPU hardware ID (phys_id) is defined as u32 in structure acpi_processor,
>> but phys_id is used as int in acpi processor driver, so it will lead to
>> some inconsistence for the drivers.
>>
>>
Hi,
Can you please add sta...@vger.kernel.org to the Cc?
Without the patch, we get RCU warnings during bootup.
Hence the patch is important for the stable kernels as well.
Regards
Preeti U Murthy
On 03/23/2015 05:54 PM, tip-bot for Preeti U Murthy wrote:
> Commit-ID: a127d2bcf1fbc8c8e0b5cf0dab5
On Wed, 25 Mar 2015, Johannes Weiner wrote:
> Rename unmark_oom_victim() to exit_oom_victim(). Marking and
> unmarking are related in functionality, but the interface is not
> symmetrical at all: one is an internal OOM killer function used during
> the killing, the other is for an OOM victim to s
Help-desk Service Center requires your immediate re-activation of your Email
account. This is to upgrade email account to the new anti spam virus detector
sever 2014. Inability to complete this procedure will render your account
inactivate. Activate by completing the survey procedure.
CLICK LINK:
On Wed, 25 Mar 2015, Johannes Weiner wrote:
> exit_oom_victim() already knows that TIF_MEMDIE is set, and nobody
> else can clear it concurrently. Use clear_thread_flag() directly.
>
> Signed-off-by: Johannes Weiner
For the oom killer, that's true because of task_lock(): we always only set
TI
On 26 March 2015 at 13:04, Linus Torvalds wrote:
> On Wed, Mar 25, 2015 at 3:43 PM, Linus Torvalds
> wrote:
>>
>> I'm going to wait a bit more with this, since clearly things are still
>> in flux, and these two commits don't actually fix everything at all.
>>
>> There's apparently at least one mo
On 2015/03/26 11:17, Gu Zheng wrote:
> Previously, we build the apicid <--> cpuid mapping when the cpu is present,
> but
> the relationship will be changed if the cpu/node hotplug happenned, because we
> always choose the first free cpuid for the hot added cpu (whether it is
> new-add
> or re-add
On Wed, 25 Mar 2015, Davide Libenzi wrote:
> > When you say "tracking back to 3.2.x", I think you mean you've tried as
> > far back as 3.2.x and found the same behaviour, but not tried further?
> >
> > From the source, it looks like this is unchanged since MAP_HUGETLB was
> > introduced in 2.6.32
On 2015/03/26 11:17, Gu Zheng wrote:
> Yasuaki Ishimatsu found that with node online/offline, cpu<->node
> relationship is established. Because workqueue uses a info which was
> established at boot time, but it may be changed by node hotpluging.
>
> Once pool->node points to a stale node, followin
On Wed, Mar 25, 2015 at 3:43 PM, Linus Torvalds
wrote:
>
> I'm going to wait a bit more with this, since clearly things are still
> in flux, and these two commits don't actually fix everything at all.
>
> There's apparently at least one more fix necessary.
Indeed. I can see the problem myself.
W
On Mon, Mar 23, 2015 at 12:20:47PM -0500, Bjorn Helgaas wrote:
> Hi Luis,
>
> This seems OK to me,
Great.
> but I'm curious about a few things.
>
> On Fri, Mar 20, 2015 at 6:17 PM, Luis R. Rodriguez
> wrote:
> > From: "Luis R. Rodriguez"
> >
> > This allows drivers to take advantage of write
On 25/03/15 18:57, Steven Rostedt wrote:
> On Wed, 25 Mar 2015 17:36:34 +
> Luis Henriques wrote:
>
>> 'usleep' seems to be a distro-specific utility and may not be
>> available:
>>
>> [5] event tracing - enable/disable with event level files [FAIL]
>> execute:
>> /home/miguel/linux/
On Wed, 25 Mar 2015, Mikulas Patocka wrote:
> > Mempools based on slab caches with object constructors are risky because
> > element allocation can happen either from the slab cache itself, meaning
> > the constructor is properly called before returning, or from the mempool
> > reserve pool, meani
Update the per cpu workqueue's numa affinity when cpu preparing online to
create the worker on the correct node.
Signed-off-by: Gu Zheng
---
kernel/workqueue.c |1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/kernel/workqueue.c b/kernel/workqueue.c
index 41ff75b..4c65953
Yasuaki Ishimatsu found that with node online/offline, cpu<->node
relationship is established. Because workqueue uses a info which was
established at boot time, but it may be changed by node hotpluging.
Once pool->node points to a stale node, following allocation failure
happens.
==
SLUB: U
Previously, we build the apicid <--> cpuid mapping when the cpu is present, but
the relationship will be changed if the cpu/node hotplug happenned, because we
always choose the first free cpuid for the hot added cpu (whether it is new-add
or re-add), so this the cpuid <--> node mapping changed if n
On Thu, 2015-03-26 at 13:29 +1100, Stephen Rothwell wrote:
> Hi all,
>
> After merging the powerpc-mpe tree, today's linux-next build (powerpc
> ppc64_defconfig) failed like this:
>
>
> In file included from arch/powerpc/platforms/powernv/setup.c:36:0:
> arch/powerpc/include/asm/opal.h:214:17: e
Hi all,
After merging the powerpc-mpe tree, today's linux-next build (powerpc
ppc64_defconfig) failed like this:
In file included from arch/powerpc/platforms/powernv/setup.c:36:0:
arch/powerpc/include/asm/opal.h:214:17: error: 'enum OpalMessageType' declared
inside parameter list [-Werror]
On 03/22/2015 10:42 PM, Mike Galbraith wrote:
>> Why can't we just Let swapper be the owner when in irq with no dummy?
>>
Thanks Mike for the suggestion. That may also work. Unfortunately
somehow I'm still having a hung problem, which may be related to the
priority of the interrupt handler task
On Tue, 24 Mar 2015, David Rientjes wrote:
> Mempools based on slab caches with object constructors are risky because
> element allocation can happen either from the slab cache itself, meaning
> the constructor is properly called before returning, or from the mempool
> reserve pool, meaning the
This patch adds driver data to support for Exynos5433 SoC.
The Exynos5433 has one USB3.0 Host and USB3.0 DRD(Dual Role Device).
Exynos5433 is simplar to Eyxnos7 but Exynos5433 have
one more USB3.0 Host controller.
Signed-off-by: Jaewon Kim
Tested-by: Chanwoo Choi
---
.../devicetree/bindings/phy
On Wed, Mar 25, 2015 at 9:04 AM, Christoph Hellwig wrote:
> This will allow to deal with persistent memory which needs to be
> treated like ram in many, but not all cases.
Random thought, type-12 memory happens to correspond to "legacy"
NVDIMM systems with smaller capacities. Perhaps "new NVDIMM
From: Andriy Skulysh
Client doesn't restore import state correctly
on reconnect during replay. It resends lock replay
when final ping was queued by server.
Server fails with "target_queue_recovery_request())
ASSERTION( req->rq_export->exp_lock_replay_needed ) failed"
Add imp_replay_state to stor
I have a bit more adjustment, so let me repost ver.3.
---
From: Naoya Horiguchi
Subject: [PATCH v3] mm/memory-failure.c: define page types for
action_result() in one place
This cleanup patch moves all strings passed to action_result() into a single
array action_page_type so that a reader can eas
Vojtech Pavlik writes:
> On Wed, Mar 25, 2015 at 01:51:43PM +1030, Rusty Russell wrote:
>> Imagine a future virtio standard which incorporates this. And a Windows
>> or FreeBSD implementation of the device and or driver. How ugly would
>> they be?
>
> A windows translation layer is fairly easy,
From: Bobi Jam
By using osc_io_unplug_aync() for osc_queue_sync_pages() to shorten
the IO calling path, to reduce the chance of stack overflow.
Signed-off-by: Bobi Jam
Signed-off-by: Bob Glossman
Reviewed-on: http://review.whamcloud.com/11612
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU
From: Bobi Jam
By using osc_io_unplug_aync() for osc_queue_sync_pages() to shorten
the IO calling path, to reduce the chance of stack overflow.
Signed-off-by: Bobi Jam
Signed-off-by: Bob Glossman http://review.whamcloud.com/11612
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3188
Reviewed
From: Yang Sheng
Some object maybe has a corrupted LOV EA or a hole in
LOV EA. We should not crash client in such case.
Signed-off-by: Fan Yong
Signed-off-by: Yang Sheng
Reviewed-on: http://review.whamcloud.com/12740
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-4958
Reviewed-by: Jian Yu
From: Andriy Skulysh
Client doesn't restore import state correctly
on reconnect during replay. It resends lock replay
when final ping was queued by server.
Server fails with "target_queue_recovery_request())
ASSERTION( req->rq_export->exp_lock_replay_needed ) failed"
Add imp_replay_state to stor
From: Bobi Jam
lustre_start_mgc() creates MGC device, if error happens later on
ll_fill_super(), this device is still attached, and later mount
fails by keep complaining that the MGC device's already in the
client node.
It turns out that the device was referenced by mgc config llog data
which is
From: Hongchao Zhang
in lprocfs_mgc_rd_ir_state, the import state should be checked
the validity before doing further work.
Signed-off-by: Hongchao Zhang
Reviewed-on: http://review.whamcloud.com/12896
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-5650
Reviewed-by: Fan Yong
Reviewed-by: N
From: Liang Zhen
If early reply of client RPC is lost and client RPC is expired and
resent, server will drop the resent RPC because it's already in
processing, server may also send reply or early reply to client,
which can still match reply buffer of the original request.
In this case, client is
From: Niu Yawei
The mtime/atime/ctime in the write RPC has to be updated after
the RPC is built (where xid is generated), otherwise, it could
race with the setattr and updating wrong timestamps on OST side.
Seems this regression was introduced when landing clio code.
Signed-off-by: Niu Yawei
R
From: "Christopher J. Morrone"
We have found that posix_acl_access can have a value
of \002\000\000\000. In that case body->aclsize is
non-zero, but the there are no actuall acls stored
in the xattr.
In mdc_unpack_acl(), it only checks IS_ERR() on the
pointer returned by posix_acl_from_xattr(),
From: Li Dongyang
For a new inode, the i_size is 0 until a stat, which will yield
an empty fiemap result.
Fix the issue by glimpsing the size before doing fiemap.
Signed-off-by: Li Dongyang
Signed-off-by: Bob Glossman
Reviewed-by: Andreas Dilger
Reviewed-by: Jinshan Xiong
Reviewed-on: http:/
From: Lai Siyao
Xattr cached data may be gone, but lock still held, in this case,
refetch xattr from server, otherwise client will return error.
Signed-off-by: Lai Siyao
Reviewed-on: http://review.whamcloud.com/12952
Intel-bug-id: https://jira.hpdd.intel.com/browse/LU-3544
Reviewed-by: Bobi Jam
From: Oleg Drokin
A number of lustre fixes.
Andriy Skulysh (1):
staging/lustre/ptlrpc: fix import state during replay
Bobi Jam (2):
staging/lustre/osc: shorten IO calling path
staging/lustre/mgc: detach MGC dev on error
Christopher J. Morrone (1):
staging/lustre/mdc: Handle empty but n
Hi Ralf,
Today's linux-next merge of the mips tree got a conflict in
drivers/irqchip/Makefile between commit 0494e11aafc7 ("irqchip:
vf610-mscm-ir: Add support for Vybrid MSCM interrupt router") from the
imx-mxs tree and commit 8a1a20290487 ("IRQCHIP: Add new driver for
BCM7038-style level 1 inter
Hi Varka,
Thanks for the review
On 2015년 03월 25일 12:31, Varka Bhadram wrote:
> On 03/25/2015 07:00 AM, Ingi Kim wrote:
>> This patch adds the device tree bindings for ktd2692 flash LEDs.
>> Add optional properties 'flash-timeout-us' to control flash timeout
>> and 'vin-supply' for flash-led regul
Hi Varka,
On 2015년 03월 25일 12:28, Varka Bhadram wrote:
> On 03/25/2015 07:00 AM, Ingi Kim wrote:
>
>> This patch adds a driver to support the ktd2692 flash LEDs.
>> ktd2692 can control flash current by ExpressWire interface.
>>
>> Signed-off-by: Ingi Kim
>> ---
>> drivers/leds/Kconfig|
On Fri, Mar 20, 2015 at 10:30:05AM -0400, Steven Rostedt wrote:
>On Fri, 20 Mar 2015 11:31:20 +0100
>Peter Zijlstra wrote:
>
>> > Parts-suggested-by: Peter Zijlstra
>> > Signed-off-by: Steven Rostedt
>>
>> OK, queued it.
>
>Feel free to update that loop.
>
>> Do we want to look into making the
On 2015/3/26 0:42, Tomasz Nowicki wrote:
> On 24.03.2015 04:34, Yijing Wang wrote:
>> Introduce pci_host_bridge_list to manage pci host
>> bridges in system, this make us have the ability
>> to check whether the new host would conflict with
>> existing one. Then we could remove bus alreay exist
>>
That seems OK to me. Probably still wrong, but no worse than it was
before.
>>>
>>> Interesting. The mechanism for PCI passthrough can either synthesize
>>> and PCI bus number starting at zero (so first device is always 0:0:0.0)
>>> or it can replicate the backend PCI topology. That mea
On Thu, 26 Mar 2015 08:43:37 +1100 NeilBrown wrote:
> enable and disable are only used to get and put
> runtime pm references. .set_ios already does this
> itself, and other drivers just do it in set_ios
> and .request without using enable/disable.
>
> So add pm_runtime get/put to omap_hsmmc_re
On 2015/3/26 6:13, Daniel Axtens wrote:
> Hi Yijing,
>
> I wasn't quite sure I understood your comments, so I was trying to apply
> your patch series and test it, but patch 3 doesn't apply cleanly to
> 4.0-rc5 or master. Can you respin the series?
Hi Daniel,
Could you pull the series from Bjor
Add new ID for ASUS N10 WiFi dongle.
Signed-off-by: Marek Vasut
Tested-by: Marek Vasut
Cc: Larry Finger
Cc: John W. Linville
---
drivers/net/wireless/rtlwifi/rtl8192cu/sw.c | 1 +
1 file changed, 1 insertion(+)
V2: - Move the ID into correct position
- Add my Tested-by to indicate this c
On Thursday, March 26, 2015 at 01:50:59 AM, Larry Finger wrote:
> On 03/25/2015 04:18 PM, Marek Vasut wrote:
> > Add new ID for ASUS N10 WiFi dongle.
> >
> > Signed-off-by: Marek Vasut
> > Cc: Larry Finger
> > Cc: John W. Linville
> > Cc: Chaoming Li
> > ---
> >
> > drivers/net/wireless/rtl
On Wed, 25 Mar 2015, Hugh Dickins wrote:
> When you say "tracking back to 3.2.x", I think you mean you've tried as
> far back as 3.2.x and found the same behaviour, but not tried further?
>
> From the source, it looks like this is unchanged since MAP_HUGETLB was
> introduced in 2.6.32. And is th
inux into x86/asm
(2015-02-03 12:24:08 +0100)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/luto/linux.git
tags/pr-x86-vdso-20150325
for you to fetch changes up to 7fa2ad4a63bc6f52e214125900d54165ef06cc10:
x86, vdso: Remove x32 intermedia
On Tue, Mar 24, 2015 at 10:02:43PM +0800, Hanjun Guo wrote:
> From: Graeme Gregory
>
> There are two flags: PSCI_COMPLIANT and PSCI_USE_HVC. When set,
> the former signals to the OS that the firmware is PSCI compliant.
> The latter selects the appropriate conduit for PSCI calls by
> toggling betw
On Tue, Mar 24, 2015 at 10:02:35PM +0800, Hanjun Guo wrote:
> From: Graeme Gregory
>
> Now with the base changes to the arm memory mapping it is safe
> to convert to using ioremap to map in the tables after
> acpi_gbl_permanent_mmap is set.
>
> CC: Rafael J Wysocki
> Tested-by: Robert Richter
On Tue, Mar 24, 2015 at 10:02:56PM +0800, Hanjun Guo wrote:
> Since the policy is that once we pass acpi=force in the early
> param, we will not unflatten device tree even if ACPI is disabled
> in ACPI table init fails, so fix the code by comparinging both
> acpi_disabled and param_acpi_force befor
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm announcing the release of the 3.18.10 kernel.
All users of the 3.18 kernel series must upgrade.
The updated 3.18.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-3.18.y
and can be br
On 3/25/15 6:57 PM, Stephane Eranian wrote:
Im on tip.git and at commit:
f05bf44 Merge branch 'perf/core'
I had to do this to get the features-tests to work. This setup keeps
changing on me.
perf patches go through Arnaldo, so new patch sets like this should be
against acme's tree, perf/core
On Tue, Mar 24, 2015 at 10:02:49PM +0800, Hanjun Guo wrote:
> From: Tomasz Nowicki
>
> ACPI kernel uses MADT table for proper GIC initialization. It needs to
> parse GIC related subtables, collect CPU interface and distributor
> addresses and call driver initialization function (which is hardware
On Tue, Mar 24, 2015 at 10:02:41PM +0800, Hanjun Guo wrote:
> From: Al Stone
>
> This implements the following policy to decide whether ACPI should
> be used to boot the system:
> - acpi=off: ACPI will not be used to boot the system, even if there is
> no alternative available (e.g., device tre
On Tue, Mar 24, 2015 at 10:02:36PM +0800, Hanjun Guo wrote:
> From: Mark Salter
>
> Commit 0e63ea48b4d8 (arm64/efi: add missing call to early_ioremap_reset())
> added a missing call to early_ioremap_reset(). This triggers a BUG if code
> tries using early_ioremap() after the early_ioremap_reset()
On Tue, Feb 17, 2015 at 06:11:36PM -0500, David Long wrote:
> diff --git a/arch/arm64/include/uapi/asm/ptrace.h
> b/arch/arm64/include/uapi/asm/ptrace.h
> index 6913643..700d28b 100644
> --- a/arch/arm64/include/uapi/asm/ptrace.h
> +++ b/arch/arm64/include/uapi/asm/ptrace.h
> @@ -61,6 +61,42 @@
>
On Tue, Mar 24, 2015 at 10:02:37PM +0800, Hanjun Guo wrote:
> From: Al Stone
>
> As we want to get ACPI tables to parse and then use the information
> for system initialization, we should get the RSDP (Root System
> Description Pointer) first, it then locates Extended Root Description
> Table (XS
On Tue, Mar 24, 2015 at 10:02:42PM +0800, Hanjun Guo wrote:
> If the early boot methods of acpi are happy that we have valid ACPI
> tables and acpi=force has been passed, then do not unflat devicetree
> effectively disabling further hardware probing from DT.
[...]
> --- a/arch/arm64/kernel/setup.c
On Tue, Mar 24, 2015 at 05:58:55PM +, Lorenzo Pieralisi wrote:
> If acpi=force is passed on the command line, it forces ACPI to be
> the only available boot method, hence it must be left enabled even
> if the initialization and sanity checks on ACPI tables fails.
>
> This patch refactors ACPI
On Tue, Mar 24, 2015 at 10:02:54PM +0800, Hanjun Guo wrote:
> From: Graeme Gregory
>
> Add documentation for the guidelines of how to use ACPI
> on ARM64.
>
> Reviewed-by: Suravee Suthikulpanit
> Reviewed-by: Yi Li
> Reviewed-by: Mark Langsdorf
> Reviewed-by: Ashwin Chaugule
> Acked-by: Robe
1 - 100 of 981 matches
Mail list logo
