On Tue, Jul 24, 2018 at 01:08:12PM +0530, Naresh Kamboju wrote:
> On 23 July 2018 at 17:54, Greg Kroah-Hartman
> wrote:
> > This is the start of the stable review cycle for the 4.17.10 release.
> > There are 63 patches in this series, all will be posted as a response
> > to this one. If anyone
On 24/07/18 09:37, Morten Rasmussen wrote:
On Mon, Jul 23, 2018 at 05:07:50PM +0100, Qais Yousef wrote:
On 23/07/18 16:27, Morten Rasmussen wrote:
It does increase the cost of things like hotplug slightly and
repartitioning of root_domains a slightly but I don't see how we can
avoid it if we
Hello
We experience soft lockups with our workload on every tested 4.17.y
kernel. I unfortunately don't know wether there are 4.17 kernels without
the bug but 4.16 kernels are fine and don't show this behaviour.
Known versions with lockup:
4.17.4, 4.17.8, 4.17.9
Latest known versions
On Mon, Jul 23, 2018 at 12:42:55PM +0200, Emmanuel Vadot wrote:
> The SID controller on H5 look the same as the one present in the A64.
> But in case we find some difference one day at a compatible string
> of it's own and a fallback to the A64 one.
>
> Signed-off-by: Emmanuel Vadot
> ---
>
On Tue, Jul 24, 2018 at 09:11:37AM +0800, jiang.bi...@zte.com.cn wrote:
> >> Signed-off-by: Cheng Lin
> >> Signed-off-by: Tan Hu
> >> Signed-off-by: Jiang Biao
> >
> >This SoB chain is invalid.
> Mm, we don't quite understand what the *Signed-off-by* precisely means,
> Does it only mean
On Mon, Jul 23, 2018 at 02:33:08PM -0700, David Rientjes wrote:
> On Mon, 23 Jul 2018, David Rientjes wrote:
>
> > > > The huge zero page can be reclaimed under memory pressure and, if it
> > > > is,
> > > > it is attempted to be allocted again with gfp flags that attempt memory
> > > >
On Mon, Jul 23, 2018 at 04:16:23PM -0700, Cong Wang wrote:
> > > +#define PERF_EF_NO_WAIT 0x08/* do not wait when
> > > stopping, for
> > > + * example, waiting for a timer
> > > + */
> >
> > That's a
On Tue 2018-07-24 10:27:08, Rafael J. Wysocki wrote:
> On Mon, Jul 23, 2018 at 11:49 PM, Pavel Machek wrote:
> >
> > pavel@amd:~$ cat /proc/acpi/battery/BAT0/state
> > present: yes
> > capacity state: ok
> > charging state: charged
> > present rate:0
On Mon, 23 Jul 2018, Matthew Wilcox wrote:
> On Mon, Jul 23, 2018 at 03:42:22PM -0700, Hugh Dickins wrote:
> > On Mon, 23 Jul 2018, Matthew Wilcox wrote:
> > > I figured out a fix and pushed it to the 'ida' branch in
> > > git://git.infradead.org/users/willy/linux-dax.git
> >
> > Great, thanks a
On Tuesday, July 24, 2018 10:46:09 AM CEST Kai Heng Feng wrote:
> Hi Rafael,
>
> > On Jun 13, 2018, at 7:17 PM, Rafael J. Wysocki wrote:
> >
> > From: Rafael J. Wysocki
> >
> > It is reported that commit a192aa923b66a (ACPI / LPSS: Consolidate
> > runtime PM and system sleep handling)
Hi Krzysztof,
On 2018-07-23 19:52, Krzysztof Kozlowski wrote:
> Hi All,
>
> Changes since v1
>
> 1. Add Tomasz's ack.
> 2. Reword description in patch 6/10.
>
>
> Tests
> =
> This is both request for comments and requests for tests. Only basic
> tests were done, including
On Mon, Jul 23, 2018 at 06:44:43PM -0700, Cong Wang wrote:
> On Mon, Jul 23, 2018 at 6:35 PM Cong Wang wrote:
> >
> > Hi, Peter, Andi
> >
> > While reviewing the deadlock, I find out it looks like we could have the
> > following infinite recursion too:
> >
> > perf_event_account_interrupt()
> >
On 24.07.2018 10:53, Michal Hocko wrote:
> On Tue 24-07-18 10:46:20, David Hildenbrand wrote:
>> On 24.07.2018 09:25, Michal Hocko wrote:
>>> On Mon 23-07-18 19:20:43, David Hildenbrand wrote:
On 23.07.2018 14:30, Michal Hocko wrote:
> On Mon 23-07-18 13:45:18, Vlastimil Babka wrote:
On Tue, Jul 24, 2018 at 09:15:18AM +0200, Ingo Molnar wrote:
>
> * Mark Rutland wrote:
>
> > From: Peter Zijlstra
> >
> > Mark found ldsem_cmpxchg() needed an (atomic_long_t *) cast to keep
> > working after making the atomic_long interface type safe.
> >
> > Needing casts is bad form, which
On Tue, Jul 24, 2018 at 11:12 AM, Pavel Machek wrote:
> On Tue 2018-07-24 10:27:08, Rafael J. Wysocki wrote:
>> On Mon, Jul 23, 2018 at 11:49 PM, Pavel Machek wrote:
>> >
>> > pavel@amd:~$ cat /proc/acpi/battery/BAT0/state
>> > present: yes
>> > capacity state: ok
>> >
Am Montag, den 23.07.2018, 13:55 + schrieb Robin Gong:
> > -Original Message-
> > From: Lucas Stach [mailto:l.st...@pengutronix.de]
> > Sent: 2018年7月23日 18:54
> > To: Robin Gong ; vk...@kernel.org;
> > dan.j.willi...@intel.com; s.ha...@pengutronix.de; li...@armlinux.or
> > g.uk
> > Cc:
On Tue, Jul 24, 2018 at 9:07 AM, Finn Thain wrote:
> This addresses the issues arising from commit 324caa29cd04
> ("m68k: mac: use time64_t in RTC handling").
>
> Adopt __u32 for the union in via_read_time(), consistent with changes
> to via_write_time().
>
> Use low_32_bits() in
On Tue, Jul 24, 2018 at 11:20:36AM +0200, Peter Zijlstra wrote:
> On Tue, Jul 24, 2018 at 09:15:18AM +0200, Ingo Molnar wrote:
> >
> > * Mark Rutland wrote:
> >
> > > From: Peter Zijlstra
> > >
> > > Mark found ldsem_cmpxchg() needed an (atomic_long_t *) cast to keep
> > > working after
On Thu, Jul 19, 2018 at 07:21:41AM +0800, Yang Shi wrote:
> When running some mmap/munmap scalability tests with large memory (i.e.
> > 300GB), the below hung task issue may happen occasionally.
>
> INFO: task ps:14018 blocked for more than 120 seconds.
>Tainted: GE
Hi Levin,
Am Samstag, 21. Juli 2018, 10:30:26 CEST schrieb d...@t-chip.com.cn:
> From: Levin Du
>
> ROC-RK3399-PC is the first power efficient 4GB DDR4 single board
maybe "is a power efficient" instead of "the first" ;-)
[...]
> diff --git a/arch/arm64/boot/dts/rockchip/rk3399-roc-pc.dts
>
Hi Stephen,
On Tue, Jul 24, 2018 at 08:50:15AM +1000, Stephen Rothwell wrote:
> Today's linux-next merge of the arm64 tree got a conflict in:
>
> arch/arm64/Makefile
>
> between commits:
>
> 38fc42486775 ("arm64: Use aarch64elf and aarch64elfb emulation mode
> variants")
> 2893af07e507
On 24 July 2018 at 10:12, Arnd Bergmann wrote:
> On Tue, Jul 24, 2018 at 2:26 AM, AKASHI Takahiro
> wrote:
>> On Tue, Jul 24, 2018 at 09:05:45AM +1000, Stephen Rothwell wrote:
>>> Hi all,
>>>
>>> After merging the arm64 tree, today's linux-next build (x86_64
>>> allmodconfig) produced this
Kconfig reports a warning on x86 builds after the ARM64 dependency
was added.
drivers/acpi/Kconfig:6:error: recursive dependency detected!
drivers/acpi/Kconfig:6: symbol ACPI depends on EFI
This rephrases the dependency to keep the ARM64 details out of the
shared Kconfig file, so Kconfig
On 32-bit targets, size_t is often 'unsigned int', so printing it as %lu
causes a warning:
drivers/fsi/fsi-master-ast-cf.c: In function 'fsi_master_acf_read':
drivers/fsi/fsi-master-ast-cf.c:609:23: error: format '%u' expects argument of
type 'unsigned int', but argument 6 has type 'size_t' {aka
On Tue, Jul 24, 2018 at 11:33 AM, Arnd Bergmann wrote:
> Kconfig reports a warning on x86 builds after the ARM64 dependency
> was added.
>
> drivers/acpi/Kconfig:6:error: recursive dependency detected!
> drivers/acpi/Kconfig:6: symbol ACPI depends on EFI
>
> This rephrases the dependency to
When CONFIG_SND_PCM_IEC958 is disabled, we get a link error for the
new driver:
sound/soc/meson/axg-spdifout.o: In function `axg_spdifout_hw_params':
axg-spdifout.c:(.text+0x650): undefined reference to
`snd_pcm_create_iec958_consumer_hw_params'
The other users use 'select', so we should do the
The newly introduced function produces a warning without CONFIG_PCI_QUIRKS:
drivers/pci/probe.c: In function 'pci_bus_read_dev_vendor_id':
drivers/pci/probe.c:2221:18: error: unused variable 'bridge'
[-Werror=unused-variable]
Move the variable declaration into that #ifdef to avoid the warning.
On Sat, Jul 21, 2018 at 07:21:16PM +0100, Al Viro wrote:
> On Sun, Jul 22, 2018 at 01:30:17AM +0800, Sean Fu wrote:
> > Use PAGE_SHIFT and i_blkbits of bd_inode directly to avoid ugly sizebits
> > calculation.
> > Remove ugly sizebits calculation.
> > Remove unnecessary sizebits parameter of
On Tue, Jul 24, 2018 at 11:37:10AM +0200, Rafael J. Wysocki wrote:
> On Tue, Jul 24, 2018 at 11:33 AM, Arnd Bergmann wrote:
> > Kconfig reports a warning on x86 builds after the ARM64 dependency
> > was added.
> >
> > drivers/acpi/Kconfig:6:error: recursive dependency detected!
> >
On Tue, Jul 24, 2018 at 11:44 AM, Will Deacon wrote:
> On Tue, Jul 24, 2018 at 11:37:10AM +0200, Rafael J. Wysocki wrote:
>> On Tue, Jul 24, 2018 at 11:33 AM, Arnd Bergmann wrote:
>
> How about something along the lines of what Ard suggested? Untested diff
> below.
>
>
> diff --git
On 07/23/2018 02:30 PM, Michal Hocko wrote:
> On Mon 23-07-18 13:45:18, Vlastimil Babka wrote:
>> On 07/20/2018 02:34 PM, David Hildenbrand wrote:
>>> Dumping tools (like makedumpfile) right now don't exclude reserved pages.
>>> So reserved pages might be access by dump tools although nobody
Hi,
Am 16.04.2018 um 11:38 schrieb Lee Jones:
> On Thu, 29 Mar 2018, Daniel Schultz wrote:
>
>> Since all three shutdown functions have almost the same code, all logic
>> from the shutdown functions can be refactored to a new function
>> "rk808_update_bits", which can update a register by a given
On Tue, Jul 24, 2018 at 11:46:23AM +0200, Arnd Bergmann wrote:
> On Tue, Jul 24, 2018 at 11:44 AM, Will Deacon wrote:
> > On Tue, Jul 24, 2018 at 11:37:10AM +0200, Rafael J. Wysocki wrote:
> >> On Tue, Jul 24, 2018 at 11:33 AM, Arnd Bergmann wrote:
>
> >
> > How about something along the lines
On 07/24/2018 09:22 AM, Michal Hocko wrote:
> On Mon 23-07-18 19:12:58, David Hildenbrand wrote:
>> On 23.07.2018 13:45, Vlastimil Babka wrote:
>>> On 07/20/2018 02:34 PM, David Hildenbrand wrote:
Dumping tools (like makedumpfile) right now don't exclude reserved pages.
So reserved pages
Kconfig reports a warning on x86 builds after the ARM64 dependency
was added.
drivers/acpi/Kconfig:6:error: recursive dependency detected!
drivers/acpi/Kconfig:6: symbol ACPI depends on EFI
This rephrases the dependency to keep the ARM64 details out of the
shared Kconfig file, so Kconfig
Hi Levin,
Missatge de Heiko Stuebner del dia dt., 24 de jul.
2018 a les 11:29:
>
> Hi Levin,
>
> Am Samstag, 21. Juli 2018, 10:30:26 CEST schrieb d...@t-chip.com.cn:
> > From: Levin Du
> >
> > ROC-RK3399-PC is the first power efficient 4GB DDR4 single board
>
> maybe "is a power efficient"
On Tue, Jul 24, 2018 at 11:48 AM, Arnd Bergmann wrote:
> Kconfig reports a warning on x86 builds after the ARM64 dependency
> was added.
>
> drivers/acpi/Kconfig:6:error: recursive dependency detected!
> drivers/acpi/Kconfig:6: symbol ACPI depends on EFI
>
> This rephrases the dependency to
Use GPC_PGC_DOMAIN_* indexes consistent.
Signed-off-by: Sven Schmitt
---
drivers/soc/imx/gpc.c | 16 ++--
1 file changed, 10 insertions(+), 6 deletions(-)
diff --git a/drivers/soc/imx/gpc.c b/drivers/soc/imx/gpc.c
index 35cc1d2dc4d5..6618ff1eaebd 100644
--- a/drivers/soc/imx/gpc.c
imx6_pm_domain_power_off() reads iso and iso2sw from GPC_PGC_PUPSCR_OFFS
which stores the power up delays.
So use GPC_PGC_PDNSCR_OFFS for the correct delays.
Signed-off-by: Sven Schmitt
---
drivers/soc/imx/gpc.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git
This patch series fixes the power down delay in gpc.c
and improves readability.
Changes in v3:
* rebased to 4.18
* split up patch into 3 parts
Changes in v2:
* dropped cntr_pup_bit
Sven Schmitt (3):
soc: imx: gpc: fix PDN delay
soc: imx: gpc: clean up
soc: imx: gpc: use GPC_PGC_DOMAIN_*
Remove unused #defines.
Signed-off-by: Sven Schmitt
---
drivers/soc/imx/gpc.c | 4
1 file changed, 4 deletions(-)
diff --git a/drivers/soc/imx/gpc.c b/drivers/soc/imx/gpc.c
index 5126185e68c6..35cc1d2dc4d5 100644
--- a/drivers/soc/imx/gpc.c
+++ b/drivers/soc/imx/gpc.c
@@ -24,15 +24,11 @@
On 23-Jul 10:11, Suren Baghdasaryan wrote:
> On Mon, Jul 23, 2018 at 8:40 AM, Patrick Bellasi
> wrote:
> > On 21-Jul 20:05, Suren Baghdasaryan wrote:
> >> On Mon, Jul 16, 2018 at 1:29 AM, Patrick Bellasi
[...]
> >> So to satisfy both TG and syscall requirements I think you would
> >> need to
Hello Steven,
I am doing correlation of linux sched events, following all tasks between cpus,
and one thing that would be really convenient would be to have a global
trace_pipe_raw, in addition to the per-cpu ones, with already sorted events.
I would imagine the core functionality is already
Hello Steven,
I am doing correlation of linux sched events, following all tasks between cpus,
and one thing that would be really convenient would be to have a global
trace_pipe_raw, in addition to the per-cpu ones, with already sorted events.
I would imagine the core functionality is already
On Tue, 2018-07-24 at 11:36 +0200, Arnd Bergmann wrote:
> When CONFIG_SND_PCM_IEC958 is disabled, we get a link error for the
> new driver:
>
> sound/soc/meson/axg-spdifout.o: In function `axg_spdifout_hw_params':
> axg-spdifout.c:(.text+0x650): undefined reference to
>
On 18 July 2018 at 19:40, Bruce Merry wrote:
>> Yes, very easy to produce zombies, though I don't think kernel
>> provides any way to tell how many zombies exist on the system.
>>
>> To create a zombie, first create a memcg node, enter that memcg,
>> create a tmpfs file of few KiBs, exit the
Am Montag, den 23.07.2018, 12:37 + schrieb Leonard Crestez:
> On Mon, 2018-07-23 at 11:38 +0200, Lucas Stach wrote:
> > Hi Leonard,
> >
> > Am Freitag, den 20.07.2018, 15:47 +0300 schrieb Leonard Crestez:
> > > On imx7d the pcie-phy power domain is turned off in suspend and this can
> > >
Both H3 and H5 and a SID controller at the same address.
They are know to be different, the H5 one is the same as the A64 so add
a node in the common dtsi and we will override the compatible string in
the SoC dts.
Signed-off-by: Emmanuel Vadot
---
arch/arm/boot/dts/sunxi-h3-h5.dtsi | 4
1
The A64 have a SID controller which consist on EFUSE (starting at 0x200)
and three registers to read/write the efuses.
Signed-off-by: Emmanuel Vadot
---
arch/arm64/boot/dts/allwinner/sun50i-a64.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git
The H5 SoC have a SID controller that looks like the one in A64, but
in case we find some difference in the futur at a binding for it.
Signed-off-by: Emmanuel Vadot
---
Documentation/devicetree/bindings/nvmem/allwinner,sunxi-sid.txt | 1 +
1 file changed, 1 insertion(+)
diff --git
The SID controller on H5 look the same as the one present in the A64.
But in case we find some difference one day at a compatible string
of it's own and a fallback to the A64 one.
Signed-off-by: Emmanuel Vadot
---
arch/arm64/boot/dts/allwinner/sun50i-h5.dtsi | 5 +
1 file changed, 5
The SID controller on H3 is one of it's kind (at least from what we
know).
Add a compatible string for it in the SoC dtsi.
Signed-off-by: Emmanuel Vadot
---
arch/arm/boot/dts/sun8i-h3.dtsi | 4
1 file changed, 4 insertions(+)
diff --git a/arch/arm/boot/dts/sun8i-h3.dtsi
On Tue, Jul 24, 2018 at 11:54:25AM +0200, Rafael J. Wysocki wrote:
> On Tue, Jul 24, 2018 at 11:48 AM, Arnd Bergmann wrote:
> > Kconfig reports a warning on x86 builds after the ARM64 dependency
> > was added.
> >
> > drivers/acpi/Kconfig:6:error: recursive dependency detected!
> >
On Tue, Jul 24, 2018 at 12:21 PM, Will Deacon wrote:
> On Tue, Jul 24, 2018 at 11:54:25AM +0200, Rafael J. Wysocki wrote:
>> On Tue, Jul 24, 2018 at 11:48 AM, Arnd Bergmann wrote:
>> > Kconfig reports a warning on x86 builds after the ARM64 dependency
>> > was added.
>> >
>> >
On Tuesday, July 24, 2018 11:13:42 AM CEST Rafael J. Wysocki wrote:
> On Tuesday, July 24, 2018 10:46:09 AM CEST Kai Heng Feng wrote:
> > Hi Rafael,
> >
> > > On Jun 13, 2018, at 7:17 PM, Rafael J. Wysocki wrote:
> > >
> > > From: Rafael J. Wysocki
> > >
> > > It is reported that commit
[v7]
* Updated the logic to check for related CPUs.
[v6]
* Renamed match table 'qcom_cpufreq_hw_match'.
* Renamed 'qcom_read_lut' to 'qcom_cpufreq_hw_read_lut'.
* Updated the logic to check for related CPUs at the beginning of the
'qcom_cpu_resources_init'.
* Use
From: Marcel Ziswiler
Reorder PCIe properties.
Signed-off-by: Marcel Ziswiler
---
arch/arm/boot/dts/tegra124-apalis-v1.2.dtsi | 2 +-
arch/arm/boot/dts/tegra124-apalis.dtsi | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
From: Marcel Ziswiler
Drop unused pinmux label.
Signed-off-by: Marcel Ziswiler
---
arch/arm/boot/dts/tegra124-apalis-v1.2.dtsi | 2 +-
arch/arm/boot/dts/tegra124-apalis.dtsi | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
From: Marcel Ziswiler
Add empty local-mac-address property to be filled in by boot loader
(e.g. U-Boot).
Signed-off-by: Marcel Ziswiler
---
arch/arm/boot/dts/tegra124-apalis-v1.2.dtsi | 5 +
arch/arm/boot/dts/tegra124-apalis.dtsi | 5 +
2 files changed, 10 insertions(+)
diff
This series is a minor overhaul for the Toradex Apalis TK1 system on
module.
Marcel Ziswiler (15):
ARM: tegra: apalis-tk1: add local-mac-address property
ARM: tegra: apalis-tk1: reorder pcie properties
ARM: tegra: apalis-tk1: reorder host1x/hdmi properties
ARM: tegra: apalis-tk1: reorder
From: Marcel Ziswiler
Add mmc-ddr-1_8v property enabling eMMC DDR52 mode.
root@apalis-tk1-mainline:~# cat /sys/kernel/debug/mmc2/ios
clock: 5200 Hz
actual clock: 5200 Hz
vdd:21 (3.3 ~ 3.4 V)
bus mode: 2 (push-pull)
chip select:0 (don't care)
power mode:
From: Marcel Ziswiler
Reorder CPU DFLL clock properties.
Signed-off-by: Marcel Ziswiler
---
arch/arm/boot/dts/tegra124-apalis-v1.2.dtsi | 2 +-
arch/arm/boot/dts/tegra124-apalis.dtsi | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
From: Marcel Ziswiler
Add toradex,apalis-tk1-v1.2 compatible.
Signed-off-by: Marcel Ziswiler
---
Documentation/devicetree/bindings/arm/tegra.txt | 2 ++
arch/arm/boot/dts/tegra124-apalis-v1.2-eval.dts | 3 ++-
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git
From: Marcel Ziswiler
PLX got bought by Broadcom therefore fix device tree compatible string
vendor which silences the following checkpatch.pl warning:
WARNING: DT compatible string vendor "plx" appears un-documented
-- check ./Documentation/devicetree/bindings/vendor-prefixes.txt
From: Marcel Ziswiler
Reorder Host1x/HDMI properties.
Signed-off-by: Marcel Ziswiler
---
arch/arm/boot/dts/tegra124-apalis-v1.2.dtsi | 4 ++--
arch/arm/boot/dts/tegra124-apalis.dtsi | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git
Hello Viresh,
Thanks for your review comments.
On 7/18/2018 11:16 AM, Viresh Kumar wrote:
On 18-07-18, 11:07, Taniya Das wrote:
+static int qcom_cpu_resources_init(struct platform_device *pdev,
+ struct device_node *np, unsigned int cpu,
+
From: Marcel Ziswiler
Just cosmetic regulator clean-up.
Signed-off-by: Marcel Ziswiler
---
arch/arm/boot/dts/tegra124-apalis-v1.2.dtsi | 100 ++--
arch/arm/boot/dts/tegra124-apalis.dtsi | 100 ++--
2 files changed, 100 insertions(+), 100
From: Marcel Ziswiler
Add proper eMMC vmmc and vqmmc supplies e.g. fixing signalling voltage.
Signed-off-by: Marcel Ziswiler
---
arch/arm/boot/dts/tegra124-apalis-v1.2.dtsi | 2 ++
arch/arm/boot/dts/tegra124-apalis.dtsi | 2 ++
2 files changed, 4 insertions(+)
diff --git
From: Marcel Ziswiler
White-space clean-up.
Signed-off-by: Marcel Ziswiler
---
arch/arm/boot/dts/tegra124-apalis-v1.2.dtsi | 3 ---
arch/arm/boot/dts/tegra124-apalis.dtsi | 3 ---
2 files changed, 6 deletions(-)
diff --git a/arch/arm/boot/dts/tegra124-apalis-v1.2.dtsi
From: Marcel Ziswiler
Reorder SD card properties.
Signed-off-by: Marcel Ziswiler
---
arch/arm/boot/dts/tegra124-apalis-eval.dts | 4 ++--
arch/arm/boot/dts/tegra124-apalis-v1.2-eval.dts | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
diff --git
From: Marcel Ziswiler
Reorder backlight properties.
Signed-off-by: Marcel Ziswiler
---
arch/arm/boot/dts/tegra124-apalis-eval.dts | 2 +-
arch/arm/boot/dts/tegra124-apalis-v1.2-eval.dts | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
Add QCOM cpufreq firmware device bindings for Qualcomm Technology Inc's
SoCs. This is required for managing the cpu frequency transitions which are
controlled by the hardware engine.
Signed-off-by: Taniya Das
---
.../bindings/cpufreq/cpufreq-qcom-hw.txt | 172 +
1
From: Marcel Ziswiler
Add missing regulators:
- reg_module_3v3_audio being VDDA supply of SGTL5000
- VDDD supply of SGTL5000 actually being reg_1v8_vio
- TMP451 temperature sensor vcc supply being reg_module_3v3
- usb3-0 vbus supply being reg_usbh_vbus
- usb3-1 vbus supply being reg_usbo1_vbus
-
From: Marcel Ziswiler
Reorder padctl properties.
Signed-off-by: Marcel Ziswiler
---
arch/arm/boot/dts/tegra124-apalis-v1.2.dtsi | 22 +++---
arch/arm/boot/dts/tegra124-apalis.dtsi | 22 +++---
2 files changed, 22 insertions(+), 22 deletions(-)
diff
The CPUfreq HW present in some QCOM chipsets offloads the steps necessary
for changing the frequency of CPUs. The driver implements the cpufreq
driver interface for this hardware engine.
Signed-off-by: Saravana Kannan
Signed-off-by: Taniya Das
---
drivers/cpufreq/Kconfig.arm | 11 ++
I got a machine that the resource of firmware enabled IOAPIC conflicts
with the resource of a children bus when the PCI host bus be hotplug.
[ 3182.243325] PCI host bridge to bus 0001:40
[ 3182.243328] pci_bus 0001:40: root bus resource [io 0xc000-0xdfff window]
[ 3182.243330] pci_bus 0001:40:
Hi Kishon,
On Tue, 24 Jul 2018 09:31:34 +0530 wrote:
> Hi,
>
> On Tuesday 17 July 2018 04:57 PM, Kunihiko Hayashi wrote:
> > Hi Kishon,
> >
> > On Fri, 13 Jul 2018 12:45:06 +0530 wrote:
> >
> >> Hi,
> >>
> >> On Wednesday 11 July 2018 05:35 PM, Kunihiko Hayashi wrote:
> >>> On Mon, 9 Jul
On Mon, Jul 23, 2018 at 04:54:02PM +0100, Srinivas Kandagatla wrote:
> This patch adds bindings for wcd9335 audio codec which can support both
> SLIMbus
> and I2S/I2C interface.
...
> +Qualcomm WCD9335 Codec is a standalone Hi-Fi audio codec IC,
> +It supports both I2S/I2C and SLIMbus audio
Add functionality to allocate interrupt lines that will deliver IRQs
as Non-Maskable Interrupts. These allocations are only successful if
the irqchip provides the necessary support and allows NMI delivery for the
interrupt line.
Interrupt lines allocated for NMI delivery must be enabled/disabled
Add support for percpu_devid interrupts treated as NMIs.
Percpu_devid NMIs need to be setup/torn down on each CPU they target.
The same restrictions as for global NMIs still apply for percpu_devid NMIs.
Signed-off-by: Julien Thierry
Cc: Thomas Gleixner
Cc: Peter Zijlstra
Cc: Ingo Molnar
Cc:
NMI handling code should be executed between calls to nmi_enter and
nmi_exit.
Add a separate domain handler to properly setup NMI context when handling
an interrupt requested as NMI.
Signed-off-by: Julien Thierry
Cc: Thomas Gleixner
Cc: Marc Zyngier
Cc: Will Deacon
Cc: Peter Zijlstra
---
On Tue, Jul 17, 2018 at 10:01:17AM +0200, Bartosz Golaszewski wrote:
> I will soon be sending my pull request to Wolfram, so if you still
> want that applied for 4.19 - please resend with the commit message
> fixed.
Alan?
Not sure whether it's too late for 4.19 now though.
--
Sakari Ailus
Provide flow handlers that are NMI safe for interrupts and percpu_devid
interrupts.
Signed-off-by: Julien Thierry
Cc: Thomas Gleixner
Cc: Marc Zyngier
Cc: Peter Zijlstra
---
include/linux/irq.h | 3 +++
kernel/irq/chip.c | 54 +
2 files
Hi,
This patch series provides a way for irqchips to define some IRQs as NMIs.
For this to be possible, the irqchip must:
- be a root irqchip
- not require bus locking
- have the NMI support flag
Once these conditions are met, interrupt lines can be requested as NMIs.
These lines must not be
The new gasket staging driver ran into a randconfig build failure when
CONFIG_EVENTFD is disabled:
In file included from drivers/staging/gasket/gasket_interrupt.h:11,
from drivers/staging/gasket/gasket_interrupt.c:4:
include/linux/eventfd.h: In function 'eventfd_ctx_fdget':
Hi,
Le lun. 23 juil. 2018 à 19:58, Paul Burton a
écrit :
Hi Paul & Vinod,
On Sat, Jul 21, 2018 at 01:06:25PM +0200, Paul Cercueil wrote:
This is the version 3 of my jz4780-dma driver update patchset.
Apologies to the DMA people, the v2 of this patchset did not make
it to
their
Hi Rob,
On Tue, 17 Jul 2018 08:16:23 -0600 wrote:
> On Tue, Jul 17, 2018 at 4:55 AM Kunihiko Hayashi
> wrote:
> >
> > Hi Rob,
> > Thank you for your comments.
> >
> > On Mon, 16 Jul 2018 14:50:49 -0600 wrote:
> >
> > > On Fri, Jun 29, 2018 at 05:38:58PM +0900, Kunihiko Hayashi wrote:
> > > >
* Mark Rutland wrote:
> On Tue, Jul 24, 2018 at 11:20:36AM +0200, Peter Zijlstra wrote:
> > On Tue, Jul 24, 2018 at 09:15:18AM +0200, Ingo Molnar wrote:
> > >
> > > * Mark Rutland wrote:
> > >
> > > > From: Peter Zijlstra
> > > >
> > > > Mark found ldsem_cmpxchg() needed an (atomic_long_t
On 20-07-18, 16:42, Peter Ujfalusi wrote:
>
>
> On 2018-07-19 12:22, Vinod wrote:
> > Hi Peter,
> >
> > On 18-07-18, 13:06, Peter Ujfalusi wrote:
> >
> +struct dma_async_tx_descriptor;
> +
> +struct dma_descriptor_metadata_ops {
> +int (*attach)(struct
On Tuesday, 24 July 2018 04:57:24 MSK Peter Geis wrote:
> On 07/23/2018 08:27 PM, Dmitry Osipenko wrote:
> > On Monday, 23 July 2018 22:38:48 MSK Peter Geis wrote:
> >> Added support for the CPCAP power management regulator functions on
> >> Tegra devices.
> >> Added sw2_sw4 value tables, which
* Masahiro Yamada wrote:
> 2018-06-23 2:22 GMT+09:00 Nadav Amit :
> > Using macros for inline assembly improves both readability and
> > compilation decisions that are distorted by big assembly blocks that use
> > alternative sections. Compile macros.S and use it to assemble all C
> > files.
The ebcdic.c file contains tables for converting between ebcdic and
PC codepage 437. I could however not identify which encoding was used
for the comments. This seems to be some variation of ISO_8859-1 with
non-UTF-8 escape characters.
I have converted this to UTF-8 by manually removing the
The font files contain bit masks for characters in the cp437 character
set, and comments showing what character this is supposed to be.
This only makes sense when the terminal used to view the files is
set to the same codepage, but all other files in the kernel now use
utf-8 encoding.
This
drivers/staging/rtl8188eu/include/odm.h uses an incorrect encoding
for the '...' character in two comments, which makes it one of the
few non-UTF-8 source files.
This removes the odd characters and uses the same ASCII representation
that we have in the regular rtlwifi driver. The second instance
On Tue 24-07-18 11:47:02, Vlastimil Babka wrote:
> On 07/23/2018 02:30 PM, Michal Hocko wrote:
> > On Mon 23-07-18 13:45:18, Vlastimil Babka wrote:
> >> On 07/20/2018 02:34 PM, David Hildenbrand wrote:
> >>> Dumping tools (like makedumpfile) right now don't exclude reserved pages.
> >>> So
On Thu, Jul 19, 2018 at 7:38 PM, Joe Perches wrote:
> On Thu, 2018-07-19 at 17:03 +0200, Geert Uytterhoeven wrote:
>> >
>> > The one exception seems to be arch/s390/kernel/ebcdic.c, which apparently
>> > uses 0x81 bytes as an excape before characters ISO-8859-1 characters with
>> > the high bit
On Monday, 23 July 2018 16:05:21 MSK Dmitry Osipenko wrote:
> On Friday, 20 July 2018 16:45:30 MSK Ben Dooks wrote:
> > The 2D and 3D clocks have an IDLE field in bits 15:8 so add these
> > clocks by making a 2D and 3D mux, and split the divider into the
> > standard 2D/3D ones and 2D/3D idle
[+cc Anders]
On Tue, Jul 24, 2018 at 4:39 AM Arnd Bergmann wrote:
>
> The newly introduced function produces a warning without CONFIG_PCI_QUIRKS:
>
> drivers/pci/probe.c: In function 'pci_bus_read_dev_vendor_id':
> drivers/pci/probe.c:2221:18: error: unused variable 'bridge'
>
On Mon, 2018-07-23 at 11:38 -0700, Andrey Smirnov wrote:
> On Mon, Jul 23, 2018 at 5:41 AM Leonard Crestez
> wrote:
> > On Fri, 2018-07-20 at 08:33 -0700, Andrey Smirnov wrote:
> > > On Fri, Jul 20, 2018 at 5:48 AM Leonard Crestez
> > > wrote:
> > > >
> > > > This reverts commit
On 22-07-18, 23:20, Andreas Färber wrote:
> From: Damien Horsley
>
> It is possible that mdc_tx_status may be called before the first
> node has been read from memory.
>
> In this case, the residue value stored in the register is undefined.
> Return the transfer size instead.
>
>
801 - 900 of 1482 matches
Mail list logo