On Thu, Jul 12, 2018 at 06:22:13PM -0700, Hugh Dickins wrote:
> A little "optimization" crept into alloc_bts_buffer() along the way,
> which now places bts_interrupt_threshold not on a record boundary.
> And Stephane has shown me the sentence in Vol 3B, 17.4.9, which says
> "This address must
On Thu, Jul 12, 2018 at 06:22:13PM -0700, Hugh Dickins wrote:
> A little "optimization" crept into alloc_bts_buffer() along the way,
> which now places bts_interrupt_threshold not on a record boundary.
> And Stephane has shown me the sentence in Vol 3B, 17.4.9, which says
> "This address must
On 07/12/2018 06:03 PM, Tony Krowiak wrote:
+static int vfio_ap_mdev_open(struct mdev_device *mdev)
+{
+struct ap_matrix_mdev *matrix_mdev = mdev_get_drvdata(mdev);
+struct ap_matrix_dev *matrix_dev =
+to_ap_matrix_dev(mdev_parent_dev(mdev));
+unsigned long events;
+
> +/*
> + * At most times, fine grained cluster lock is sufficient to protect
Can we call out those times, please?
> + * the operations on sis->swap_map.
Please be careful with the naming. You can call it 'si' because that's
what the function argument is named. Or, swap_info_struct because
On 07/12/2018 06:03 PM, Tony Krowiak wrote:
+static int vfio_ap_mdev_open(struct mdev_device *mdev)
+{
+struct ap_matrix_mdev *matrix_mdev = mdev_get_drvdata(mdev);
+struct ap_matrix_dev *matrix_dev =
+to_ap_matrix_dev(mdev_parent_dev(mdev));
+unsigned long events;
+
> +/*
> + * At most times, fine grained cluster lock is sufficient to protect
Can we call out those times, please?
> + * the operations on sis->swap_map.
Please be careful with the naming. You can call it 'si' because that's
what the function argument is named. Or, swap_info_struct because
On Fri, Jul 13, 2018 at 12:32:41PM +0800, Rong Chen wrote:
> Thanks, it's fixed with the patch.
Ingo, could you merge?
---
Subject: watchdog/softlockup: Fix cpu_stop_queue_work double-queue
From: Peter Zijlstra
Date: Wed, 11 Jul 2018 14:34:36 +0200
When scheduling is delayed for longer than
On Fri, Jul 13, 2018 at 12:32:41PM +0800, Rong Chen wrote:
> Thanks, it's fixed with the patch.
Ingo, could you merge?
---
Subject: watchdog/softlockup: Fix cpu_stop_queue_work double-queue
From: Peter Zijlstra
Date: Wed, 11 Jul 2018 14:34:36 +0200
When scheduling is delayed for longer than
Dmitry noticed what is wrong and fixed the bug as
https://github.com/google/syzkaller/commit/06c33b3af0ff4072fb002879f83077c9d162a224
.
Since the bug did not reproduce for last 24 hours, it is OK to close this
report.
#syz invalid
Thanks all.
Dmitry noticed what is wrong and fixed the bug as
https://github.com/google/syzkaller/commit/06c33b3af0ff4072fb002879f83077c9d162a224
.
Since the bug did not reproduce for last 24 hours, it is OK to close this
report.
#syz invalid
Thanks all.
Am Freitag, den 13.07.2018, 13:01 +0300 schrieb Leonard Crestez:
> This is functionally identical but simpler and slightly faster.
>
> The PU domain is turned on at boot time and never turned off. In the
> current implementation the pm core will repeatedly call power_off when
> the domain is
Am Freitag, den 13.07.2018, 13:01 +0300 schrieb Leonard Crestez:
> This is functionally identical but simpler and slightly faster.
>
> The PU domain is turned on at boot time and never turned off. In the
> current implementation the pm core will repeatedly call power_off when
> the domain is
The return value of the get_parent operation is a u8, whereas a -EINVAL
was returned. This wrong value was return if the value was bigger that
the number of parent but this case was already handled by the core.
So we can just remove this chunk of code to fix the issue.
Reported-by: Dan Carpenter
The return value of the get_parent operation is a u8, whereas a -EINVAL
was returned. This wrong value was return if the value was bigger that
the number of parent but this case was already handled by the core.
So we can just remove this chunk of code to fix the issue.
Reported-by: Dan Carpenter
Sandra Loosemore wrote:
> I'm not familiar with the Fedora tools, but to build a complete toolchain
> you'll need library support as well and I'm not sure what the submission
> status/plans for that are.
The idea behind the cross-gcc package in Fedora is that it's for kernel builds
and
Sandra Loosemore wrote:
> I'm not familiar with the Fedora tools, but to build a complete toolchain
> you'll need library support as well and I'm not sure what the submission
> status/plans for that are.
The idea behind the cross-gcc package in Fedora is that it's for kernel builds
and
On Fri, Jul 13, 2018 at 11:56 AM, Tudor Ambarus
wrote:
> Hi, Arnd,
>
> On 07/09/2018 06:57 PM, Arnd Bergmann wrote:
>> + nc->ebi_csa_offs = (uintptr_t)match->data;
>
> I guess we should declare ebi_csa_offs as size_t, right?
Yes, that would make sense, though it doesn't change the behavior.
On Fri, Jul 13, 2018 at 11:56 AM, Tudor Ambarus
wrote:
> Hi, Arnd,
>
> On 07/09/2018 06:57 PM, Arnd Bergmann wrote:
>> + nc->ebi_csa_offs = (uintptr_t)match->data;
>
> I guess we should declare ebi_csa_offs as size_t, right?
Yes, that would make sense, though it doesn't change the behavior.
More simple version. Is this assumption correct?
>From 52f10183f2b921cd946dd4c83d9b1d99bc48914e Mon Sep 17 00:00:00 2001
From: Tetsuo Handa
Date: Fri, 13 Jul 2018 12:15:54 +0900
Subject: [PATCH] fs: Add to super_blocks list after SB_BORN is set.
syzbot is reporting hung tasks at
More simple version. Is this assumption correct?
>From 52f10183f2b921cd946dd4c83d9b1d99bc48914e Mon Sep 17 00:00:00 2001
From: Tetsuo Handa
Date: Fri, 13 Jul 2018 12:15:54 +0900
Subject: [PATCH] fs: Add to super_blocks list after SB_BORN is set.
syzbot is reporting hung tasks at
Hello Hugh,
> A little "optimization" crept into alloc_bts_buffer() along the way, which now
> places bts_interrupt_threshold not on a record boundary.
> And Stephane has shown me the sentence in Vol 3B, 17.4.9, which says "This
> address must point to an offset from the BTS buffer base that is a
Hello Hugh,
> A little "optimization" crept into alloc_bts_buffer() along the way, which now
> places bts_interrupt_threshold not on a record boundary.
> And Stephane has shown me the sentence in Vol 3B, 17.4.9, which says "This
> address must point to an offset from the BTS buffer base that is a
On 13/07/2018 12:56:22+0300, Radu Pirea wrote:
>
>
> On 07/10/2018 09:15 PM, Mark Brown wrote:
> > On Mon, Jun 25, 2018 at 08:22:29PM +0300, Radu Pirea wrote:
> >
> > This is mostly good, just a couple of small things:
> >
> > > +config SPI_AT91_USART
> > > + tristate "Atmel USART Controller
On 13/07/2018 12:56:22+0300, Radu Pirea wrote:
>
>
> On 07/10/2018 09:15 PM, Mark Brown wrote:
> > On Mon, Jun 25, 2018 at 08:22:29PM +0300, Radu Pirea wrote:
> >
> > This is mostly good, just a couple of small things:
> >
> > > +config SPI_AT91_USART
> > > + tristate "Atmel USART Controller
On Thu, Jul 12, 2018 at 01:53:19PM -0700, Andy Lutomirski wrote:
> > On Jul 11, 2018, at 4:29 AM, Joerg Roedel wrote:
> > NMI will no longer use most of the shared return path,
> > because NMI needs special handling when the CR3 switches for
> > PTI are added.
>
> Why? What would go wrong?
>
>
On Thu, Jul 12, 2018 at 01:53:19PM -0700, Andy Lutomirski wrote:
> > On Jul 11, 2018, at 4:29 AM, Joerg Roedel wrote:
> > NMI will no longer use most of the shared return path,
> > because NMI needs special handling when the CR3 switches for
> > PTI are added.
>
> Why? What would go wrong?
>
>
This is functionally identical but simpler and slightly faster.
The PU domain is turned on at boot time and never turned off. In the
current implementation the pm core will repeatedly call power_off when
the domain is unused and get -EBUSY back. If the domain is marked as
"always on" instead the
This is functionally identical but simpler and slightly faster.
The PU domain is turned on at boot time and never turned off. In the
current implementation the pm core will repeatedly call power_off when
the domain is unused and get -EBUSY back. If the domain is marked as
"always on" instead the
On Tue, Jul 10, 2018 at 02:31:30PM -0400, Waiman Long wrote:
> It was found that a constant stream of readers might cause the count to
> go negative most of the time after an initial trigger by a writer even
> if no writer was present afterward. As a result, most of the readers
> would have to go
On Tue, Jul 10, 2018 at 02:31:30PM -0400, Waiman Long wrote:
> It was found that a constant stream of readers might cause the count to
> go negative most of the time after an initial trigger by a writer even
> if no writer was present afterward. As a result, most of the readers
> would have to go
On Fri, 13 Jul 2018 at 14:54, Jens Wiklander wrote:
>
> [+Sumit]
>
> On Mon, Jul 09, 2018 at 08:15:49AM +0200, Jens Wiklander wrote:
> > Adds a kernel internal TEE client interface to be used by other drivers.
> >
> > Signed-off-by: Jens Wiklander
> > ---
Thanks Jens for this patch. I have
On Fri, 13 Jul 2018 at 14:54, Jens Wiklander wrote:
>
> [+Sumit]
>
> On Mon, Jul 09, 2018 at 08:15:49AM +0200, Jens Wiklander wrote:
> > Adds a kernel internal TEE client interface to be used by other drivers.
> >
> > Signed-off-by: Jens Wiklander
> > ---
Thanks Jens for this patch. I have
On Thu, Jul 12, 2018 at 04:37:25PM -0400, Pavel Tatashin wrote:
> Changelog:
> v5 - v4
> - Fixed the issue that was reported on ppc64 when
> CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER is removed
> - Consolidated the new buffer allocation between vmemmap
> and non-vmemmap
On Thu, Jul 12, 2018 at 04:37:25PM -0400, Pavel Tatashin wrote:
> Changelog:
> v5 - v4
> - Fixed the issue that was reported on ppc64 when
> CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER is removed
> - Consolidated the new buffer allocation between vmemmap
> and non-vmemmap
Hi, Arnd,
On 07/09/2018 06:57 PM, Arnd Bergmann wrote:
> + nc->ebi_csa_offs = (uintptr_t)match->data;
I guess we should declare ebi_csa_offs as size_t, right?
Best,
ta
Hi, Arnd,
On 07/09/2018 06:57 PM, Arnd Bergmann wrote:
> + nc->ebi_csa_offs = (uintptr_t)match->data;
I guess we should declare ebi_csa_offs as size_t, right?
Best,
ta
SDHCI-MSM platform is using devfreq ondemand governor.
Select devfreq governor for SDHCI-MSM platform.
Signed-off-by: Ritesh Harjani
Signed-off-by: Sayali Lokhande
---
drivers/mmc/host/Kconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/mmc/host/Kconfig
SDHCI-MSM platform is using devfreq ondemand governor.
Select devfreq governor for SDHCI-MSM platform.
Signed-off-by: Ritesh Harjani
Signed-off-by: Sayali Lokhande
---
drivers/mmc/host/Kconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/mmc/host/Kconfig
On 07/10/2018 09:15 PM, Mark Brown wrote:
On Mon, Jun 25, 2018 at 08:22:29PM +0300, Radu Pirea wrote:
This is mostly good, just a couple of small things:
+config SPI_AT91_USART
+ tristate "Atmel USART Controller SPI driver"
+ depends on HAS_DMA
+ depends on (ARCH_AT91 ||
Limiting the max frequency supported by host controller
to a certain value can be useful for testing power consumption
at various frequencies that are supported by the host.
Note: If the card supports less than desired value then the
frequency of operation would be limited to that frequency.
On 07/10/2018 09:15 PM, Mark Brown wrote:
On Mon, Jun 25, 2018 at 08:22:29PM +0300, Radu Pirea wrote:
This is mostly good, just a couple of small things:
+config SPI_AT91_USART
+ tristate "Atmel USART Controller SPI driver"
+ depends on HAS_DMA
+ depends on (ARCH_AT91 ||
Limiting the max frequency supported by host controller
to a certain value can be useful for testing power consumption
at various frequencies that are supported by the host.
Note: If the card supports less than desired value then the
frequency of operation would be limited to that frequency.
This change adds support for devfreq suspend/resume
to be called on each system suspend/resume, runtime
suspend/resume, power restore.
Signed-off-by: Talel Shenhar
Signed-off-by: Subhash Jadavani
Signed-off-by: Sayali Lokhande
---
drivers/mmc/core/core.c | 112
This change enables clock scaling capability for sdhci-msm
platform driver.
Signed-off-by: Sayali Lokhande
---
drivers/mmc/host/sdhci-msm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mmc/host/sdhci-msm.c b/drivers/mmc/host/sdhci-msm.c
index e9fe8c6..8846a76 100644
---
This change adds support for devfreq suspend/resume
to be called on each system suspend/resume, runtime
suspend/resume, power restore.
Signed-off-by: Talel Shenhar
Signed-off-by: Subhash Jadavani
Signed-off-by: Sayali Lokhande
---
drivers/mmc/core/core.c | 112
This change enables clock scaling capability for sdhci-msm
platform driver.
Signed-off-by: Sayali Lokhande
---
drivers/mmc/host/sdhci-msm.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/mmc/host/sdhci-msm.c b/drivers/mmc/host/sdhci-msm.c
index e9fe8c6..8846a76 100644
---
This change adds the use of devfreq to MMC.
Both eMMC and SD card will use it.
For some workloads, such as video playback, it isn't
necessary for these cards to run at high speed.
Running at lower frequency, for example 52MHz, in such
cases can still meet the deadlines for data transfers.
Scaling
Add sysfs attributes to allow dynamic control of clock scaling
parameters. These attributes are used to enable/disable clock
scaling at runtime and change the up_threshold, down_threshold,
and polling_interval values. Complete documentation for these
sysfs entries are provided at
This change adds the use of devfreq to MMC.
Both eMMC and SD card will use it.
For some workloads, such as video playback, it isn't
necessary for these cards to run at high speed.
Running at lower frequency, for example 52MHz, in such
cases can still meet the deadlines for data transfers.
Scaling
Add sysfs attributes to allow dynamic control of clock scaling
parameters. These attributes are used to enable/disable clock
scaling at runtime and change the up_threshold, down_threshold,
and polling_interval values. Complete documentation for these
sysfs entries are provided at
From: Sahitya Tummala
Add new flag "simple_scaling" to on demand governor so that
the clocks can be scaled up only when the load is more than
up threshold and can be scaled down only when the load is less
than down differential data as provided within
struct devfreq_simple_ondemand_data.
From: Sahitya Tummala
Add new flag "simple_scaling" to on demand governor so that
the clocks can be scaled up only when the load is more than
up threshold and can be scaled down only when the load is less
than down differential data as provided within
struct devfreq_simple_ondemand_data.
This change adds the use of devfreq based clock scaling to MMC.
Both eMMC and SD card can use it.
For some workloads, such as video playback, it isn't necessary
for these cards to run at high speed. Running at lower frequency,
in such cases can still meet the deadlines for data transfers.
Scaling
This change adds the use of devfreq based clock scaling to MMC.
Both eMMC and SD card can use it.
For some workloads, such as video playback, it isn't necessary
for these cards to run at high speed. Running at lower frequency,
in such cases can still meet the deadlines for data transfers.
Scaling
On Thu, Jul 12, 2018 at 01:49:13PM -0700, Andy Lutomirski wrote:
> > On Jul 11, 2018, at 4:29 AM, Joerg Roedel wrote:
> >/* Offset from the sysenter stack to tss.sp0 */
> > -DEFINE(TSS_entry_stack, offsetof(struct cpu_entry_area,
> > tss.x86_tss.sp0) -
> > +DEFINE(TSS_entry_stack,
On Thu, Jul 12, 2018 at 01:49:13PM -0700, Andy Lutomirski wrote:
> > On Jul 11, 2018, at 4:29 AM, Joerg Roedel wrote:
> >/* Offset from the sysenter stack to tss.sp0 */
> > -DEFINE(TSS_entry_stack, offsetof(struct cpu_entry_area,
> > tss.x86_tss.sp0) -
> > +DEFINE(TSS_entry_stack,
On Fri, 13 Jul 2018 01:43:05 +
Marcel Ziswiler wrote:
> On Mon, 2018-07-02 at 15:16 +0200, Ulf Hansson wrote:
> > On 4 June 2018 at 17:35, Aapo Vienamo wrote:
> > > The sdhci get_max_clock callback is set to
> > > sdhci_pltfm_clk_get_max_clock
> > > and tegra_sdhci_get_max_clock is
Add the pin-controller driver for Synaptics AS370 SoC, with definition
of its groups and functions. This uses the core Berlin pinctrl driver.
Signed-off-by: Jisheng Zhang
---
drivers/pinctrl/berlin/Kconfig | 5 +
drivers/pinctrl/berlin/Makefile| 1 +
On Fri, 13 Jul 2018 01:43:05 +
Marcel Ziswiler wrote:
> On Mon, 2018-07-02 at 15:16 +0200, Ulf Hansson wrote:
> > On 4 June 2018 at 17:35, Aapo Vienamo wrote:
> > > The sdhci get_max_clock callback is set to
> > > sdhci_pltfm_clk_get_max_clock
> > > and tegra_sdhci_get_max_clock is
Add the pin-controller driver for Synaptics AS370 SoC, with definition
of its groups and functions. This uses the core Berlin pinctrl driver.
Signed-off-by: Jisheng Zhang
---
drivers/pinctrl/berlin/Kconfig | 5 +
drivers/pinctrl/berlin/Makefile| 1 +
Add as370 to existing berlin pinctrl device tree binding.
Signed-off-by: Jisheng Zhang
---
Documentation/devicetree/bindings/pinctrl/berlin,pinctrl.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/pinctrl/berlin,pinctrl.txt
Add as370 to existing berlin pinctrl device tree binding.
Signed-off-by: Jisheng Zhang
---
Documentation/devicetree/bindings/pinctrl/berlin,pinctrl.txt | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/Documentation/devicetree/bindings/pinctrl/berlin,pinctrl.txt
This series is to add the Synaptics AS370 SoC pinctrl driver.
Jisheng Zhang (2):
dt-binding: pinctrl: berlin: document AS370 SoC pinctrl
pinctrl: berlin: add the as370 SoC pinctrl driver
.../bindings/pinctrl/berlin,pinctrl.txt | 3 +-
drivers/pinctrl/berlin/Kconfig|
This series is to add the Synaptics AS370 SoC pinctrl driver.
Jisheng Zhang (2):
dt-binding: pinctrl: berlin: document AS370 SoC pinctrl
pinctrl: berlin: add the as370 SoC pinctrl driver
.../bindings/pinctrl/berlin,pinctrl.txt | 3 +-
drivers/pinctrl/berlin/Kconfig|
Randy Dunlap wrote:
> I would review this but it sounds like I should just wait for the
> next version.
Probably a good idea. Thanks for the consideration anyway.
David
Randy Dunlap wrote:
> I would review this but it sounds like I should just wait for the
> next version.
Probably a good idea. Thanks for the consideration anyway.
David
On Wed, Jul 11, 2018 at 08:21:43PM +0100, John Whitmore wrote:
> Simple rename of the preprosessor switch, protecting against multiple
> inclusion of the header file. Change to clear the checkpatch coding style
> issue.
>
> Signed-off-by: John Whitmore
> ---
> drivers/staging/rtl8192u/r8192U.h
On Wed, Jul 11, 2018 at 08:21:43PM +0100, John Whitmore wrote:
> Simple rename of the preprosessor switch, protecting against multiple
> inclusion of the header file. Change to clear the checkpatch coding style
> issue.
>
> Signed-off-by: John Whitmore
> ---
> drivers/staging/rtl8192u/r8192U.h
On Fri, Jul 13, 2018 at 11:07:11AM +0200, Andrea Parri wrote:
> On Thu, Jul 12, 2018 at 07:05:39PM -0700, Daniel Lustig wrote:
> > On 7/12/2018 11:10 AM, Linus Torvalds wrote:
> > > On Thu, Jul 12, 2018 at 11:05 AM Peter Zijlstra
> > > wrote:
> > >>
> > >> The locking pattern is fairly simple
On Fri, Jul 13, 2018 at 11:07:11AM +0200, Andrea Parri wrote:
> On Thu, Jul 12, 2018 at 07:05:39PM -0700, Daniel Lustig wrote:
> > On 7/12/2018 11:10 AM, Linus Torvalds wrote:
> > > On Thu, Jul 12, 2018 at 11:05 AM Peter Zijlstra
> > > wrote:
> > >>
> > >> The locking pattern is fairly simple
Hi Ludovic
On 06/25/2018 05:42 PM, Ludovic Barre wrote:
From: Ludovic Barre
This patch series updates stm32_iwdg driver to manage pclk
clock by compatible. stm32mp1 requires a pclk clock.
v5:
-update stm32f429.dtsi
v4:
-dt-bindings: split and review
v3:
-remove stm32_iwdg_config structure,
pls ignore this,my bad.
On 2018/7/13 15:11, YueHaibing wrote:
> When CONFIG_PROC_FS isn't set, gcc warning this:
>
> drivers/connector/connector.c:242:12: warning: ‘cn_proc_show’ defined but not
> used [-Wunused-function]
> static int cn_proc_show(struct seq_file *m, void *v)
> ^
>
Hi Ludovic
On 06/25/2018 05:42 PM, Ludovic Barre wrote:
From: Ludovic Barre
This patch series updates stm32_iwdg driver to manage pclk
clock by compatible. stm32mp1 requires a pclk clock.
v5:
-update stm32f429.dtsi
v4:
-dt-bindings: split and review
v3:
-remove stm32_iwdg_config structure,
pls ignore this,my bad.
On 2018/7/13 15:11, YueHaibing wrote:
> When CONFIG_PROC_FS isn't set, gcc warning this:
>
> drivers/connector/connector.c:242:12: warning: ‘cn_proc_show’ defined but not
> used [-Wunused-function]
> static int cn_proc_show(struct seq_file *m, void *v)
> ^
>
sorry for noise,there has a fix:
[PATCH] acpi/button.c: fix defined but not used warning
https://lkml.org/lkml/2018/7/11/231
On 2018/7/13 15:19, YueHaibing wrote:
> When CONFIG_PROC_FS isn't set, gcc warning this:
>
> drivers/acpi/button.c:255:12: warning: ‘acpi_button_state_seq_show’ defined
sorry for noise,there has a fix:
[PATCH] acpi/button.c: fix defined but not used warning
https://lkml.org/lkml/2018/7/11/231
On 2018/7/13 15:19, YueHaibing wrote:
> When CONFIG_PROC_FS isn't set, gcc warning this:
>
> drivers/acpi/button.c:255:12: warning: ‘acpi_button_state_seq_show’ defined
Add initial dtsi file to support Synaptics AS370 SoC with quad
Cortex-A53 CPUs.
Signed-off-by: Jisheng Zhang
---
arch/arm64/boot/dts/synaptics/as370.dtsi | 177 +++
1 file changed, 177 insertions(+)
create mode 100644 arch/arm64/boot/dts/synaptics/as370.dtsi
diff --git
On Thu, Jul 12, 2018 at 12:30:01PM -0600, Tycho Andersen wrote:
> On Thu, Jul 12, 2018 at 08:25:45PM +0200, Greg Kroah-Hartman wrote:
> > On Thu, Jul 12, 2018 at 12:18:46PM -0600, Tycho Andersen wrote:
> > > On Thu, Jul 12, 2018 at 05:40:15PM +0200, Greg Kroah-Hartman wrote:
> > > > On Thu, Jul
Add initial dtsi file to support Synaptics AS370 SoC with quad
Cortex-A53 CPUs.
Signed-off-by: Jisheng Zhang
---
arch/arm64/boot/dts/synaptics/as370.dtsi | 177 +++
1 file changed, 177 insertions(+)
create mode 100644 arch/arm64/boot/dts/synaptics/as370.dtsi
diff --git
On Thu, Jul 12, 2018 at 12:30:01PM -0600, Tycho Andersen wrote:
> On Thu, Jul 12, 2018 at 08:25:45PM +0200, Greg Kroah-Hartman wrote:
> > On Thu, Jul 12, 2018 at 12:18:46PM -0600, Tycho Andersen wrote:
> > > On Thu, Jul 12, 2018 at 05:40:15PM +0200, Greg Kroah-Hartman wrote:
> > > > On Thu, Jul
The AS370 SoC is a new derivative of the berlin family. The only
difference is the SoC isn't named as berlin*.
Signed-off-by: Jisheng Zhang
---
Documentation/devicetree/bindings/arm/syna.txt | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
The AS370 SoC is a new derivative of the berlin family. The only
difference is the SoC isn't named as berlin*.
Signed-off-by: Jisheng Zhang
---
Documentation/devicetree/bindings/arm/syna.txt | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
Pls ignore this, there has a fix.
[PATCH] staging/rtl8192u: fix defined but not used build warnings
On 2018/7/13 16:01, YueHaibing wrote:
> When CONFIG_PROC_FS isn't set, gcc warning this:
>
> drivers/staging/rtl8192u/r8192U_core.c:508:12: warning: ‘proc_get_stats_ap’
> defined but not used
Pls ignore this, there has a fix.
[PATCH] staging/rtl8192u: fix defined but not used build warnings
On 2018/7/13 16:01, YueHaibing wrote:
> When CONFIG_PROC_FS isn't set, gcc warning this:
>
> drivers/staging/rtl8192u/r8192U_core.c:508:12: warning: ‘proc_get_stats_ap’
> defined but not used
[+Sumit]
On Mon, Jul 09, 2018 at 08:15:49AM +0200, Jens Wiklander wrote:
> Adds a kernel internal TEE client interface to be used by other drivers.
>
> Signed-off-by: Jens Wiklander
> ---
> drivers/tee/tee_core.c | 113 +---
> include/linux/tee_drv.h | 73
[+Sumit]
On Mon, Jul 09, 2018 at 08:15:49AM +0200, Jens Wiklander wrote:
> Adds a kernel internal TEE client interface to be used by other drivers.
>
> Signed-off-by: Jens Wiklander
> ---
> drivers/tee/tee_core.c | 113 +---
> include/linux/tee_drv.h | 73
On Thu, Jul 12, 2018 at 01:29:40PM -0400, Johannes Weiner wrote:
> +static inline void psi_ttwu_dequeue(struct task_struct *p)
> +{
> + if (psi_disabled)
> + return;
> + /*
> + * Is the task being migrated during a wakeup? Make sure to
> + * deregister its
On Thu, Jul 12, 2018 at 01:29:40PM -0400, Johannes Weiner wrote:
> +static inline void psi_ttwu_dequeue(struct task_struct *p)
> +{
> + if (psi_disabled)
> + return;
> + /*
> + * Is the task being migrated during a wakeup? Make sure to
> + * deregister its
Move berlin binding documentation as part of transition from Marvell
berlin to Synaptics SoC.
Signed-off-by: Jisheng Zhang
---
.../bindings/arm/{marvell/marvell,berlin.txt => syna.txt} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename
Move berlin binding documentation as part of transition from Marvell
berlin to Synaptics SoC.
Signed-off-by: Jisheng Zhang
---
.../bindings/arm/{marvell/marvell,berlin.txt => syna.txt} | 0
1 file changed, 0 insertions(+), 0 deletions(-)
rename
Add initial dtsi file for Synaptics AS370 SoC.
patch1 moves berlin binding to syna.txt.
patch2 add dt-binding for the AS370 SoC.
patch3 add the initial dtsi file for the SoC.
Jisheng Zhang (3):
dt-bindings: arm: move berlin binding documentation to syna.txt
dt-bindings: arm: syna: add
Add initial dtsi file for Synaptics AS370 SoC.
patch1 moves berlin binding to syna.txt.
patch2 add dt-binding for the AS370 SoC.
patch3 add the initial dtsi file for the SoC.
Jisheng Zhang (3):
dt-bindings: arm: move berlin binding documentation to syna.txt
dt-bindings: arm: syna: add
Output the warning message before we clobber type and be -1 all the time.
The error message would now be
[1.519791] EXT4-fs warning (device vdb): ext4_enable_quotas:5402:
Failed to enable quota tracking (type=0, err=-3). Please run e2fsck to fix.
Signed-off-by: Junichi Uekawa
---
Output the warning message before we clobber type and be -1 all the time.
The error message would now be
[1.519791] EXT4-fs warning (device vdb): ext4_enable_quotas:5402:
Failed to enable quota tracking (type=0, err=-3). Please run e2fsck to fix.
Signed-off-by: Junichi Uekawa
---
Hi,
On 13-07-18 00:27, Srinivas Pandruvada wrote:
From: Srinivas
One of the requirement for modern x86 system to enter lowest power mode
(SLP_S0) is SATA IP block to be off. This is true even during when
platform is suspended to idle and not only in opportunistic (runtime)
suspend.
Several
Hi,
On 13-07-18 00:27, Srinivas Pandruvada wrote:
From: Srinivas
One of the requirement for modern x86 system to enter lowest power mode
(SLP_S0) is SATA IP block to be off. This is true even during when
platform is suspended to idle and not only in opportunistic (runtime)
suspend.
Several
At 07/12/2018 08:04 AM, Pavel Tatashin wrote:
cyc2ns converts tsc to nanoseconds, and it is handled in a per-cpu data
structure.
Currently, the setup code for c2ns data for every possible CPU goes through
the same sequence of calculations as for the boot CPU, but is based on the
same tsc
At 07/12/2018 08:04 AM, Pavel Tatashin wrote:
cyc2ns converts tsc to nanoseconds, and it is handled in a per-cpu data
structure.
Currently, the setup code for c2ns data for every possible CPU goes through
the same sequence of calculations as for the boot CPU, but is based on the
same tsc
> -#ifdef CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER
> -static void __init sparse_early_mem_maps_alloc_node(void *data,
> - unsigned long pnum_begin,
> - unsigned long pnum_end,
> - unsigned long map_count, int
> -#ifdef CONFIG_SPARSEMEM_ALLOC_MEM_MAP_TOGETHER
> -static void __init sparse_early_mem_maps_alloc_node(void *data,
> - unsigned long pnum_begin,
> - unsigned long pnum_end,
> - unsigned long map_count, int
701 - 800 of 944 matches
Mail list logo
