On Fri, 18 Nov 2016, Tan Jui Nee wrote:
> This patch follows the example of mfd/wm831x to rename the driver
> from "lpc_ich" to "lpc_ich_core".
>
> Signed-off-by: Tan Jui Nee
> Reviewed-by: Mika Westerberg
> ---
> Changes in V11:
> - No change
>
> Changes in V10:
> - No change
>
>
On Sun, Nov 20, 2016 at 09:21:51AM +0100, Sergio Paracuellos wrote:
> On Sat, Nov 19, 2016 at 2:20 PM, Greg KH wrote:
> > On Fri, Nov 18, 2016 at 06:57:18PM +0100, Sergio Paracuellos wrote:
> >> Remove incorrect __iomem annotation.
> >>
> >> This patch fix the following sparse warnings in slicoss
Mark, please see below:
On Sat, 19 Nov 2016, Robert Jarzmik wrote:
> Lee Jones writes:
>
> >> +#define WM9705_VENDOR_ID 0x574d4c05
> >> +#define WM9712_VENDOR_ID 0x574d4c12
> >> +#define WM9713_VENDOR_ID 0x574d4c13
> >> +#define WM97xx_VENDOR_ID_MASK 0x
> >
> > These are probably better
On 17-11-16, 10:48, Viresh Kumar wrote:
> From: Steve Muckle
>
> The rate-limit tunable in the schedutil governor applies to transitions
> to both lower and higher frequencies. On several platforms it is not the
> ideal tunable though, as it is difficult to get best power/performance
> figures us
On 21/11/2016 10:03, Boris Brezillon wrote:
> The nand_to_mtd() helper is here to hide internal mtd_info <-> nand_chip
> association and ease future refactors.
>
> Make use of this helper instead of directly accessing chip->mtd.
>
> Signed-off-by: Boris Brezillon
> ---
> drivers/mtd/nand/tango
Since commit e647b532275b ("ACPI: Add early device probing
infrastructure") the kernel has gained the infrastructure that allows
adding linker script section entries to execute ACPI driver callbacks
(ie probe routines) for all subsystems that register a table entry
in the respective kernel section
The of_iommu_{set/get}_ops() API is used to associate a device
tree node with a specific set of IOMMU operations. The same
kernel interface is required on systems booting with ACPI, where
devices are not associated with a device tree node, therefore
the interface requires generalization.
The struc
On DT based systems, the of_dma_configure() API implements DMA
configuration for a given device. On ACPI systems an API equivalent to
of_dma_configure() is missing which implies that it is currently not
possible to set-up DMA operations for devices through the ACPI generic
kernel layer.
This patch
In ACPI based systems, in order to be able to create platform
devices and initialize them for ARM SMMU components, the IORT
kernel implementation requires a set of static functions to be
used by the IORT kernel layer to configure platform devices for
ARM SMMU components.
Add static configuration f
Current ARM SMMUv3 probe functions intermingle HW and DT probing in the
initialization functions to detect and programme the ARM SMMU v3 driver
features. In order to allow probing the ARM SMMUv3 with other firmwares
than DT, this patch splits the ARM SMMUv3 init functions into DT and HW
specific po
In ACPI bases systems, in order to be able to create platform
devices and initialize them for ARM SMMU v3 components, the IORT
kernel implementation requires a set of static functions to be
used by the IORT kernel layer to configure platform devices for
ARM SMMU v3 components.
Add static configura
Hi Andy,
On Fri, 2016-11-18 at 21:26 +0200, Andy Shevchenko wrote:
> On Fri, 2016-11-18 at 22:12 +0300, Eugeniy Paltsev wrote:
> >
> > It wasn't possible to enable some features like
> > memory-to-memory transfers or multi block transfers via DT.
> > It is fixed by these patches.
>
> First of al
Current ARM SMMU probe functions intermingle HW and DT probing
in the initialization functions to detect and programme the ARM SMMU
driver features. In order to allow probing the ARM SMMU with other
firmwares than DT, this patch splits the ARM SMMU init functions into
DT and HW specific portions so
DT based systems have a generic kernel API to configure IOMMUs
for devices (ie of_iommu_configure()).
On ARM based ACPI systems, the of_iommu_configure() equivalent can
be implemented atop ACPI IORT kernel API, with the corresponding
functions to map device identifiers to IOMMUs and retrieve the
c
Current ARM SMMU driver rely on the struct device.of_node pointer for
device look-up and iommu_ops retrieval.
In preparation for ACPI probing enablement, convert the driver to use
the struct device.fwnode member for device and iommu_ops look-up so that
the driver infrastructure can be used also on
Current ARM SMMU v3 driver rely on the struct device.of_node pointer for
device look-up and iommu_ops retrieval.
In preparation for ACPI probing enablement, convert the driver to use
the struct device.fwnode member for device and iommu_ops look-up so that
the driver infrastructure can be used also
In ARM ACPI systems, IOMMU components are specified through static
IORT table entries. In order to create platform devices for the
corresponding ARM SMMU components, IORT kernel code should be made
able to parse IORT table entries and create platform devices
dynamically.
This patch adds the generi
The current IORT id mapping API requires components to provide
an input requester ID (a Bus-Device-Function (BDF) identifier for
PCI devices) to translate an input identifier to an output
identifier through an IORT range mapping.
Named components do not have an identifiable source ID therefore
the
Device drivers (eg ARM SMMU) need to know if a specific component
is part of the IORT table, so that kernel data structures are not
initialized at initcalls time if the respective component is not
part of the IORT table.
To this end, this patch adds a trivial function that allows detecting
if a gi
IORT tables provide data that allow the kernel to carry out
device ID mappings between endpoints and system components
(eg interrupt controllers, IOMMUs). When the mapping for a
given device ID is carried out, the translation mechanism
is done on a per-subsystem basis rather than a component
subtyp
This patch series is v9 of a previous posting:
https://lkml.org/lkml/2016/11/16/386
v8 -> v9
- Updated bypass flag handling in ARM SMMU v3 according to
reviews
- Removed SMMUv1/v2 configuration interrupt handling
- Rebased against v4.9-rc5
- Updated tags
On systems booting with a device tree, every struct device is associated
with a struct device_node, that provides its DT firmware representation.
The device node can be used in generic kernel contexts (eg IRQ
translation, IOMMU streamid mapping), to retrieve the properties
associated with the devic
The ACPI IORT table provide entries for IOMMU (aka SMMU in ARM world)
components that allow creating the kernel data structures required to
probe and initialize the IOMMU devices.
This patch provides support in the IORT kernel code to register IOMMU
components and their respective fwnode.
Signed-
On Fri, Nov 18, 2016 at 4:37 PM, Amir Goldstein wrote:
> Found one typo and one bug in error that can cause crash on
> dput(ERR_PTR(err)):
Thanks.
Fixes force pushed to overlayfs-next.
Also pushed the redirect patches to overlayfs-next, as they seem to
have matured enough.
Thanks,
Miklos
Hi Jon,
I will update the patch per your comment.
Here is answer for some of the query.
Thanks,
Laxman
On Tuesday 15 November 2016 08:37 PM, Jon Hunter wrote:
On 09/11/16 13:06, Laxman Dewangan wrote:
+/**
+ * Macro for 1.8V, keep 200mV as tolerance for deciding that
+ * IO pads should be se
On Thu, Nov 21, 2016 at 03:15 PM +0800, Krzeminski, Marcin (Nokia - PL/Wroclaw)
wrote:
> > -Original Message-
> > From: Yao Yuan [mailto:yao.y...@nxp.com]
> > Sent: Monday, November 21, 2016 7:28 AM
> > To: Krzeminski, Marcin (Nokia - PL/Wroclaw)
> > ; Han Xu
> > Cc: David Woodhouse ; lin
* Frederic Weisbecker wrote:
> > But I am still not happy about the approach. What is the compelling reason
> > for
> > this change except for the "but it looks ugly"?
>
> The diffstat (600 lines removed). Also the fact that we have all these
> workarounds in the core code just for the speci
Not only media documents may have images. So, move the
rules for building images from graphviz and from SVG to
the Documentation makefile.
With this change, if some Documentation subdir "foo"
can now specify that he has SVG and/or DOT source images
that are included inside the documentation.
All
Hi Mark,
On 19 November 2016 at 03:30, Mark Rutland wrote:
> On Wed, Nov 16, 2016 at 09:48:59PM +0800, fu@linaro.org wrote:
>> From: Fu Wei
>>
>> The patch refactor original arch_timer_uses_ppi init code:
>> (1) Extract a subfunction: arch_timer_uses_ppi_init
>> (2) Use the new subfunction i
On Mon, Nov 21, 2016 at 01:02:25AM -0800, Paul E. McKenney wrote:
> On Mon, Nov 21, 2016 at 01:53:43AM +0100, Jiri Olsa wrote:
> >
> > it got away with attached change.. but this rcu logic
> > is far beyond me, so it's just wild guess.. ;-)
>
> If in idle, the _rcuidle() is needed, so:
Well, the
On Mon, Nov 21, 2016 at 10:34:25AM +0100, Jiri Olsa wrote:
> On Mon, Nov 21, 2016 at 10:28:50AM +0100, Peter Zijlstra wrote:
> > I think I prefer something like the below, that only annotates the one
> > RDMSR in question, instead of all of them.
>
> I was wondering about that, but haven't found
* Dave Hansen wrote:
> On 11/16/2016 08:56 AM, Yu-cheng Yu wrote:
> > Robert O'Callahan reported that after an execve PTRACE_GETREGSET
> > NT_X86_XSTATE continues to return the pre-exec register values
> > until the exec'ed task modifies FPU state. The test code is at
> > https://bugzilla.redha
On Fri, Nov 18, 2016 at 10:15:42PM -0600, Wei Huang wrote:
> From: Christopher Covington
>
> Calculate the numbers of cycles per instruction (CPI) implied by ARM
> PMU cycle counter values. The code includes a strict checking facility
> intended for the -icount option in TCG mode in the configura
On Mon, Nov 21, 2016 at 10:02:23AM +0100, Peter Zijlstra wrote:
> On Mon, Nov 21, 2016 at 04:44:28PM +0800, Boqun Feng wrote:
> > On Fri, Nov 18, 2016 at 12:37:18PM +0100, Peter Zijlstra wrote:
> > [snip]
> > > +
> > > +/*
> > > + * Similar to atomic_inc(), will saturate at UINT_MAX and WARN.
> > >
On Mon, Nov 21, 2016 at 10:28:50AM +0100, Peter Zijlstra wrote:
> On Mon, Nov 21, 2016 at 01:53:43AM +0100, Jiri Olsa wrote:
> > hi,
> > Jan hit following output when msr tracepoints are enabled on amd server:
> >
> > [ 91.585653] ===
> > [ 91.589840] [ INFO: suspic
On Wednesday 16 November 2016 12:18 AM, Jon Hunter wrote:
On 09/11/16 13:06, Laxman Dewangan wrote:
+NVIDIA Tegra124 and later SoCs support the multi-voltage level and
+low power state of some of its IO pads. When IO interface are not
+used then IO pads can be configure in low power state to re
diff --git a/Makefile b/Makefile
index c1519ab85258..7cf2b4985703 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 8
-SUBLEVEL = 9
+SUBLEVEL = 10
EXTRAVERSION =
NAME = Psychotic Stoned Sheep
diff --git a/arch/sparc/include/asm/uaccess_64.h
b/arch/sparc/include/as
diff --git a/Makefile b/Makefile
index a513c045c8de..30924aabf1b4 100644
--- a/Makefile
+++ b/Makefile
@@ -1,6 +1,6 @@
VERSION = 4
PATCHLEVEL = 4
-SUBLEVEL = 33
+SUBLEVEL = 34
EXTRAVERSION =
NAME = Blurry Fish Butt
diff --git a/arch/sparc/include/asm/mmu_64.h b/arch/sparc/include/asm/mmu_64.h
I'm announcing the release of the 4.4.34 kernel.
All users of the 4.4 kernel series must upgrade.
The updated 4.4.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.4.y
and can be browsed at the normal kernel.org git web browser:
On Mon, Nov 21, 2016 at 01:53:43AM +0100, Jiri Olsa wrote:
> hi,
> Jan hit following output when msr tracepoints are enabled on amd server:
>
> [ 91.585653] ===
> [ 91.589840] [ INFO: suspicious RCU usage. ]
> [ 91.594025] 4.9.0-rc1+ #1 Not tainted
> [ 91.597691
I'm announcing the release of the 4.8.10 kernel.
All users of the 4.8 kernel series must upgrade.
The updated 4.8.y git tree can be found at:
git://git.kernel.org/pub/scm/linux/kernel/git/stable/linux-stable.git
linux-4.8.y
and can be browsed at the normal kernel.org git web browser:
On Mon, Nov 21, 2016 at 03:01:57PM +0900, Tomasz Figa wrote:
> One thing to correct here is that the typical clock is PCLK, which is
> derived from one of the PLLs and AFAIR is between 33-66 MHz on
> s3c24xx. Technically you can drive the PWM block from an external
> clock (12 MHz for some board-fi
On 21/11/16 06:01, Tomasz Figa wrote:
2016-11-18 17:46 GMT+09:00 Arnd Bergmann :
Maybe add a paragraph about the specific problem:
"On s3c24xx, the PWM counter is only 16 bit wide, and with the
typical 12MHz input clock that overflows every 5.5ms. This works
with HZ=200 or higher but not with H
On Fri, Nov 18, 2016 at 10:15:41PM -0600, Wei Huang wrote:
> From: Christopher Covington
>
> Ensure that reads of the PMCCNTR_EL0 are monotonically increasing,
> even for the smallest delta of two subsequent reads.
>
> Signed-off-by: Christopher Covington
> Signed-off-by: Wei Huang
> ---
> ar
The indent code blocks of the else statements were unnecessary
and are better written without them.
Signed-off-by: Shiva Kerdel
---
drivers/staging/rtl8712/rtl871x_ioctl_linux.c | 4 ++--
drivers/staging/rtl8712/rtl871x_mlme.c| 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
di
Hi Bjorn
Many thanks for your review
> -Original Message-
> From: linux-pci-ow...@vger.kernel.org [mailto:linux-pci-
> ow...@vger.kernel.org] On Behalf Of Bjorn Helgaas
> Sent: 18 November 2016 17:08
> To: liudongdong (C)
> Cc: a...@arndb.de; raf...@kernel.org; lorenzo.pieral...@arm.com;
On Sun, Nov 20, 2016 at 3:58 AM, David Lechner wrote:
> On 11/14/2016 08:40 AM, ahas...@baylibre.com wrote:
>>
>> Instead of global variables, use the extra_priv_size of
>> the ohci driver.
>>
>> We cannot yet move the ocic mask because this is used on
>> the interrupt handler which is registerded
On Mon, Nov 21, 2016 at 08:59:06AM +, Ben Dooks wrote:
> On 21/11/16 06:01, Tomasz Figa wrote:
> >2016-11-18 17:46 GMT+09:00 Arnd Bergmann :
> >>Maybe add a paragraph about the specific problem:
> >>
> >>"On s3c24xx, the PWM counter is only 16 bit wide, and with the
> >>typical 12MHz input cloc
Hi,
I updated my config and set CONFIG_WDAT_WDT=y, got this:
drivers/built-in.o: In function `wdat_wdt_probe':
/home/vegard/linux/drivers/watchdog/wdat_wdt.c:444: undefined
reference to `devm_watchdog_register_device'
Makefile:962: recipe for target 'vmlinux' failed
make: *** [vmlinux] Error 1
L
tree: https://git.kernel.org/pub/scm/linux/kernel/git/tip/tip.git ras/core
head: c698decd333b67b3814682cf65e9069e6db2ecd1
commit: c698decd333b67b3814682cf65e9069e6db2ecd1 [6/6] x86/mce/AMD: Add system
physical address translation for AMD Fam17h
config: i386-tinyconfig (attached as .config)
com
Commit-ID: ed3db40f00be77b8aa407885e35513c7a517e65e
Gitweb: http://git.kernel.org/tip/ed3db40f00be77b8aa407885e35513c7a517e65e
Author: Yazen Ghannam
AuthorDate: Thu, 17 Nov 2016 17:57:27 -0500
Committer: Ingo Molnar
CommitDate: Mon, 21 Nov 2016 10:00:22 +0100
x86/mce/AMD: Add system ph
The nand_to_mtd() helper is here to hide internal mtd_info <-> nand_chip
association and ease future refactors.
Make use of this helper instead of directly accessing chip->mtd.
Signed-off-by: Boris Brezillon
---
drivers/mtd/nand/tango_nand.c | 25 -
1 file changed, 16 in
On Mon, Nov 21, 2016 at 01:53:43AM +0100, Jiri Olsa wrote:
> hi,
> Jan hit following output when msr tracepoints are enabled on amd server:
>
> [ 91.585653] ===
> [ 91.589840] [ INFO: suspicious RCU usage. ]
> [ 91.594025] 4.9.0-rc1+ #1 Not tainted
> [ 91.597691
On 21 November 2016 at 16:56, Thomas Gleixner wrote:
> On Mon, 21 Nov 2016, Baolin Wang wrote:
>> On 21 November 2016 at 16:13, Ingo Molnar wrote:
>> > Hm, there's a weirdness here: if freezer_delta != 0 when
>> > alarmtimer_suspend() is
>> > called then type might be '0', although it's not alar
On Mon, Nov 21, 2016 at 04:44:28PM +0800, Boqun Feng wrote:
> On Fri, Nov 18, 2016 at 12:37:18PM +0100, Peter Zijlstra wrote:
> [snip]
> > +
> > +/*
> > + * Similar to atomic_inc(), will saturate at UINT_MAX and WARN.
> > + *
> > + * Provides no memory ordering, it is assumed the caller already has
On Mon, 21 Nov 2016, Baolin Wang wrote:
> On 21 November 2016 at 16:13, Ingo Molnar wrote:
> > Hm, there's a weirdness here: if freezer_delta != 0 when
> > alarmtimer_suspend() is
> > called then type might be '0', although it's not alarm_bases[0] this value
> > is
> > picked up from.
> >
> > Wo
On 11/19/2016 01:17 PM, Jonathan Cameron wrote:
On 15/11/16 15:30, Fabrice Gasnier wrote:
Add core driver for STMicroelectronics STM32 ADC (Analog to Digital
Converter). STM32 ADC can be composed of up to 3 ADCs with shared
resources like clock prescaler, common interrupt line and analog
referen
* John Stultz wrote:
> From: Chris Metcalf
>
> The "cycles" argument should not be an absolute clocksource cycle
> value, as the implementation's arithmetic will overflow relatively
> easily with wide (64 bit) clocksource counters.
>
> For performance, the implementation is simple and fast, s
"Zhangjian (Bamvor)" writes:
> On 2016/11/18 18:31, Michael Ellerman wrote:
> >bamvor.zhangj...@huawei.com writes:
> >> From: Bamvor Jian Zhang
> >> Currently, kselftest use TEST_PROGS, TEST_PROGS_EXTENDED, TEST_FILES to
> >> indicate the default test program, extended test program and test f
Hi Bjorn
> -Original Message-
> From: Bjorn Helgaas [mailto:helg...@kernel.org]
> Sent: 18 November 2016 17:54
> To: Gabriele Paoloni
> Cc: Bjorn Helgaas; linux-...@vger.kernel.org; linux-
> a...@vger.kernel.org; linux-kernel@vger.kernel.org; linux-arm-
> ker...@lists.infradead.org; linaro
Hi,
I'm revisiting this since we're asked to do the same for iwlwifi.
On Thu, 2016-05-05 at 14:44 +0800, Wei-Ning Huang wrote:
> Recent new hardware has the ability to switch between tablet mode and
> clamshell mode. To optimize WiFi performance, we want to be able to
> use different power table
Commit-ID: ed68d7e9b9cfb64f3045ffbcb108df03c09a0f98
Gitweb: http://git.kernel.org/tip/ed68d7e9b9cfb64f3045ffbcb108df03c09a0f98
Author: Andy Lutomirski
AuthorDate: Sat, 19 Nov 2016 15:37:30 -0800
Committer: Ingo Molnar
CommitDate: Mon, 21 Nov 2016 09:04:32 +0100
x86/boot: Fail the boot
Commit-ID: a0faa9bf847c87d99a513a2d3e1940252e3a8d7d
Gitweb: http://git.kernel.org/tip/a0faa9bf847c87d99a513a2d3e1940252e3a8d7d
Author: Yazen Ghannam
AuthorDate: Thu, 17 Nov 2016 17:57:27 -0500
Committer: Thomas Gleixner
CommitDate: Mon, 21 Nov 2016 09:43:09 +0100
x86/mce/AMD: Add syste
Hi Ingo,
On 21 November 2016 at 16:13, Ingo Molnar wrote:
>
> * John Stultz wrote:
>
>> @@ -222,7 +226,7 @@ static int alarmtimer_suspend(struct device *dev)
>> ktime_t min, now;
>> unsigned long flags;
>> struct rtc_device *rtc;
>> - int i;
>> + int i, type = 0;
>>
Commit-ID: c698decd333b67b3814682cf65e9069e6db2ecd1
Gitweb: http://git.kernel.org/tip/c698decd333b67b3814682cf65e9069e6db2ecd1
Author: Yazen Ghannam
AuthorDate: Thu, 17 Nov 2016 17:57:27 -0500
Committer: Thomas Gleixner
CommitDate: Mon, 21 Nov 2016 09:38:59 +0100
x86/mce/AMD: Add syste
On Fri, Nov 18, 2016 at 12:37:18PM +0100, Peter Zijlstra wrote:
[snip]
> +
> +/*
> + * Similar to atomic_inc(), will saturate at UINT_MAX and WARN.
> + *
> + * Provides no memory ordering, it is assumed the caller already has a
> + * reference on the object, will WARN when this is not so.
> + */
>
Hi Rafał,
I tried your new usbport trigger in Linux 4.9 with little luck as can be seen in
the following output of the serial console.
root@wrt1900acs:/# cd /sys/class/leds/pca963x\:shelby\:white\:usb2/
root@wrt1900acs:/sys/devices/platform/soc/soc:internal-regs/f1011000.i2c/i2c-0/0-0068/led
On Sunday 20 November 2016 10:31 PM, David Lechner wrote:
> On 11/20/2016 06:59 AM, Sekhar Nori wrote:
>> On Saturday 19 November 2016 10:11 AM, David Lechner wrote:
>>> @@ -400,6 +401,9 @@ static int davinci_spi_of_setup(struct spi_device
>>> *spi)
>>> if (!of_property_read_u32(np, "ti
On Mon, Nov 21, 2016 at 08:48:26AM +0100, Ingo Molnar wrote:
>
> * Boqun Feng wrote:
>
> > > It also fails to decrement in the underflow case (which is fine, but not
> > > obvious from the comment). Same thing below.
> > >
> >
> > Maybe a table in the comment like the following helps?
> >
> >
On Sun, 20 Nov 2016, Eric Dumazet wrote:
> Another potential issue with CONFIG_VMAP_STACK is that we make no
> attempt to allocate 4 consecutive pages.
>
> Even if we have plenty of memory, 4 calls to alloc_page() are likely to
> give us 4 pages in completely different locations.
>
> Here I prin
On Sat, Nov 19, 2016 at 12:48:27PM -0600, Tom Lendacky wrote:
> Should I move this functionality into the sme_set_mem_* functions or
> remove the sme_set_mem_* functions and use the set_memory_* functions
> directly. The latter means calculating the number of pages, but makes
> it clear that this
* Thomas Gleixner wrote:
> On Fri, 18 Nov 2016, Ingo Molnar wrote:
> > * Kyle Huey wrote:
> > > + if (test_tsk_thread_flag(prev_p, TIF_NOCPUID) ^
> > > + test_tsk_thread_flag(next_p, TIF_NOCPUID)) {
> > > + set_cpuid_faulting(test_tsk_thread_flag(next_p, TIF_NOCPUID));
> > > + }
> >
On Sun, Nov 20, 2016 at 06:19:48PM -0800, Andy Lutomirski wrote:
>
> > Herbert, can you clarify this? The check seems rather bizarre --
> > you're doing an incomplete check for aliasing and skipping the whole
> > copy if the beginning aliases. In any event the stack *can't*
> > reasonably alias t
On 11/18/2016 11:48 PM, Jérôme Glisse wrote:
> When a ZONE_DEVICE page refcount reach 1 it means it is free and nobody
> is holding a reference on it (only device to which the memory belong do).
> Add a callback and call it when that happen so device driver can implement
> their own free page manag
Hi Rafael
Many Thanks for your review.
在 2016/11/19 6:00, Rafael J. Wysocki 写道:
On Fri, Nov 18, 2016 at 10:22 AM, Dongdong Liu wrote:
The acpi_get_rc_resources() is used to get the RC register address that can
not be described in MCFG. It takes the _HID&segment to look for and outputs
the RC
On Sun, 20 Nov 2016, Peter Zijlstra wrote:
> On Sat, Nov 19, 2016 at 01:47:37PM -, Thomas Gleixner wrote:
> > When entering idle, it's a good oportunity to verify that the TSC_ADJUST
> > MSR has not been tampered with (BIOS hiding SMM cycles). If tampering is
> > detected, emit a warning and re
On 11/18/2016 11:48 PM, Jérôme Glisse wrote:
> Catch page from ZONE_DEVICE in free_hot_cold_page(). This should never
> happen as ZONE_DEVICE page must always have an elevated refcount.
>
> This is to catch refcounting issues in a sane way for ZONE_DEVICE pages.
>
> Signed-off-by: Jérôme Glisse
> On Fri, Nov 18, 2016 at 05:33:35PM +, Reshetova, Elena wrote:
> > On Thu, Nov 17, 2016 at 09:53:42AM +0100, Peter Zijlstra wrote:
> > > On Wed, Nov 16, 2016 at 12:08:52PM -0800, Alexei Starovoitov wrote:
> > >
> > > > I prefer to avoid 'fixing' things that are not broken.
> > > > Note, prog->
* John Stultz wrote:
> +static int pm_trace_notify(struct notifier_block *nb,
> + unsigned long mode, void *_unused)
> +{
> + switch (mode) {
> + case PM_POST_HIBERNATION:
> + case PM_POST_SUSPEND:
> + if (pm_trace_rtc_abused) {
> +
On Tue, Nov 01, 2016 at 02:59:33PM +0200, Peter Ujfalusi wrote:
> If the pwm is not enabled the backlight initially should not be enabled
> either if we have booted with DT and there is a phandle pointing to the
> backlight node.
>
> The patch extends the checks to decide if we should keep the bac
* John Stultz wrote:
> @@ -222,7 +226,7 @@ static int alarmtimer_suspend(struct device *dev)
> ktime_t min, now;
> unsigned long flags;
> struct rtc_device *rtc;
> - int i;
> + int i, type = 0;
> int ret;
>
> spin_lock_irqsave(&freezer_delta_lock, flags);
On Tue, Nov 01, 2016 at 02:59:32PM +0200, Peter Ujfalusi wrote:
> Move the checks to select the initial state for the backlight to a new
> function and document the checks we are doing.
>
> With the separate function it is going to be easier to fix or improve the
> initial power state configuratio
If CONFIG_STM_SOURCE_FTRACE is selected, Function trace data can be
writen to sink via STM, all functions that related to writing data
packets to STM should be marked 'notrace' to avoid being traced by
Ftrace, otherwise the program would stall into an endless loop.
Signed-off-by: Chunyan Zhang
Ac
If CONFIG_STM_SOURCE_FTRACE is selected, Function trace data can be
writen to sink via STM, all functions that related to writing data
packets to STM should be marked 'notrace' to avoid being traced by
Ftrace, otherwise the program would stall into an endless loop.
Signed-off-by: Chunyan Zhang
Ac
If CONFIG_STM_SOURCE_FTRACE is selected, Function trace data can be
writen to sink via STM, all functions that related to writing data
packets to STM should be marked 'notrace' to avoid being traced by
Ftrace, otherwise the program would stall into an endless loop.
Signed-off-by: Chunyan Zhang
Ac
This patch adds a driver that models itself as an stm_source called
stm_ftrace. Once the stm device and stm_ftrace have been linked via
sysfs, the driver registers itself as a trace_export and everything
passed to the interface from Ftrace subsystem will end up in the STM
trace engine.
Signed-off-
If CONFIG_STM_SOURCE_FTRACE is selected, Function trace data can be
writen to sink via STM, all functions that related to writing data
packets to STM should be marked 'notrace' to avoid being traced by
Ftrace, otherwise the program would stall into an endless loop.
Signed-off-by: Chunyan Zhang
Ac
Currently Function traces can be only exported to ring buffer, this
patch added trace_export concept which can process traces and export
them to a registered destination as an addition to the current only
one output of Ftrace - i.e. ring buffer.
In this way, if we want Function traces to be sent t
Commit-ID: fc0e81b2bea0ebceb71889b61d2240856141c9ee
Gitweb: http://git.kernel.org/tip/fc0e81b2bea0ebceb71889b61d2240856141c9ee
Author: Andy Lutomirski
AuthorDate: Sat, 19 Nov 2016 18:42:40 -0800
Committer: Ingo Molnar
CommitDate: Mon, 21 Nov 2016 08:06:54 +0100
x86/traps: Ignore high w
On 11/18/2016 11:48 PM, Jérôme Glisse wrote:
> This add support for un-addressable device memory. Such memory is hotpluged
> only so we can have struct page but should never be map. This patch add code
struct pages inside the system RAM range unlike the vmem_altmap scheme
where the struct pages ca
IP blocks allowing a variety of trace sources to log debugging
information to a pre-defined area have been introduced on a couple of
architecture [1][2]. These system trace blocks (also known as STM)
typically follow the MIPI STPv2 protocol [3] and provide a system wide
logging facility to any devi
On 11/21/2016 08:32 AM, Alexander Shishkin wrote:
Quentin Lambert writes:
Most error branches following the call to class_find_device contain
a call to put_device. This patch add calls to put_device where
they are missing.
This issue was found with Hector.
Signed-off-by: Quentin Lambert
On Mon, Nov 21, 2016 at 06:27:14PM +1100, Nicholas Piggin wrote:
> Hi Adam,
>
> Thanks. I'd suggest doing x86: or x86/kbuild: prefix for the patch. Also
> possibly consider describing what the patch does at a higher level in your
> subject line, e.g.:
>
> x86/kbuild: enable modversions for symb
801 - 893 of 893 matches
Mail list logo
