Signed-off-by: Irina Tirdea
---
drivers/input/touchscreen/goodix.c | 19 ++-
1 file changed, 10 insertions(+), 9 deletions(-)
diff --git a/drivers/input/touchscreen/goodix.c
b/drivers/input/touchscreen/goodix.c
index 7f0da7e..1f0625a 100644
---
Add support for runtime power management so that the device is
turned off when not used (when the userspace holds no open
handles of the input device). The device uses autosuspend with a
default delay of 2 seconds, so the device will suspend if no
handles to it are open for 2 seconds.
The runtime
Add ESD (Electrostatic Discharge) protection mechanism.
The driver enables ESD protection in HW and checks a register
to determine if ESD occurred. If ESD is signalled by the HW,
the driver will reset the device.
The ESD poll time (in ms) can be set through the sysfs property
esd_timeout. If it
Goodix devices have a configuration information register area that
specify various parameters for the device. The configuration information
has a specific format described in the Goodix datasheet. It includes X/Y
resolution, maximum supported touch points, interrupt flags, various
sesitivity
Each of the Goodix devices supported by this driver has a fixed size for
the configuration information registers. The size varies depending on the
device and is specified in the datasheet.
Use the proper configuration length as specified in the datasheet for
each device model, so we do not read
Implement suspend/resume for goodix driver.
The suspend and resume process uses the gpio pins.
If the device ACPI/DT information does not declare gpio pins,
suspend/resume will not be available for these devices.
This is based on Goodix datasheets for GT911 and GT9271
and on Goodix driver
After power on, it is recommended that the driver resets the device.
The reset procedure timing is described in the datasheet and is used
at device init (before writing device configuration) and
for power management. It is a sequence of setting the interrupt
and reset pins high/low at specific
On Fri, Oct 02, 2015 at 02:18:44PM +0900, Namhyung Kim wrote:
> Since it's gonna share struct mmap with dummy tracking evsel to track
> meta events only, let's move auxtrace out of struct perf_mmap.
after applying this one I got:
[jolsa@krava perf]$ ./perf record kill
failed to mmap with 13
Il giovedì 8 ottobre 2015 12:06:15 CEST, Mika Westerberg ha scritto:
On Mon, Oct 05, 2015 at 05:59:38PM +0200, Niccolò Belli wrote:
Il lunedì 5 ottobre 2015 15:54:49 CEST, Mika Westerberg ha scritto: ...
It looks like a memory corruption somewhere. Unfortunately it is not
obvious from the log
Add driver for the digital imput to PWM output stereo
class D amplifier. It comes with filter, digitally
controlled gain, an equalizer and a dmphase filter.
Signed-off-by: Songjun Wu
---
Changes in v3:
- Remove '.owner' field in variable 'atmel_classd_driver',
since the core will do it.
-
On Fri, Oct 02, 2015 at 02:18:43PM +0900, Namhyung Kim wrote:
> It is more convenient saving mmap length rather than (bit) mask. With
> this patch, we can eliminate dependency to perf_evlist other than
> getting mmap_desc for dealing with mmaps. The mask and length can be
> converted using
The Audio Class D Amplifier driver includes two parts.
1) Driver code to implement the Audio Class D Amplifier function.
2) Device tree binding document, it describes how to add the Audio
Class D Amplifier in device tree.
Changes in v3:
- Remove '.owner' field in variable
DT binding documentation for this new ASoC driver.
Signed-off-by: Songjun Wu
---
Changes in v3: None
Changes in v2:
- Delete the device node "Sound" in dts.
.../devicetree/bindings/sound/atmel-classd.txt | 52
1 file changed, 52 insertions(+)
create mode 100644
On Mon, Oct 05, 2015 at 06:02:00PM +0100, Suzuki K. Poulose wrote:
> diff --git a/arch/arm64/kernel/smp.c b/arch/arm64/kernel/smp.c
> index cb3e0d8..6987de4 100644
> --- a/arch/arm64/kernel/smp.c
> +++ b/arch/arm64/kernel/smp.c
> @@ -163,14 +163,14 @@ asmlinkage void secondary_start_kernel(void)
>
On Mon, Oct 05, 2015 at 05:59:38PM +0200, Niccolò Belli wrote:
> Il lunedì 5 ottobre 2015 15:54:49 CEST, Mika Westerberg ha scritto:
> >On Mon, Oct 05, 2015 at 03:41:09PM +0200, Niccolò Belli wrote:
> >>Il lunedì 5 ottobre 2015 12:46:45 CEST, Mika Westerberg ha scritto: ...
> >
> >It says:
> >
>
> -Original Message-
> From: Pavel Machek [mailto:pa...@ucw.cz]
> Sent: 05 October, 2015 23:58
> To: Tirdea, Irina
> Cc: Dmitry Torokhov; Bastien Nocera; Aleksei Mamlin;
> linux-in...@vger.kernel.org; Mark Rutland; Purdila, Octavian; linux-
> ker...@vger.kernel.org;
On Thu, Oct 01, 2015 at 12:34:54AM +, Bondarenko, Anton wrote:
> On 30.09.2015 10:35, Robin Gong wrote:
> > On Fri, Sep 25, 2015 at 07:57:10PM +0200, Anton Bondarenko wrote:
> >> @@ -91,11 +91,15 @@ struct spi_imx_data {
> >>
> >>struct completion xfer_done;
> >>void __iomem *base;
>
On Thu, Oct 8, 2015 at 5:47 PM, Russell King - ARM Linux
wrote:
>
> On Thu, Oct 08, 2015 at 05:43:11PM +0800, Ley Foon Tan wrote:
> > +static int altera_pcie_cfg_write(struct pci_bus *bus, unsigned int devfn,
> > + int where, int size, u32 value)
> > +{
> > +
Function graph tracer modifies a return address (LR) in a stack frame
to hook a function return. This will result in many useless entries
(return_to_handler) showing up in a stack tracer's output.
This patch replaces such entries with originals values preserved in
current->ret_stack[].
we have two processes to do:
P1#: ifconfig eth0 down; which will call bnx2_close, then will
, and set Null to stats_blk
P2#: ifconfig eth0; which will call bnx2_get_stats64, it will
use stats_blk.
In one case:
--P1#-- --P2#--
stats_blk(no null)
Jan Kara writes:
>> ---
>> a/kernel/panic.c~panic-release-stale-console-lock-to-always-get-the-logbuf-printed-out-fix
>> +++ a/kernel/panic.c
>> @@ -149,10 +149,10 @@ void panic(const char *fmt, ...)
>> bust_spinlocks(0);
>>
>> /*
>> - * We may have ended up killing the CPU
A function prologue analyzer is a requisite for implementing stack tracer
and getting better views of stack usages on arm64.
To implement a function prologue analyzer, we have to be able to decode,
at least, stp, add, sub and mov instructions.
This patch adds decoders for those instructions, that
CONFIG_FRAME_POINTER is always enabled on arm64, adding
-fno-omit-frame-pointer, while ftrace, CONFIG_FUNCTION_TRACER, adds -pg
to KBUILD_CFLAGS.
The combination of these options, however, does not implicitly enables
-fno-omit-leaf-frame-pointer option, and no leaf functions are actually
traced
Stack tracer on arm64, check_stack(), is uniqeue in the following
points:
* analyze a function prologue of a traced function to estimate a more
accurate stack pointer value, replacing naive ' + 0x10.'
* use walk_stackframe(), instead of slurping stack contents as orignal
check_stack() does, to
A stack frame may be used in a different way depending on cpu architecture.
Thus it is not always appropriate to slurp the stack contents, as current
check_stack() does, in order to calcurate a stack index (height) at a given
function call. At least not on arm64.
In addition, there is a
On arm64, no PC values returned by save_stack_trace() will match to LR
values saved in stack frames on a stack after the following commit:
commit e306dfd06fcb ("ARM64: unwind: Fix PC calculation")
As a result, the output from stack tracer will be messed up.
This patch introduces an
Function graph tracer modifies a return address (LR) in a stack frame by
calling ftrace_prepare_return() in a traced function's function prologue.
The current code does this modification before preserving an original
address at ftrace_push_return_trace() and there is always a small window
of
Hi,
Arnd Bergmann writes:
> With those two changes in place, we no longer need the fake
> pci_sys_data/pci_bus structures for faking config space writes,
> and the stack usage goes down as well.
> arch/arm/mach-cns3xxx/pcie.c | 71
>
This is the third patch series for fixing stack tracer on arm64.
The original issue was reported by Jungseok[1], and then I found more
issues[2].
(Steven, Jungseok, sorry for not replying to your comments directly.)
I address here all the issues and implement fixes described in [2] except
for
On 07/10/15 20:36, Stephen Warren wrote:
> On 10/07/2015 10:19 AM, Jon Hunter wrote:
>>
>> On 07/10/15 17:09, Stephen Warren wrote:
>>> On 10/07/2015 02:43 AM, Jon Hunter wrote:
On 07/10/15 00:04, Stephen Warren wrote:
> On 10/05/2015 06:10 AM, Jon Hunter wrote:
>> Add
Hello,
On 2015-10-08 11:35, Javier Martinez Canillas wrote:
Hello,
On 10/08/2015 08:23 AM, Marek Szyprowski wrote:
Hello,
On 2015-10-08 08:02, Krzysztof Kozlowski wrote:
On 07.10.2015 23:26, Marek Szyprowski wrote:
Hello,
On 2015-10-07 02:30, Krzysztof Kozlowski wrote:
Introduction
On 07/10/15 18:16, Catalin Marinas wrote:
On Mon, Oct 05, 2015 at 06:01:56PM +0100, Suzuki K. Poulose wrote:
diff --git a/arch/arm64/include/asm/cpufeature.h
b/arch/arm64/include/asm/cpufeature.h
index b5f313d..7ed92f2 100644
--- a/arch/arm64/include/asm/cpufeature.h
+++
Andrew Morton writes:
> (cc Jan)
>
> On Wed, 7 Oct 2015 19:02:22 +0200 Vitaly Kuznetsov
> wrote:
>
>> In some cases we may end up killing the CPU holding the console lock
>> while still having valuable data in logbuf. E.g. I'm observing the
>> following:
>> - A crash is happening on one CPU
On Wed, Oct 07, 2015 at 09:48:58AM -0700, Paul E. McKenney wrote:
> > Some implementation choice requires this barrier upgrade -- and in
> > another email I suggest its the whole tree thing, we need to firmly
> > establish the state of one level before propagating the state up etc.
> >
> > Now
Display the whole word of "alarm", make it look more comfortable.
Signed-off-by: Zhen Lei
---
drivers/rtc/rtc-proc.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/rtc/rtc-proc.c b/drivers/rtc/rtc-proc.c
index ffa69e1..ef83f34 100644
---
On Thu, Oct 08, 2015 at 05:43:11PM +0800, Ley Foon Tan wrote:
> +static int altera_pcie_cfg_write(struct pci_bus *bus, unsigned int devfn,
> + int where, int size, u32 value)
> +{
> + struct altera_pcie *pcie = bus->sysdata;
> + u32 data32;
> + u32 shift =
Commit-ID: ae938802443732e77d01f8d5b52b900b9327ff30
Gitweb: http://git.kernel.org/tip/ae938802443732e77d01f8d5b52b900b9327ff30
Author: Arnaldo Carvalho de Melo
AuthorDate: Tue, 6 Oct 2015 17:46:46 -0300
Committer: Arnaldo Carvalho de Melo
CommitDate: Wed, 7 Oct 2015 19:41:50 -0300
Commit-ID: 1178bfd41f3ab6914eb6884875b776bc3032c9b5
Gitweb: http://git.kernel.org/tip/1178bfd41f3ab6914eb6884875b776bc3032c9b5
Author: Jiri Olsa
AuthorDate: Tue, 6 Oct 2015 14:25:12 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 6 Oct 2015 18:04:59 -0300
perf tools: Use
Commit-ID: 38349665388fb079fb2bc8c46db9446dd976802a
Gitweb: http://git.kernel.org/tip/38349665388fb079fb2bc8c46db9446dd976802a
Author: Andrzej Hajda
AuthorDate: Tue, 6 Oct 2015 11:00:17 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 6 Oct 2015 18:04:59 -0300
perf tools:
Commit-ID: beeaaeb3684d97e89548c1b6b6275329214014df
Gitweb: http://git.kernel.org/tip/beeaaeb3684d97e89548c1b6b6275329214014df
Author: Jiri Olsa
AuthorDate: Tue, 6 Oct 2015 14:25:11 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 6 Oct 2015 18:04:59 -0300
perf tools:
Commit-ID: 0974d2c9719a4c74fea0f6886b9922b100b903a6
Gitweb: http://git.kernel.org/tip/0974d2c9719a4c74fea0f6886b9922b100b903a6
Author: Jiri Olsa
AuthorDate: Tue, 6 Oct 2015 14:25:10 +0200
Committer: Arnaldo Carvalho de Melo
CommitDate: Tue, 6 Oct 2015 18:04:58 -0300
perf tools: Get
This patch adds Altera PCIe MSI driver. This soft IP supports configurable
number of vectors, which is a dts parameter.
Signed-off-by: Ley Foon Tan
Reviewed-by: Marc Zyngier
---
drivers/pci/host/Kconfig | 8 +
drivers/pci/host/Makefile | 1 +
On Thu, Oct 08, 2015 at 12:38:28PM +0300, Michael S. Tsirkin wrote:
> On Thu, Oct 08, 2015 at 10:59:10AM +0300, Gleb Natapov wrote:
> > I do not remember this been an issue when uio_generic was accepted
> > into the kernel. The reason was because it meant to be accessible by root
> > only.
>
> No
This patch adds the bindings for Altera PCIe host controller driver and
Altera PCIe MSI driver.
Signed-off-by: Ley Foon Tan
---
.../devicetree/bindings/pci/altera-pcie-msi.txt| 28 +
.../devicetree/bindings/pci/altera-pcie.txt| 49 ++
2 files changed,
Signed-off-by: Ley Foon Tan
---
MAINTAINERS | 16
1 file changed, 16 insertions(+)
diff --git a/MAINTAINERS b/MAINTAINERS
index 9f6685f..482de0b 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
@@ -7943,6 +7943,14 @@ F: include/linux/pci*
F: arch/x86/pci/
F:
This patch adds the Altera PCIe host controller driver.
Signed-off-by: Ley Foon Tan
Reviewed-by: Marc Zyngier
---
drivers/pci/host/Kconfig | 7 +
drivers/pci/host/Makefile | 1 +
drivers/pci/host/pcie-altera.c | 588 +
3 files changed, 596
On 10/08/2015 12:16 PM, Michael S. Tsirkin wrote:
On Thu, Oct 08, 2015 at 11:46:30AM +0300, Avi Kivity wrote:
On 10/08/2015 10:32 AM, Michael S. Tsirkin wrote:
On Thu, Oct 08, 2015 at 08:33:45AM +0300, Avi Kivity wrote:
It is good practice to defend against root oopsing the kernel, but in
Include asm-generic/msi.h to support CONFIG_GENERIC_MSI_IRQ_DOMAIN.
This to fix compilation error:
"include/linux/msi.h:123:21: fatal error: asm/msi.h:
No such file or directory"
Signed-off-by: Ley Foon Tan
---
arch/arm/include/asm/Kbuild | 1 +
1 file changed, 1 insertion(+)
diff --git
Signed-off-by: Ley Foon Tan
---
include/linux/pci_ids.h | 2 ++
1 file changed, 2 insertions(+)
diff --git a/include/linux/pci_ids.h b/include/linux/pci_ids.h
index d9ba49c..08e4462 100644
--- a/include/linux/pci_ids.h
+++ b/include/linux/pci_ids.h
@@ -1550,6 +1550,8 @@
#define
This is the 8th version of patch set to add support for Altera PCIe host
controller with MSI feature on Altera FPGA device families. This patchset
mainly resolve comments from Rob Herring and Marc Zyngier in v7 and minor fix.
This patchset is based on v4.3-rc3.
v7->v8 changes:
-
On 08/10/15 01:14, Steve Muckle wrote:
> On 08/25/2015 03:45 AM, Juri Lelli wrote:
>> But, it is true that if the above events happened the other way around
>> (we trigger an update after load balancing and a new task arrives), we
>> may miss the opportunity to jump to max with the new task. In my
On Thu, Oct 08, 2015 at 05:18:14PM +0800, yalin wang wrote:
> is it also possible to implement it on ARM platforms?
> ARM64 platform don’t have HIGH_MEM zone .
> but ARM platform have .
> i remember boot loader must put init rd into low memory region,
> so if some boot loader put init rd into
On Wed, Oct 07, 2015 at 06:12:42PM -0700, Andrew Duggan wrote:
> I can confirm that it is working on the Dell XPS 13 and the buttonpad
> property is set correctly. However, I also tried it on an older non
> production precision touchpad and it didn't work. It reports that it fails
> to fetch
On 10/07/2015 12:43 PM, Tetsuo Handa wrote:
Vlastimil Babka wrote:
On 5.10.2015 16:44, Michal Hocko wrote:
So I can see basically only few ways out of this deadlock situation.
Either we face the reality and allow small allocations (withtout
__GFP_NOFAIL) to fail after all attempts to reclaim
Hi David,
On 10/07/2015 09:41 PM, David Ahern wrote:
On 10/6/15 8:25 PM, Hemant Kumar wrote:
@@ -358,7 +357,12 @@ static bool handle_end_event(struct
perf_kvm_stat *kvm,
time_diff = sample->time - time_begin;
if (kvm->duration && time_diff > kvm->duration) {
-char
On Thu, Oct 08, 2015 at 10:52:05AM +0200, Arnd Bergmann wrote:
> On Thursday 08 October 2015 08:23:44 Miroslav Lichvar wrote:
> > The difference is that with the one-week step the kernel and userspace
> > still agree on the current time and it is always valid from the kernel
> > point of view,
On Thu, Oct 08, 2015 at 11:01:48AM +0200, Alexandre Belloni wrote:
> On 05/10/2015 at 18:00:52 +0100, Andre Przywara wrote :
> > Turning on KVM and LPAE support on top of a multi_v7_defconfig will
> > produce a compiler warning in the Atmel serial driver:
> > drivers/tty/serial/atmel_serial.c: In
On Thu, Oct 08, 2015 at 10:59:10AM +0300, Gleb Natapov wrote:
> I do not remember this been an issue when uio_generic was accepted
> into the kernel. The reason was because it meant to be accessible by root
> only.
No - because it does not need bus mastering. So it can be used safely
with some
On Thu, Oct 01, 2015 at 12:02:41AM +, Bondarenko, Anton wrote:
> >> @@ -201,9 +202,8 @@ static bool spi_imx_can_dma(struct spi_master *master,
> >> struct spi_device *spi,
> >> {
> >>struct spi_imx_data *spi_imx = spi_master_get_devdata(master);
> >>
> >> - if (spi_imx->dma_is_inited
Hello,
On 10/08/2015 08:23 AM, Marek Szyprowski wrote:
> Hello,
>
> On 2015-10-08 08:02, Krzysztof Kozlowski wrote:
>> On 07.10.2015 23:26, Marek Szyprowski wrote:
>>> Hello,
>>>
>>> On 2015-10-07 02:30, Krzysztof Kozlowski wrote:
Introduction
This patchset tries to
On Thu, Oct 08, 2015 at 03:55:12PM +0800, Chen Feng wrote:
> Signed-off-by: Chen Feng
> Signed-off-by: Yu Dongbin
I can't take a patch with no changelog entry at all, sorry. You are
going to have to at least explain what this driver is, what it does, and
what hardware it supports.
thanks,
--
On 03/09/15 00:23, Mikulas Patocka wrote:
> [ I sent this some times ago, but didn't get any response ]
>
>
> Nvidia cards have a BIOS function 0x4f14 that allows to set flat panel
> scaling. This patch adds a module parameter "scaling" that uses this
> function to set the scaling. By default,
On 08/10/15 06:05, Juergen Gross wrote:
> On 10/07/2015 10:21 PM, Konrad Rzeszutek Wilk wrote:
>> Hey,
>>
>> I was running some tools in which we would heavily do rescheduling
>> of events - and realized to my surprise that the event channels (and
>> the hypercall) would slow things down. If I
On Thu, Oct 01, 2015 at 12:16:49AM +, Bondarenko, Anton wrote:
> On 30.09.2015 10:42, Robin Gong wrote:
> > On Fri, Sep 25, 2015 at 07:57:12PM +0200, Anton Bondarenko wrote:
> >> @@ -370,8 +374,12 @@ static int __maybe_unused mx51_ecspi_config(struct
> >> spi_imx_data *spi_imx,
> >>if
On 23/09/15 20:57, Denys Vlasenko wrote:
> With this .config: http://busybox.net/~vda/kernel_config,
> after uninlining these functions have sizes and callsite counts
> as follows:
>
> __OUTPLLP: 61 bytes, 12 callsites
> __INPLL: 79 bytes, 150 callsites
> __OUTPLL: 82 bytes, 138 callsites
>
On Thu, 2015-10-08 at 10:37 +0200, Arnd Bergmann wrote:
> On Thursday 08 October 2015 16:46:27 Krzysztof Kozlowski wrote:
> > On 08.10.2015 16:41, Arnd Bergmann wrote:
> > > On Thursday 08 October 2015 03:48:36 Anand Moon wrote:
> > > > diff --git a/arch/arm/configs/exynos_defconfig
> > > >
Rob,
On 15-09-15, 08:17, Viresh Kumar wrote:
> On 14-09-15, 15:22, Rob Herring wrote:
> > What if we have a 2nd device and supply rail? For example, what if the
> > L2$ has a separate rail from the cores but is linked to the OPPs.
>
> Right, so that is the case with the Mediatek SoC as well,
This patch modifies the id and name of external connector with the
additional prefix to clarify both attribute and meaning of external
connector as following:
- EXTCON_CHG_* mean the charger connector.
- EXTCON_JACK_* mean the jack connector.
- EXTCON_DISP_* mean the display port connector.
Rob Herring writes:
> On Wed, Oct 7, 2015 at 11:47 AM, Måns Rullgård wrote:
>> Mark Rutland writes:
>>
>>> On Wed, Oct 07, 2015 at 04:37:13PM +0100, Mans Rullgard wrote:
This adds a DT binding for a generic mmio clocksource as implemented
by clocksource_mmio_init().
On Wed, 2015-10-07 at 23:09 +0530, Viresh Kumar wrote:
[...]
> And why not fix it properly by doing this:
>
> diff --git a/drivers/cpufreq/arm_big_little.c
> b/drivers/cpufreq/arm_big_little.c
> index f1e42f8ce0fc..5b36657a76d6 100644
> --- a/drivers/cpufreq/arm_big_little.c
> +++
On 02/10/15 00:22, Ondrej Zary wrote:
> Fire GL2 AGP has GXT6000P and is a x86 card but the gxt4500 driver is
> currently limited to PPC.
>
> This patch series makes the driver work on x86, fixes some color problems
> and enhances performance.
>
Thanks, applying for 4.4.
Tomi
Hi Matthew,
On Thu, Oct 08, 2015 at 03:07:34AM +0100, Matthew Minter wrote:
> On Wednesday 07 October 2015 18:08:47 Bjorn Helgaas wrote:
[...]
> Yes, I had been working on this last year, and got a patchset that was tested
> on arm, x86 (and amd64), and slightly tested on powerpc. However I
On 10/08/2015 11:32 AM, Michael S. Tsirkin wrote:
On Thu, Oct 08, 2015 at 08:33:45AM +0300, Avi Kivity wrote:
On 08/10/15 00:05, Michael S. Tsirkin wrote:
On Wed, Oct 07, 2015 at 07:39:16PM +0300, Avi Kivity wrote:
That's what I thought as well, but apparently adding msix support to the
Thu, Oct 08, 2015 at 11:04:48AM CEST, l...@intel.com wrote:
>Hi Vivien,
>
>[auto build test ERROR on net-next/master -- if it's inappropriate base,
>please ignore]
>
>config: arm64-allyesconfig (attached as .config)
>reproduce:
>wget
>
> On Oct 8, 2015, at 16:49, Christoffer Dall
> wrote:
>
> On Tue, Oct 06, 2015 at 01:16:52PM -0400, Mark Salter wrote:
>> On Tue, 2015-10-06 at 18:11 +0100, Mark Rutland wrote:
>>> On Tue, Sep 08, 2015 at 12:31:13PM +0100, Mark Rutland wrote:
Hi Mark,
On Mon, Aug 17, 2015 at
On Thu, Oct 08, 2015 at 11:46:30AM +0300, Avi Kivity wrote:
>
>
> On 10/08/2015 10:32 AM, Michael S. Tsirkin wrote:
> >On Thu, Oct 08, 2015 at 08:33:45AM +0300, Avi Kivity wrote:
> >>It is good practice to defend against root oopsing the kernel, but in some
> >>cases it cannot be achieved.
>
Mark Rutland writes:
>> >> +- clocks: phandle to the source clock
>> >
>> > Is the frequency expected to be exactly the source clock frequency? I
>> > imagine it's possible for there to be a divisor.
>>
>> There could of course be, though there isn't in the hardware I'm dealing
>> with. Is
On 2015/9/28 17:44, Leizhen (ThunderTown) wrote:
>> >
>>> >> --drivers/char/Kconfig--
>>> >> if RTC_LIB=n
>>> >>
>>> >> config RTC
>>> >> tristate "Enhanced Real Time Clock Support (legacy PC RTC driver)"
>>> >>
>>> >> ...
>>> >>
>>> >> config EFI_RTC
>>> >>
The DMA engine supports memory copy, RAID5 XOR, RAID6 PQ, and other
computations. But the bandwidth of the entire DMA engine is shared
among all channels. This patch re-configures operations availability
such that one can achieve maximum performance for XOR and PQ
computation by removing the
Hi Vivien,
[auto build test ERROR on net-next/master -- if it's inappropriate base, please
ignore]
config: arm64-allyesconfig (attached as .config)
reproduce:
wget
https://git.kernel.org/cgit/linux/kernel/git/wfg/lkp-tests.git/plain/sbin/make.cross
-O ~/bin/make.cross
chmod +x
On Wed, Oct 07, 2015 at 09:26:53AM -0700, Paul E. McKenney wrote:
> On Wed, Oct 07, 2015 at 04:26:27PM +0200, Peter Zijlstra wrote:
> Indeed, that approach looks better than moving rcu_note_context_switch(),
> which probably results in deadlocks. I will update my patch accordingly.
Yeah,
On Wed 07-10-15 15:34:08, Andrew Morton wrote:
> (cc Jan)
>
> On Wed, 7 Oct 2015 19:02:22 +0200 Vitaly Kuznetsov
> wrote:
>
> > In some cases we may end up killing the CPU holding the console lock
> > while still having valuable data in logbuf. E.g. I'm observing the
> > following:
> > - A
On 05/10/2015 at 18:00:52 +0100, Andre Przywara wrote :
> Turning on KVM and LPAE support on top of a multi_v7_defconfig will
> produce a compiler warning in the Atmel serial driver:
> drivers/tty/serial/atmel_serial.c: In function 'atmel_verify_port':
> drivers/tty/serial/atmel_serial.c:2299:6:
On Wed, Oct 07, 2015 at 09:14:45AM -0700, Paul E. McKenney wrote:
> On Wed, Oct 07, 2015 at 03:49:29PM +0200, Peter Zijlstra wrote:
> > On Wed, Oct 07, 2015 at 03:43:11PM +0200, Peter Zijlstra wrote:
> > > On Tue, Oct 06, 2015 at 09:29:23AM -0700, Paul E. McKenney wrote:
> > > > @@ -167,42 +307,18
On Wed, Oct 07, 2015 at 09:17:44AM -0700, tip-bot for Andy Lutomirski wrote:
> Commit-ID: 72f924783b8a87e4454516520ffb5f35e4930371
> Gitweb: http://git.kernel.org/tip/72f924783b8a87e4454516520ffb5f35e4930371
> Author: Andy Lutomirski
> AuthorDate: Mon, 5 Oct 2015 17:47:54 -0700
>
On Thu, Oct 8, 2015 at 2:23 PM, Arnd Bergmann wrote:
> On Thursday 08 October 2015 13:55:16 Rameshwar Prasad Sahu wrote:
>> The DMA engine supports memory copy, RAID5 XOR, RAID6 PQ, and other
>> computations. But the bandwidth of the entire DMA engine is shared
>> among all channels. This patch
On Wed, Oct 07, 2015 at 03:05:27PM +0100, Mark Brown wrote:
> On Wed, Oct 07, 2015 at 05:52:12PM +0530, Sudip Mukherjee wrote:
> > We were getting build warning about "Section mismatch".
> > dmi_platform_intel_broadwell is being referenced from the probe function
> > rt5645_i2c_probe(), but
On Thursday 08 October 2015 13:55:16 Rameshwar Prasad Sahu wrote:
> The DMA engine supports memory copy, RAID5 XOR, RAID6 PQ, and other
> computations. But the bandwidth of the entire DMA engine is shared
> among all channels. This patch re-configures operations availability
> such that one can
On Thursday 08 October 2015 08:23:44 Miroslav Lichvar wrote:
> On Wed, Oct 07, 2015 at 05:10:34PM +0200, Arnd Bergmann wrote:
> > On Wednesday 07 October 2015 16:23:44 Miroslav Lichvar wrote:
> > > Without the limit added by this patch make will go nuts just one week
> > > later when the 32-bit
On Thu, Oct 08, 2015 at 11:32:50AM +0300, Michael S. Tsirkin wrote:
> On Thu, Oct 08, 2015 at 08:33:45AM +0300, Avi Kivity wrote:
> > On 08/10/15 00:05, Michael S. Tsirkin wrote:
> > >On Wed, Oct 07, 2015 at 07:39:16PM +0300, Avi Kivity wrote:
> > >>That's what I thought as well, but apparently
* Prarit Bhargava wrote:
> re-ping on this. Just making sure this wasn't dropped on the floor.
So I didn't apply it back when I saw your patch because I didn't see where you
addressed/analyzed the second paragraph of hpa's review:
"The downside with set is that it only sets a single byte,
On Tue, Oct 06, 2015 at 01:16:52PM -0400, Mark Salter wrote:
> On Tue, 2015-10-06 at 18:11 +0100, Mark Rutland wrote:
> > On Tue, Sep 08, 2015 at 12:31:13PM +0100, Mark Rutland wrote:
> > > Hi Mark,
> > >
> > > On Mon, Aug 17, 2015 at 06:01:06PM +0100, Mark Salter wrote:
> > > > The use of mem=
* Linus Torvalds wrote:
> So I really refuse to worry about the snprintf() family of functions wrt this
> race. I don't think it was hugely important for strlcpy() either - more of a
> "quality of implementation" issue rather than anything fundamental - but for
> snprintf and friends it's an
On Wed, Oct 07, 2015 at 10:55:30AM +0300, Vlad Zolotarov wrote:
> * not safe - UIO
That's wrong. UIO (in particular uio_pci_generic) can be used
safely in many ways, for example with any device not doing DMA. I
wouldn't put it upstream otherwise.
Make your driver work in such a way that it can
On 10/08/2015 10:32 AM, Michael S. Tsirkin wrote:
On Thu, Oct 08, 2015 at 08:33:45AM +0300, Avi Kivity wrote:
It is good practice to defend against root oopsing the kernel, but in some
cases it cannot be achieved.
Absolutely. That's one of the issues with these patches. They don't even
try
This patch generates prologue for each 'struct probe_trace_event' for
fetching arguments for BPF programs.
After bpf__probe(), iterate over each programs to check whether
prologue is required. If none of 'struct perf_probe_event' a program
will attach to has at least one argument, simply skip
This is the final patch which makes basic BPF filter work. After
applying this patch, users are allowed to use BPF filter like:
# perf record --event ./hello_world.o ls
A bpf_fd field is appended to 'struct evsel', and setup during the
callback function add_bpf_event() for each
This patch replaces the original toy BPF program with previous introduced
bpf-script-example.c. Dynamically embedded it into 'llvm-src.c'.
The newly introduced BPF program attaches a BPF program at
'sys_epoll_pwait()', and collect half samples from it. perf itself never
use that syscall, so
On October 07, 2015 17:22, Rob Herring wrote:
> > +- dlg,micbias1-lvl : Voltage (mV) for Mic Bias 1
> > + [<1600>, <2200>, <2500>, <3000>]
> > +- dlg,micbias2-lvl : Voltage (mV) for Mic Bias 2
> > + [<1600>, <2200>, <2500>, <3000>]
>
> Please append the units (-microvolt).
Given
This patch provides infrastructure for passing source files to --event
directly using:
# perf record --event bpf-file.c command
This patch does following works:
1) Allow passing '.c' file to '--event'. parse_events_load_bpf() is
expanded to allow caller tell it whether the passed file is
901 - 1000 of 2210 matches
Mail list logo
