From: Kan Liang
This is the user space patch for Haswell LBR call stack support.
For many profiling tasks we need the callgraph. For example we often
need to see the caller of a lock or the caller of a memcpy or other
library function to actually tune the program. Frame pointer unwinding
is
What kind of underlying disk is it?
On Fri, Nov 14, 2014 at 7:36 AM, Jagan Teki wrote:
> On 14 November 2014 18:50, Roger Heflin wrote:
>> If you are robocoping small files you will hit other limits.
>>
>> Best I have seen with small files is around 30 files/second, and that
>> involves
Intel Processor Trace is an architecture extension that allows for program
flow tracing.
Signed-off-by: Alexander Shishkin
---
arch/x86/include/asm/cpufeature.h | 1 +
arch/x86/kernel/cpu/scattered.c | 1 +
2 files changed, 2 insertions(+)
diff --git a/arch/x86/include/asm/cpufeature.h
When AUX area gets a certain amount of new data, we want to wake up
userspace to collect it. This adds a new control to specify how much
data will cause a wakeup. This is then passed down to pmu drivers via
output handle's "wakeup" field, so that the driver can find the nearest
point where it can
Add support for Intel Processor Trace (PT) to kernel's perf events.
PT is an extension of Intel Architecture that collects information about
software execuction such as control flow, execution modes and timings and
formats it into highly compressed binary packets. Even being compressed,
these
Rockchip RK3288 hdmi is compatible with dw_hdmi
Signed-off-by: Andy Yan
---
Changes in v11: None
Changes in v10:
- add more display mode support mpll configuration for rk3288
Changes in v9:
- move some phy configuration to platform driver
Changes in v8: None
Changes in v7: None
Changes in
For pmus that wish to write data to ring buffer's AUX area, provide
perf_aux_output_{begin,end}() calls to initiate/commit data writes,
similarly to perf_output_{begin,end}. These also use the same output
handle structure. Also, similarly to software counterparts, these
will direct inherited
On Fri, Nov 14, 2014 at 02:18:31PM +0100, Takashi Iwai wrote:
> At Fri, 14 Nov 2014 18:12:21 +0530,
> Sudip Mukherjee wrote:
> >
> > earlier we were ignoring the return value of snd_ak4114_create and
> > always returning 0.
> > now we are returning the actual status. revo_init is calling this
> >
For pmus that don't support scatter-gather for AUX data in hardware, it
might still make sense to implement software double buffering to avoid
losing data while the user is reading data out. For this purpose, add
a pmu capability that guarantees multiple high-order chunks for AUX buffer,
so that
Signed-off-by: Andy Yan
---
Changes in v11: None
Changes in v10: None
Changes in v9: None
Changes in v8:
- Add documentation for rockchip dw hdmi
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in v2: None
For counters that generate AUX data that is bound to the context of a
running task, such as instruction tracing, the decoder needs to know
exactly which task is running when the event is first scheduled in,
before the first sched_switch. The decoder's need to know this stems
from the fact that
HDMI_IH_I2CMPHY_STAT0 is a clear on write register, which indicates i2cm
operation status(i2c transfer done or error), every hdmi phy register
configuration must check this register to make sure the configuration
has complete. But the indication bit should be cleared after check, otherwise
the
On pią, 2014-11-14 at 14:31 +0100, Ulf Hansson wrote:
> On 14 November 2014 09:50, Krzysztof Kozlowski
> wrote:
> > Add system suspend/resume capabilities to the pl330 driver so the amba
> > bus clock could be also unprepared to conserve energy.
> >
> > Signed-off-by: Krzysztof Kozlowski
> >
Add support for Branch Trace Store (BTS) via kernel perf event infrastructure.
The difference with the existing implementation of BTS support is that this
one is a separate PMU that exports events' trace buffers to userspace by means
of AUX area of the perf buffer, which is zero-copy mapped into
RK3288 HDMI will not work without the spare bit of
HDMI_PHY_CONF0 enable
Signed-off-by: Andy Yan
---
Changes in v11:
- split from patch
Changes in v10: None
Changes in v9: None
Changes in v8: None
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3:
At Fri, 14 Nov 2014 19:15:02 +0530,
Sudip Mukherjee wrote:
>
> On Fri, Nov 14, 2014 at 02:18:31PM +0100, Takashi Iwai wrote:
> > At Fri, 14 Nov 2014 18:12:21 +0530,
> > Sudip Mukherjee wrote:
> > >
> > > earlier we were ignoring the return value of snd_ak4114_create and
> > > always returning 0.
From: Peter Zijlstra
This patch introduces "AUX space" in the perf mmap buffer, intended for
exporting high bandwidth data streams to userspace, such as instruction
flow traces.
AUX space is a ring buffer, defined by aux_{offset,size} fields in the
user_page structure, and read/write pointers
When there's new data in the AUX space, output a record indicating its
offset and size and a set of flags, such as PERF_AUX_FLAG_TRUNCATED, to
mean the described data was truncated to fit in the ring buffer.
Signed-off-by: Alexander Shishkin
Cc: Arnaldo Carvalho de Melo
---
This adds support for overwrite mode in the AUX area, which means "keep
collecting data till you're stopped", turning AUX area into a circular
buffer, where new data overwrites old data. It does not depend on data
buffer's overwrite mode, so that it doesn't lose sideband data that is
instrumental
Intel PT cannot be used at the same time as LBR or BTS and will cause a
general protection fault if they are used together. In order to avoid
fixing up GPs in the fast path, instead we disallow creating LBR/BTS
events when PT events are present and vice versa.
Signed-off-by: Alexander Shishkin
Some pmus (such as BTS or Intel PT without multiple-entry ToPA capability)
don't support scatter-gather and will prefer larger contiguous areas for
their output regions.
This patch adds a new pmu capability to request higher order allocations.
Signed-off-by: Alexander Shishkin
---
some platform may not support all the display mode,
add mode_valid interface check it
Signed-off-by: Andy Yan
---
Changes in v11: None
Changes in v10: None
Changes in v9: None
Changes in v8: None
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: None
Usually, pmus that do, for example, instruction tracing, would only ever
be able to have one event per task per cpu (or per perf_context). For such
pmus it makes sense to disallow creating conflicting events early on, so
as to provide consistent behavior for the user.
This patch adds a pmu
On rockchip rk3288, only word(32-bit) accesses are
permitted for hdmi registers. Byte width accesses (writeb,
readb) generate an imprecise external abort.
Signed-off-by: Andy Yan
---
Changes in v11: None
Changes in v10: None
Changes in v9: None
Changes in v8: None
Changes in v7: None
Changes
Hi Peter and all,
Since there weren't too many review comments on the two previous
versions, here's another one with a couple more fixes.
[full description below the changelog]
Changes since v7:
* fixed a bug in aux allocation logic that caused more than
requested pages to be allocated,
Currently, the actual perf ring buffer is one page into the mmap area,
following the user page and the userspace follows this convention. This
patch adds data_{offset,size} fields to user_page that can be used by
userspace instead for locating perf data in the mmap area. This is also
helpful when
2014-10-20 5:40 GMT+03:00 Sasha Levin :
> gcc5 changes the default standard to c11, which makes kernel
> build unhappy.
>
> Explicitly define the kernel standard to be gnu89 which should
> keep everything working exactly like it was before gcc5.
>
Ping.
--
To unsubscribe from this list: send the
Signed-off-by: Andy Yan
---
Changes in v11: None
Changes in v10: None
Changes in v9: None
Changes in v8:
- correct some spelling mistake
- modify ddc-i2c-bus and interrupt description
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes in v4: None
Changes in v3: None
Changes in
From: Yakir Yang
keep the connector & birdge in dw_hdmi.c, handle encoder
in dw_hdmi-imx.c, as most of the encoder operation are
platform specific such as crtc select and panel format
set
Signed-off-by: Andy Yan
Signed-off-by: Yakir Yang
---
Changes in v11: None
Changes in v10: None
Changes
the original imx hdmi driver is under staging/imx-drm,
which depends on imx-drm, so move the imx hdmi driver out
to drm/bridge and rename imx-hdmi to dw_hdmi
Signed-off-by: Andy Yan
---
Changes in v11: None
Changes in v10: None
Changes in v9: None
Changes in v8: None
Changes in v7: None
IMX6 and Rockchip RK3288 and JZ4780 (Ingenic Xburst/MIPS)
use the interface compatible Designware HDMI IP, but they
also have some lightly differences, such as phy pll configuration,
register width, 4K support, clk useage, and the crtc mux configuration
is also platform specific.
To reuse the imx
On Thu, Nov 13, 2014 at 01:27:28PM +0100, Johan Havold wrote:
> On Wed, Nov 12, 2014 at 03:38:09PM +0200, Laurentiu Palcu wrote:
> > This adds support for Diolan DLN2 USB-SPI adapter.
> >
> > Information about the USB protocol interface can be found in the
> > Programmer's Reference Manual [1],
drm driver may probe before the i2c bus, so the driver should
defer probing until it is available
Signed-off-by: Andy Yan
---
Changes in v11: None
Changes in v10: None
Changes in v9: None
Changes in v8: None
Changes in v7: None
Changes in v6: None
Changes in v5: None
Changes in v4:
- defer
CHECK: Alignment should match open parenthesis
+ if ((hdmi->vic == 10) || (hdmi->vic == 11) ||
+ (hdmi->vic == 12) || (hdmi->vic == 13) ||
CHECK: braces {} should be used on all arms of this statement
+ if (hdmi->hdmi_data.video_mode.mdvi)
[...]
+ else {
[...]
We found Freescale imx6 and Rockchip rk3288 and Ingenic JZ4780 (Xburst/MIPS)
use the interface compatible Designware HDMI IP, but they also have some
lightly differences, such as phy pll configuration, register width(imx hdmi
register is one byte, but rk3288 is 4 bytes width and can only be
On 14 November 2014 18:50, Roger Heflin wrote:
> If you are robocoping small files you will hit other limits.
>
> Best I have seen with small files is around 30 files/second, and that
> involves multiple copies going on. Remember with a small files there
> are several reads and writes that need
Convert existing users of pte_numa and friends to the new helper. Note
that the kernel is broken after this patch is applied until the other
page table modifiers are also altered. This patch layout is to make
review easier.
Needs-signed-off: Aneesh Kumar
Needs-signed-off: Linus Torvalds
This patch removes the NUMA PTE bits and associated helpers. As a side-effect
it increases the maximum possible swap space on x86-64.
One potential source of problems is races between the marking of PTEs
PROT_NONE, NUMA hinting faults and migration. It must be guaranteed that
a PTE being
On Fri, 14 Nov 2014 12:12:00 +0100
Paolo Bonzini wrote:
> This completes the optimization from the previous patch, by
> removing the KVM_MEM_SLOTS_NUM-iteration loop from insert_memslot.
>
> Signed-off-by: Paolo Bonzini
> ---
> virt/kvm/kvm_main.c | 39 +++
2014-11-14 12:12+0100, Paolo Bonzini:
> This completes the optimization from the previous patch, by
> removing the KVM_MEM_SLOTS_NUM-iteration loop from insert_memslot.
>
> Signed-off-by: Paolo Bonzini
> ---
> virt/kvm/kvm_main.c | 39 +++
> 1 file changed,
Hi Arnd,
Thanks for taking the time to explain this.
On Fri, 14 Nov 2014, Arnd Bergmann wrote:
> > address of the device's resources within the address space defined by its
> > parent bus").
>
> You will also have to add an appropriate 'ranges' property then.
>
> > Or maybe you meant, if I
Faults on the huge zero page are pointless and there is a BUG_ON
to catch them during fault time. This patch reintroduces a check
that avoids marking the zero page PAGE_NONE.
Signed-off-by: Mel Gorman
---
include/linux/huge_mm.h | 3 ++-
mm/huge_memory.c| 13 -
mm/memory.c
This is follow up from the "pipe/page fault oddness" thread.
Automatic NUMA balancing depends on being able to protect PTEs to trap a
fault and gather reference locality information. Very broadly speaking it
would mark PTEs as not present and use another bit to distinguish between
NUMA hinting
With PROT_NONE, the traditional page table manipulation functions are
sufficient.
Needs-signed-off: Aneesh Kumar
Needs-signed-off: Linus Torvalds
Signed-off-by: Mel Gorman
---
include/linux/huge_mm.h | 3 +--
mm/huge_memory.c| 33 +++--
mm/memory.c
Commit b38af4721f59 ("x86,mm: fix pte_special versus pte_numa") adjusted
the pte_special check to take into account that a special pte had SPECIAL
and neither PRESENT nor PROTNONE. Now that NUMA hinting PTEs are no
longer modifying _PAGE_PRESENT it should be safe to restore the original
pte_protnone_numa is only safe to use after VMA checks for PROT_NONE are
complete. Treating a real PROT_NONE PTE as a NUMA hinting fault is going
to result in strangeness so add a check for it. BUG_ON looks like overkill
but if this is hit then it's a serious bug that could result in corruption
so
This is a preparatory patch that introduces protnone helpers for automatic
NUMA balancing.
Needs-signed-off: Aneesh Kumar
Needs-signed-off: Linus Torvalds
Signed-off-by: Mel Gorman
---
arch/powerpc/include/asm/pgtable.h | 11 +++
arch/x86/include/asm/pgtable.h | 16
My apologies, yes I was concerned about LATEST. Try the test that Steve
described and if that works I'm happy.
--
paul moore
www.paul-moore.com
On November 13, 2014 8:09:11 PM Richard Guy Briggs wrote:
On 14/11/13, Paul Moore wrote:
> On Thursday, November 13, 2014 03:29:10 PM Richard Guy
On 14 November 2014 09:50, Krzysztof Kozlowski wrote:
> Add system suspend/resume capabilities to the pl330 driver so the amba
> bus clock could be also unprepared to conserve energy.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> drivers/dma/pl330.c | 41
On Thu, 13 Nov 2014, Seth Jennings wrote:
> On Thu, Nov 13, 2014 at 11:16:00AM +0100, Miroslav Benes wrote:
> >
> > Hi,
> >
> > thank you for the first version of the united live patching core.
> >
> > The patch below implements some of our review objections. Changes are
> > described in the
On 11/14/2014 03:58 AM, Doug Anderson wrote:
> Addy,
>
> On Tue, Nov 4, 2014 at 6:03 AM, Addy Ke wrote:
>> The bit of sdio interrupt is 16 in designware implementation,
>> but it is 24 on Rockchip SoCs.This patch add sdio_id0 for the
>> number of slot0 in the SDIO interrupt registers.
>>
>>
If you are robocoping small files you will hit other limits.
Best I have seen with small files is around 30 files/second, and that
involves multiple copies going on. Remember with a small files there
are several reads and writes that need to be done to complete a create
of a small file and each
Since commit 20cde694027e ("x86, ia64: Move EFI_FB
vga_default_device() initialization to pci_vga_fixup()") in the 3.17
merge window, the EFI framebuffer depends on the VGA arbitration
layer. However, the configuration does not reflect this, which leads
to a hard-to-find bug when FB_EFI is
Hello, Michael, Petr.
On Wed, Nov 12, 2014 at 03:32:04PM +0200, Michael S. Tsirkin wrote:
> > + /* The workqueue servicing the balloon. */
> > + struct workqueue_struct *wq;
> > + struct work_struct wq_work;
>
> We could use system_freezable_wq instead.
> I do agree a dedicated wq is
At Fri, 14 Nov 2014 18:12:21 +0530,
Sudip Mukherjee wrote:
>
> earlier we were ignoring the return value of snd_ak4114_create and
> always returning 0.
> now we are returning the actual status. revo_init is calling this
> function, and revo_init is checking the return value.
>
> Signed-off-by:
Hi, Addy.
Did you use the DW_MCI_QUIRK_IDMAC_DTO?
I'm not sure, but i wonder if you get what result when you use above quirk.
And i will check more this patch at next week.
Thanks for your efforts.
Best Regards,
Jaehoon Chung
On 11/14/2014 10:05 PM, Addy Ke wrote:
> From: Addy
>
> This
On Thu 2014-11-13 20:12:56, Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> The trace_seq_printf() and friends are used to store strings into a buffer
> that can be passed around from function to function. If the trace_seq buffer
> fills up, it will not print any more. The return
On Thu, Nov 13, 2014 at 02:24:15PM -0500, Pranith Kumar wrote:
> Recently lockless_dereference() was added which can be used in place of
> hard-coding smp_read_barrier_depends(). The following PATCH makes the change.
>
> Signed-off-by: Pranith Kumar
How should this be routed? There's a pending
Hello, Andrew.
On Thu, Nov 13, 2014 at 02:40:41PM -0800, Andrew Morton wrote:
> In that case tjpointer_add() would need to do a kmalloc() for each inode
> which is added to the bdev/cdev, just as ptrset_add() is doing.
>
> That might require a nasty preload thing. But really, for just two
>
Hi,
back in 2012 [1] there was a discussion about a forking load which
accumulates anon_vmas. There was a trivial test case which triggers this
and can potentially deplete the memory by local user.
We have a report for an older enterprise distribution where nsd is
suffering from this issue most
From: Addy
This patch add a new quirk to notify the driver to teminate
current transfer and report a data timeout to the core,
if data over interrupt does NOT come within the given time.
dw_mmc call mmc_request_done func to finish transfer depends on
data over interrupt. If data over interrupt
On 14 November 2014 04:35, Yuanhan Liu wrote:
> On Wed, Nov 12, 2014 at 03:44:34PM +0100, Vincent Guittot wrote:
>> On 10 November 2014 06:54, wrote:
>> > FYI, we noticed the below changes on
>> >
>> > https://git.linaro.org/people/mturquette/linux.git eas-next
>> > commit
On (11/13/14 21:37), Mahendran Ganesh wrote:
> After patch [1], the zs_exit is only called in module exit.
> So add __init/__exit to zs_init/zs_exit.
>
> [1] mm/zsmalloc: avoid unregister a NOT-registered zsmalloc zpool driver
>
> Signed-off-by: Mahendran Ganesh
makes sense.
-ss
>
Mahendran Ganesh reported that zpool-enabled zsmalloc should not
call zpool_unregister_driver() from zs_init() if cpu notifier
registration has failed, because error handling is performed
before we register the driver via zpool_register_driver() call.
Factor out cpu notifier registration and
2014-11-14 6:14 GMT+01:00 Howard Chen :
> * A dtsi for boards based on Mediatek MT6592 SoCs
> * Compatible string in arch/arm/mach-mediatek/mediatek.c
>
> Signed-off-by: Howard Chen
I applied the whole series [0].
Thanks.
[0] https://github.com/mbgg/linux-mediatek/commits/v3.19-next/dts
> ---
Hi,
I'm doing a performance testing on my bench ARM box.
1. dd test: I have validate the read and write by mounting /dev/sda1
with ext4 filesystem,
able to get the good performance numbers where read is high
compared to write
2. robocopy test:
- mkfs.ext4 /dev/sda1
- mount
On Fri, 14 Nov 2014 13:41:26 +0100
Petr Mladek wrote:
> > -static enum print_line_t
> > +static void
> > print_graph_irq(struct trace_iterator *iter, unsigned long addr,
> > enum trace_type type, int cpu, pid_t pid, u32 flags)
> > {
> > - int ret;
> > struct trace_seq *s =
On architectures that have support for efficient unaligned access
struct printk_log has 4-byte alignment.
Specify alignment attribute in type declaration.
The whole point of this patch is to fix deadlock which happening
when UBSan detects unaligned access in printk() thus UBSan recursively
calls
Next spin of UBSan and there are two patches from now.
"Two there should be; no more, no less. One to embody the UBSan,
the other to not deadlock it."
Patches on top of v3.18-rc4. As usual they are available in git:
git://github.com/aryabinin/linux ubsan/v2
Changes since v1:
-
UBSan uses compile-time instrumentation to catch undefined behavior (UB).
Compiler inserts code that perform certain kinds of checks before
operations that could cause UB. If check fails (i.e. UB detected)
__ubsan_handle_* function called to print error message.
So the most of the work is done by
On 11/14/2014 12:58 PM, David Vrabel wrote:
On 13/11/14 09:21, Juergen Gross wrote:
On 11/11/2014 06:47 PM, David Vrabel wrote:
Can you please test this with the following guests/scenarios.
* 64 bit dom0 with PCI devices with high MMIO BARs.
I'm not sure I have a machine available with
earlier we were ignoring the return value of snd_ak4114_create and
always returning 0.
now we are returning the actual status. revo_init is calling this
function, and revo_init is checking the return value.
Signed-off-by: Sudip Mukherjee
---
change in v3: spec->ak4114 is now dereferenced if we
On Thu 2014-11-13 20:12:50, Steven Rostedt wrote:
> From: "Steven Rostedt (Red Hat)"
>
> Instead of doing individual checks all over the place that makes the code
> very messy. Just check trace_seq_has_overflowed() at the end or in
> strategic places.
>
> This makes the code much cleaner and
Currently it is not possible to exploit FIQ for systems with a GIC, even if
the systems are otherwise capable of it. This patch makes it possible
for IPIs to be delivered using FIQ.
To do so it modifies the register state so that normal interrupts are
placed in group 1 and specific IPIs are
Hi Thomas, Hi Jason,
[Today I was *planning* to ask if patches 1 & 2 are OK for the irqchip
tree. However just to be on the safe side I ran some build tests and
they picked up something I overlooked last time. So instead of a poke
I've put out a new patchset instead. Just to be sure I ran
Currently calling printk() from a FIQ can result in deadlock on
irq_controller_lock within gic_raise_softirq(). This occurs because
printk(), which is otherwise structured to survive calls from FIQ/NMI,
calls this function to raise an IPI when it needs to wake_up_klogd().
This patch fixes the
Add basic infrastructure for triggering a backtrace of other CPUs
via an IPI, preferably at FIQ level. It is intended that this shall
be used for cases where we have detected that something has already
failed in the kernel.
Signed-off-by: Russell King
Signed-off-by: Daniel Thompson
---
Previous changes have introduced both a replacement default FIQ handler
and an implementation of arch_trigger_all_cpu_backtrace for ARM but
these are currently independent of each other.
This patch plumbs together these features making it possible, on platforms
that support it, to trigger
On Fri, 14 Nov 2014 18:54:23 +0900 (JST)
HATAYAMA Daisuke wrote:
> From: Petr Tesarik
> Subject: Re: [PATCH] kdump, x86: report actual value of phys_base in
> VMCOREINFO
> Date: Fri, 14 Nov 2014 09:31:45 +0100
>
> > On Fri, 14 Nov 2014 10:42:35 +0900 (JST)
> > HATAYAMA Daisuke wrote:
> >
>
On Fri, 07 Nov, at 01:38:36PM, Peter Zijlstra wrote:
>
> For optional goodness:
>
> if (nr_limbo > max_scan_size)
> break;
>
> Which will limit the number of RMIDs you'll scan from the IPI, and
> thereby limit the time taken there.
To limit the amount of
On Fri, 14 Nov 2014 07:31:46 -0500
Steven Rostedt wrote:
> On Fri, 14 Nov 2014 12:13:51 +
> Daniel Thompson wrote:
>
> > BTW I did check on kernel.org before punting them back on the list:
> > https://git.kernel.org/cgit/linux/kernel/git/rostedt/linux-trace.git/log/?h=for-next
> >
> > Am
On Wed, Nov 12, 2014 at 09:39:52AM +, Vinod Koul wrote:
> On Thu, Nov 06, 2014 at 05:20:12PM +, Liviu Dudau wrote:
> > The datasheet for PL330 says that the data buffer value in the CRD
> > register is 10bits wide. However, the value stored is "minus one",
> > which the driver corrects
On Fri, 14 Nov 2014 12:13:51 +
Daniel Thompson wrote:
> BTW I did check on kernel.org before punting them back on the list:
> https://git.kernel.org/cgit/linux/kernel/git/rostedt/linux-trace.git/log/?h=for-next
>
> Am I looking in the wrong place or are they not aimed at linux-next just
>
Thank you,
fixes are queued for review.
Am 14.11.2014 um 01:07 schrieb Jeremiah Mahler:
>
> In version 20141113 of the linux-next kernel, if it is compiled with
> CONFIG_ATH9K_DEBUGFS unset, an error about ath_cmn_process_fft() being
> redefined will be produced.
>
> make
> ...
> LD
This patch adds support for configuring keyboard backlight settings on supported
Dell laptops. It exports kernel leds interface and uses Dell SMBIOS tokens or
keyboard class interface.
With this patch it is possible to set:
* keyboard backlight level
* timeout after which will be backlight
On 14/11/14 11:59, Steven Rostedt wrote:
> On Fri, 14 Nov 2014 09:08:21 +
> Daniel Thompson wrote:
>
>> On 14/11/14 02:26, Steven Rostedt wrote:
>>> On Thu, 6 Nov 2014 12:41:55 +
>>> Daniel Thompson wrote:
>>>
Currently kdb's ftdump command unconditionally crashes due to a null
On Fri, 14 Nov 2014, Jiang Liu wrote:
> On 2014/11/14 9:31, Thomas Gleixner wrote:
> > On Fri, 14 Nov 2014, Yijing Wang wrote:
> >
> > Could you please use a mail client which does proper line wraps or
> > configure yours to do so?
> >
> >> Associate the irq domain and PCI bus is not necessary,
On Do, 2014-11-13 at 17:36 -0800, Alexei Starovoitov wrote:
> the current meaning of BPF_MAP_UPDATE_ELEM syscall command is:
> either update existing map element or create a new one.
> Initially the plan was to add a new command to handle the case of
> 'create new element if it didn't exist', but
Russell,
this patch needs your feedback.
- Stefano
On Wed, 12 Nov 2014, Stefano Stabellini wrote:
> Introduce a boolean flag and an accessor function to check whether a
> device is dma_coherent. Set the flag from set_arch_dma_coherent_ops.
>
> Signed-off-by: Stefano Stabellini
> Signed-off-by:
On Fri, 14 Nov 2014 09:08:21 +
Daniel Thompson wrote:
> On 14/11/14 02:26, Steven Rostedt wrote:
> > On Thu, 6 Nov 2014 12:41:55 +
> > Daniel Thompson wrote:
> >
> >> Currently kdb's ftdump command unconditionally crashes due to a null
> >> pointer de-reference whenever the command is
16 minors per MMC block device are required to boot Rinato (Gear 2)
board because up to 15 partitions are used.
With default 8 minors booting failed with:
[1.329092] mmcblk0: mmc0:0001 F5X5MA 3.64 GiB
[1.329448] mmcblk0boot0: mmc0:0001 F5X5MA partition 1 4.00 MiB
[1.329627]
On Fri, 14 Nov 2014 12:25:23 +0100
Petr Mladek wrote:
> On Thu 2014-11-13 20:12:46, Steven Rostedt wrote:
> > From: "Steven Rostedt (Red Hat)"
> >
> > Adding a trace_seq_has_overflowed() which returns true if the trace_seq
> > had too much written into it allows us to simplify the code.
> >
>
On 13/11/14 09:21, Juergen Gross wrote:
> On 11/11/2014 06:47 PM, David Vrabel wrote:
>>
>> Can you please test this with the following guests/scenarios.
>>
>> * 64 bit dom0 with PCI devices with high MMIO BARs.
>
> I'm not sure I have a machine available with this configuration.
We have a bunch
Hi,
this series adds support for hardware-triggered thermal reset to the PMC
driver. Namely, it adds device tree properties for specifying the I2C
command to be sent when thermtrip is triggered.
The soctherm driver has now been acked and will be taken into 3.19, so we
can move forward with this.
From: Mikko Perttunen
Hardware-triggered thermal reset requires configuring the I2C
reset procedure. This configuration is read from the device tree,
so document the relevant properties in the binding documentation.
Signed-off-by: Mikko Perttunen
---
adding Matthew Khouzam to the loop
jirka
On Thu, Nov 13, 2014 at 08:24:48PM +0100, Sebastian Andrzej Siewior wrote:
> I try to get through my ctf mailbox and I hoped I can finish it today
> but I don't make it completely…
>
> On 11/06/2014 04:25 AM, Alexandre Montplaisir wrote:
> > "mvn clean
From: Mikko Perttunen
This adds a device tree controlled option to enable PMC-based
thermal reset in overheating situations. Thermtrip is supported on
Tegra30, Tegra114 and Tegra124. The thermal reset only works when
the thermal sensors are calibrated, so a soctherm driver is also
required.
The
From: Mikko Perttunen
This adds the required information to reset the board during an overheating
situation to the Jetson TK1 device tree. The thermal reset is handled by the
PMC by sending an I2C message to the PMIC. The entries specify the I2C
message to be sent.
Signed-off-by: Mikko
Hello Corey,
On Wednesday, November 12, 2014 09:05:00 AM Corey Minyard wrote:
> This is probably a good idea, but I would expect that the BMC would
> respond with a "Request data field length limit exceeded. (C8h)"
> completion code in this case instead of being silent. Though as far as
> I can
Check that dma_ops are initialized correctly.
Signed-off-by: Michal Simek
---
Functions dma_mmap_attrs(), dma_get_sgtable_attrs()
already have this checking.
The whole discussion was originally here:
https://lkml.org/lkml/2013/6/3/255
We have middle solution where some functions have this
501 - 600 of 1460 matches
Mail list logo