Quoting Tero Kristo (2018-11-29 23:37:35)
> On 30/11/2018 02:26, Stephen Boyd wrote:
> > Quoting Andreas Kemnade (2018-11-10 12:31:12)
> >> On the gta04 with a dm3730 omap_hdq does not work properly when the
> >> device enters lower power states. Idling uart1 and 2 is enough
> >> to show up that
Quoting Tero Kristo (2018-11-29 23:37:35)
> On 30/11/2018 02:26, Stephen Boyd wrote:
> > Quoting Andreas Kemnade (2018-11-10 12:31:12)
> >> On the gta04 with a dm3730 omap_hdq does not work properly when the
> >> device enters lower power states. Idling uart1 and 2 is enough
> >> to show up that
Quoting Tero Kristo (2018-11-29 23:35:35)
> On 30/11/2018 09:20, Stephen Boyd wrote:
> > Quoting Andreas Kemnade (2018-11-29 22:15:34)
> >> Hi Stephen,
> >>
> >> On Thu, 29 Nov 2018 16:25:05 -0800
> >> Stephen Boyd wrote:
> >>
> >>> Quoting Andreas Kemnade (2018-11-10 12:31:14)
> Code might
Quoting Tero Kristo (2018-11-29 23:35:35)
> On 30/11/2018 09:20, Stephen Boyd wrote:
> > Quoting Andreas Kemnade (2018-11-29 22:15:34)
> >> Hi Stephen,
> >>
> >> On Thu, 29 Nov 2018 16:25:05 -0800
> >> Stephen Boyd wrote:
> >>
> >>> Quoting Andreas Kemnade (2018-11-10 12:31:14)
> Code might
On Thu, Nov 29, 2018 at 03:45:23PM -0800, Stephen Boyd wrote:
> Quoting Nicholas Mc Guire (2018-11-21 04:28:30)
> > The kmalloc here is small (< 16 bytes) and occurs during initialization
> > during system startup here (can not be built as module) thus if this
> > kmalloc failed it is an
On Thu, Nov 29, 2018 at 03:45:23PM -0800, Stephen Boyd wrote:
> Quoting Nicholas Mc Guire (2018-11-21 04:28:30)
> > The kmalloc here is small (< 16 bytes) and occurs during initialization
> > during system startup here (can not be built as module) thus if this
> > kmalloc failed it is an
On 11/29/18 9:59 PM, Atish Patra wrote:
On 11/27/18 2:04 AM, Anup Patel wrote:
Currently on SMP host, all CPUs take external interrupts routed via
PLIC. All CPUs will try to claim a given external interrupt but only
one of them will succeed while other CPUs would simply resume whatever
they
On 11/29/18 9:59 PM, Atish Patra wrote:
On 11/27/18 2:04 AM, Anup Patel wrote:
Currently on SMP host, all CPUs take external interrupts routed via
PLIC. All CPUs will try to claim a given external interrupt but only
one of them will succeed while other CPUs would simply resume whatever
they
Quoting Charles Keepax (2018-11-20 06:16:30)
> diff --git a/drivers/clk/clk-lochnagar.c b/drivers/clk/clk-lochnagar.c
> new file mode 100644
> index ..8b2a78689715
> --- /dev/null
> +++ b/drivers/clk/clk-lochnagar.c
> @@ -0,0 +1,360 @@
[...]
> +
> +static int
Quoting Charles Keepax (2018-11-20 06:16:30)
> diff --git a/drivers/clk/clk-lochnagar.c b/drivers/clk/clk-lochnagar.c
> new file mode 100644
> index ..8b2a78689715
> --- /dev/null
> +++ b/drivers/clk/clk-lochnagar.c
> @@ -0,0 +1,360 @@
[...]
> +
> +static int
Here is a patch-series which adding EPT-Based Sub-page Write Protection Support.
Introduction:
EPT-Based Sub-page Write Protection referred to as SPP, it is a capability which
allow Virtual Machine Monitors(VMM) to specify write-permission for guest
physical memory at a sub-page(128 byte)
Here is a patch-series which adding EPT-Based Sub-page Write Protection Support.
Introduction:
EPT-Based Sub-page Write Protection referred to as SPP, it is a capability which
allow Virtual Machine Monitors(VMM) to specify write-permission for guest
physical memory at a sub-page(128 byte)
On Fri, Nov 30, 2018 at 11:29 AM Atish Patra wrote:
>
> On 11/27/18 2:04 AM, Anup Patel wrote:
> > Currently on SMP host, all CPUs take external interrupts routed via
> > PLIC. All CPUs will try to claim a given external interrupt but only
> > one of them will succeed while other CPUs would
On Fri, Nov 30, 2018 at 11:29 AM Atish Patra wrote:
>
> On 11/27/18 2:04 AM, Anup Patel wrote:
> > Currently on SMP host, all CPUs take external interrupts routed via
> > PLIC. All CPUs will try to claim a given external interrupt but only
> > one of them will succeed while other CPUs would
Hi Rafael,
On 2018.11.23 02:36 Rafael J. Wysocki wrote:
... [snip]...
> +/**
> + * teo_find_shallower_state - Find shallower idle state matching given
> duration.
> + * @drv: cpuidle driver containing state data.
> + * @dev: Target CPU.
> + * @state_idx: Index of the capping idle state.
> + *
Hi Rafael,
On 2018.11.23 02:36 Rafael J. Wysocki wrote:
... [snip]...
> +/**
> + * teo_find_shallower_state - Find shallower idle state matching given
> duration.
> + * @drv: cpuidle driver containing state data.
> + * @dev: Target CPU.
> + * @state_idx: Index of the capping idle state.
> + *
On Thu, Nov 29, 2018 at 04:09:15PM -0700, Mathieu Poirier wrote:
> Hi Greg,
>
> On Thu, Nov 29, 2018 at 08:49:36AM +0100, Greg KH wrote:
> > On Wed, Nov 28, 2018 at 03:01:16PM -0700, Mathieu Poirier wrote:
> > > This patch uses the PMU driver configuration held in event::hw::drv_config
> > > to
On Thu, Nov 29, 2018 at 04:09:15PM -0700, Mathieu Poirier wrote:
> Hi Greg,
>
> On Thu, Nov 29, 2018 at 08:49:36AM +0100, Greg KH wrote:
> > On Wed, Nov 28, 2018 at 03:01:16PM -0700, Mathieu Poirier wrote:
> > > This patch uses the PMU driver configuration held in event::hw::drv_config
> > > to
Hi, Stephen
Best Regards!
Anson Huang
> -Original Message-
> From: Stephen Boyd [mailto:sb...@kernel.org]
> Sent: 2018年11月30日 15:25
> To: ker...@pengutronix.de; linux-arm-ker...@lists.infradead.org;
> linux-...@vger.kernel.org; linux-kernel@vger.kernel.org;
> mturque...@baylibre.com;
Hi, Stephen
Best Regards!
Anson Huang
> -Original Message-
> From: Stephen Boyd [mailto:sb...@kernel.org]
> Sent: 2018年11月30日 15:25
> To: ker...@pengutronix.de; linux-arm-ker...@lists.infradead.org;
> linux-...@vger.kernel.org; linux-kernel@vger.kernel.org;
> mturque...@baylibre.com;
On 30/11/2018 02:26, Stephen Boyd wrote:
Quoting Andreas Kemnade (2018-11-10 12:31:12)
On the gta04 with a dm3730 omap_hdq does not work properly when the
device enters lower power states. Idling uart1 and 2 is enough
to show up that problem, if there are no other things enabled.
Further
On 30/11/2018 02:26, Stephen Boyd wrote:
Quoting Andreas Kemnade (2018-11-10 12:31:12)
On the gta04 with a dm3730 omap_hdq does not work properly when the
device enters lower power states. Idling uart1 and 2 is enough
to show up that problem, if there are no other things enabled.
Further
On 30/11/2018 09:20, Stephen Boyd wrote:
Quoting Andreas Kemnade (2018-11-29 22:15:34)
Hi Stephen,
On Thu, 29 Nov 2018 16:25:05 -0800
Stephen Boyd wrote:
Quoting Andreas Kemnade (2018-11-10 12:31:14)
Code might use autoidle api with clocks not being omap2 clocks,
so check if clock type is
On 30/11/2018 09:20, Stephen Boyd wrote:
Quoting Andreas Kemnade (2018-11-29 22:15:34)
Hi Stephen,
On Thu, 29 Nov 2018 16:25:05 -0800
Stephen Boyd wrote:
Quoting Andreas Kemnade (2018-11-10 12:31:14)
Code might use autoidle api with clocks not being omap2 clocks,
so check if clock type is
The pshold block is used to drive pshold towards the PMIC, which is used
to trigger a configurable event, such as reboot or poweroff of the
QCS404 platform. Add the necessary node to enable this functionality.
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/qcs404.dtsi | 5 +
1
The pshold block is used to drive pshold towards the PMIC, which is used
to trigger a configurable event, such as reboot or poweroff of the
QCS404 platform. Add the necessary node to enable this functionality.
Signed-off-by: Bjorn Andersson
---
arch/arm64/boot/dts/qcom/qcs404.dtsi | 5 +
1
Andrew's question makes me think if this fix is superficial. Actually
i have had same question. But when i saw a smilar patch in kernel-4.4
was already merged in 2012, i decided to submit this patch first.
Here is the call stack i got:
[0.003450] [] proc_mount+0x2c/0x98
[0.003459] []
Andrew's question makes me think if this fix is superficial. Actually
i have had same question. But when i saw a smilar patch in kernel-4.4
was already merged in 2012, i decided to submit this patch first.
Here is the call stack i got:
[0.003450] [] proc_mount+0x2c/0x98
[0.003459] []
LPASS_Audio_Wrapper_AON clock is on by default. Remove
it from lpass clock list to avoid voting for it.
Signed-off-by: Rohit kumar
---
Documentation/devicetree/bindings/remoteproc/qcom,adsp-pil.txt | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git
Lpass_aon clock is on by default. Remove it from lpass
clock list to avoid voting for it.
Signed-off-by: Rohit kumar
---
drivers/remoteproc/qcom_q6v5_adsp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/remoteproc/qcom_q6v5_adsp.c
LPASS_Audio_Wrapper_AON clock is on by default. Remove
it from lpass clock list to avoid voting for it.
Signed-off-by: Rohit kumar
---
Documentation/devicetree/bindings/remoteproc/qcom,adsp-pil.txt | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git
Lpass_aon clock is on by default. Remove it from lpass
clock list to avoid voting for it.
Signed-off-by: Rohit kumar
---
drivers/remoteproc/qcom_q6v5_adsp.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/remoteproc/qcom_q6v5_adsp.c
LPASS Audio Wrapper AON clock is on by default. Remove
voting for it.
Rohit kumar (2):
dt-binding: remoteproc: Remove lpass_aon clock from adsp pil clock
list
remoteproc: q6v5_adsp: Remove voting for lpass_aon clock
Documentation/devicetree/bindings/remoteproc/qcom,adsp-pil.txt | 5
LPASS Audio Wrapper AON clock is on by default. Remove
voting for it.
Rohit kumar (2):
dt-binding: remoteproc: Remove lpass_aon clock from adsp pil clock
list
remoteproc: q6v5_adsp: Remove voting for lpass_aon clock
Documentation/devicetree/bindings/remoteproc/qcom,adsp-pil.txt | 5
On Thu 29 Nov 23:06 PST 2018, Stephen Boyd wrote:
> Quoting Bjorn Andersson (2018-11-29 22:52:58)
> > Drop the halt check of the UFS symbol clocks, in accordance with other
> > platforms. This makes clk_disable_unused() happy and makes it possible
> > to turn the clocks on again without an error.
On Thu 29 Nov 23:06 PST 2018, Stephen Boyd wrote:
> Quoting Bjorn Andersson (2018-11-29 22:52:58)
> > Drop the halt check of the UFS symbol clocks, in accordance with other
> > platforms. This makes clk_disable_unused() happy and makes it possible
> > to turn the clocks on again without an error.
Quoting Anson Huang (2018-11-29 23:23:47)
> Same as other i.MX6 SoCs, ensure unused MMDC channel's
> handshake is bypassed, this is to make sure no request
> signal will be generated when periphe_clk_sel is changed
> or SRC warm reset is triggered.
>
> Signed-off-by: Anson Huang
Does this need
Quoting Anson Huang (2018-11-29 23:23:47)
> Same as other i.MX6 SoCs, ensure unused MMDC channel's
> handshake is bypassed, this is to make sure no request
> signal will be generated when periphe_clk_sel is changed
> or SRC warm reset is triggered.
>
> Signed-off-by: Anson Huang
Does this need
On Thu 29 Nov 23:05 PST 2018, Stephen Boyd wrote:
> Quoting Bjorn Andersson (2018-11-29 22:52:57)
> > Keep the two clocks enabled, so that the platform passes
> > clk_disable_unused().
> >
> > Signed-off-by: Bjorn Andersson
> > ---
> > drivers/clk/qcom/gcc-msm8998.c | 2 ++
> > 1 file changed,
On Thu 29 Nov 23:05 PST 2018, Stephen Boyd wrote:
> Quoting Bjorn Andersson (2018-11-29 22:52:57)
> > Keep the two clocks enabled, so that the platform passes
> > clk_disable_unused().
> >
> > Signed-off-by: Bjorn Andersson
> > ---
> > drivers/clk/qcom/gcc-msm8998.c | 2 ++
> > 1 file changed,
Same as other i.MX6 SoCs, ensure unused MMDC channel's
handshake is bypassed, this is to make sure no request
signal will be generated when periphe_clk_sel is changed
or SRC warm reset is triggered.
Signed-off-by: Anson Huang
---
drivers/clk/imx/clk-imx6sl.c | 6 ++
1 file changed, 6
Same as other i.MX6 SoCs, ensure unused MMDC channel's
handshake is bypassed, this is to make sure no request
signal will be generated when periphe_clk_sel is changed
or SRC warm reset is triggered.
Signed-off-by: Anson Huang
---
drivers/clk/imx/clk-imx6sl.c | 6 ++
1 file changed, 6
Quoting Andreas Kemnade (2018-11-29 22:15:34)
> Hi Stephen,
>
> On Thu, 29 Nov 2018 16:25:05 -0800
> Stephen Boyd wrote:
>
> > Quoting Andreas Kemnade (2018-11-10 12:31:14)
> > > Code might use autoidle api with clocks not being omap2 clocks,
> > > so check if clock type is not basic
> > >
> >
Quoting Andreas Kemnade (2018-11-29 22:15:34)
> Hi Stephen,
>
> On Thu, 29 Nov 2018 16:25:05 -0800
> Stephen Boyd wrote:
>
> > Quoting Andreas Kemnade (2018-11-10 12:31:14)
> > > Code might use autoidle api with clocks not being omap2 clocks,
> > > so check if clock type is not basic
> > >
> >
On 29. 11. 18 17:15, Faiz Abbas wrote:
> The "ti,am654-sdhci-5.1" binding has been moved to a new driver. Indicate
> this by a deprecated message.
>
> Signed-off-by: Faiz Abbas
> ---
> Documentation/devicetree/bindings/mmc/arasan,sdhci.txt | 4
> 1 file changed, 4 insertions(+)
>
> diff
On 29. 11. 18 17:15, Faiz Abbas wrote:
> The "ti,am654-sdhci-5.1" binding has been moved to a new driver. Indicate
> this by a deprecated message.
>
> Signed-off-by: Faiz Abbas
> ---
> Documentation/devicetree/bindings/mmc/arasan,sdhci.txt | 4
> 1 file changed, 4 insertions(+)
>
> diff
On Fri, Nov 30, 2018 at 03:54:48AM +0530, Harsh Shandilya wrote:
> On 29 November 2018 7:41:31 PM IST, Greg Kroah-Hartman
> wrote:
> >This is the start of the stable review cycle for the 4.19.6 release.
> >There are 110 patches in this series, all will be posted as a response
> >to this one. If
On Fri, Nov 30, 2018 at 03:54:48AM +0530, Harsh Shandilya wrote:
> On 29 November 2018 7:41:31 PM IST, Greg Kroah-Hartman
> wrote:
> >This is the start of the stable review cycle for the 4.19.6 release.
> >There are 110 patches in this series, all will be posted as a response
> >to this one. If
On Thu, Nov 29, 2018 at 01:36:14PM -0700, shuah wrote:
> On 11/29/18 7:11 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.19.6 release.
> > There are 110 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues
On Thu, Nov 29, 2018 at 01:36:14PM -0700, shuah wrote:
> On 11/29/18 7:11 AM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 4.19.6 release.
> > There are 110 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues
On Thu, 29 Nov 2018 at 19:56, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.85 release.
> There are 100 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
On Thu, 29 Nov 2018 at 19:56, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.14.85 release.
> There are 100 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
On Thu 29 Nov 13:45 PST 2018, Lina Iyer wrote:
> On Wed, Nov 28 2018 at 17:25 -0700, Bjorn Andersson wrote:
> > On Wed 28 Nov 09:39 PST 2018, Lina Iyer wrote:
> >
> > > On Tue, Nov 27 2018 at 14:45 -0700, Stephen Boyd wrote:
> > > > Quoting Lina Iyer (2018-11-27 10:21:23)
> > > > > On Tue, Nov
On Thu 29 Nov 13:45 PST 2018, Lina Iyer wrote:
> On Wed, Nov 28 2018 at 17:25 -0700, Bjorn Andersson wrote:
> > On Wed 28 Nov 09:39 PST 2018, Lina Iyer wrote:
> >
> > > On Tue, Nov 27 2018 at 14:45 -0700, Stephen Boyd wrote:
> > > > Quoting Lina Iyer (2018-11-27 10:21:23)
> > > > > On Tue, Nov
On Thu, 29 Nov 2018 at 19:51, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.142 release.
> There are 92 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
On Thu, 29 Nov 2018 at 19:51, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.9.142 release.
> There are 92 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
>
Quoting Bjorn Andersson (2018-11-29 22:52:58)
> Drop the halt check of the UFS symbol clocks, in accordance with other
> platforms. This makes clk_disable_unused() happy and makes it possible
> to turn the clocks on again without an error.
>
> Signed-off-by: Bjorn Andersson
Someone was supposed
Quoting Bjorn Andersson (2018-11-29 22:52:58)
> Drop the halt check of the UFS symbol clocks, in accordance with other
> platforms. This makes clk_disable_unused() happy and makes it possible
> to turn the clocks on again without an error.
>
> Signed-off-by: Bjorn Andersson
Someone was supposed
Quoting Bjorn Andersson (2018-11-29 22:52:57)
> Keep the two clocks enabled, so that the platform passes
> clk_disable_unused().
>
> Signed-off-by: Bjorn Andersson
> ---
> drivers/clk/qcom/gcc-msm8998.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/clk/qcom/gcc-msm8998.c
Quoting Bjorn Andersson (2018-11-29 22:52:57)
> Keep the two clocks enabled, so that the platform passes
> clk_disable_unused().
>
> Signed-off-by: Bjorn Andersson
> ---
> drivers/clk/qcom/gcc-msm8998.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/clk/qcom/gcc-msm8998.c
Quoting Rob Herring (2018-11-29 17:01:54)
> On Thu, Nov 29, 2018 at 6:28 PM Stephen Boyd wrote:
> >
> > Quoting Stephen Boyd (2018-11-07 10:37:31)
> > > appropriate structure with to_platform_device() or to_i2c_client()?
> > >
> > > So the example would become
> > >
> > > struct
Quoting Rob Herring (2018-11-29 17:01:54)
> On Thu, Nov 29, 2018 at 6:28 PM Stephen Boyd wrote:
> >
> > Quoting Stephen Boyd (2018-11-07 10:37:31)
> > > appropriate structure with to_platform_device() or to_i2c_client()?
> > >
> > > So the example would become
> > >
> > > struct
>From b893df3a1a937bd5fe22d39ceae93454a2e5e0e4 Mon Sep 17 00:00:00 2001
From: Alek Du
Date: Fri, 30 Nov 2018 14:02:28 +0800
Subject: [PATCH] sdhci: fix the fake timeout bug
We observed some fake timeouts on some devices, the log is like this:
[ 7586.290201] mmc1: Timeout waiting for hardware
>From b893df3a1a937bd5fe22d39ceae93454a2e5e0e4 Mon Sep 17 00:00:00 2001
From: Alek Du
Date: Fri, 30 Nov 2018 14:02:28 +0800
Subject: [PATCH] sdhci: fix the fake timeout bug
We observed some fake timeouts on some devices, the log is like this:
[ 7586.290201] mmc1: Timeout waiting for hardware
The scm binding and driver was updated to rely on the fallback to the
default qcom,scm for any modern SoC and as such both are required. Add
the default compatible to make the scm instance probe.
Fixes: d850156a226a ("arm64: dts: qcom: msm8998: Add firmware node")
Signed-off-by: Bjorn Andersson
The scm binding and driver was updated to rely on the fallback to the
default qcom,scm for any modern SoC and as such both are required. Add
the default compatible to make the scm instance probe.
Fixes: d850156a226a ("arm64: dts: qcom: msm8998: Add firmware node")
Signed-off-by: Bjorn Andersson
Enable the GCC and PINCTRL for MSM8998 to make upstream boot to console.
Signed-off-by: Bjorn Andersson
---
arch/arm64/configs/defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 1f1f4eab89df..206f50d121ba 100644
---
Enable the GCC and PINCTRL for MSM8998 to make upstream boot to console.
Signed-off-by: Bjorn Andersson
---
arch/arm64/configs/defconfig | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index 1f1f4eab89df..206f50d121ba 100644
---
Quoting Ryder Lee (2018-11-05 00:43:56)
> This patch adds the binding documentation for apmixedsys, infracfg,
> pciesys, pericfg, topckgen, ethsys, sgmiisys and ssusbsys for MT7629.
>
> Signed-off-by: Ryder Lee
> ---
Applied to clk-next
Quoting Ryder Lee (2018-11-05 00:43:56)
> This patch adds the binding documentation for apmixedsys, infracfg,
> pciesys, pericfg, topckgen, ethsys, sgmiisys and ssusbsys for MT7629.
>
> Signed-off-by: Ryder Lee
> ---
Applied to clk-next
Quoting Ryder Lee (2018-11-05 00:43:55)
> Add all supported clocks exported from every susbystem found on MT7629 SoC.
>
> Signed-off-by: Wenzhen Yu
> Signed-off-by: Ryder Lee
> ---
Applied to clk-next
On 30/11/2018 07:44, kbuild test robot wrote:
> Hi Juergen,
>
> FYI, the error/warning still remains.
This problem is one of gcc. It is in no way the (direct) result of my
patch. Please see my gcc bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908154
Juergen
>
> tree:
On Thu, Nov 29, 2018 at 11:13:57PM -0600, Eric W. Biederman wrote:
> Arnd Bergmann writes:
>
> > On Thu, Nov 29, 2018 at 9:14 PM Andy Lutomirski wrote:
> >> > On Nov 29, 2018, at 11:55 AM, Christian Brauner
> >> > wrote:
> >> >> On Thu, Nov 29, 2018 at 11:22:58AM -0800, Andy Lutomirski wrote:
Quoting Ryder Lee (2018-11-05 00:43:55)
> Add all supported clocks exported from every susbystem found on MT7629 SoC.
>
> Signed-off-by: Wenzhen Yu
> Signed-off-by: Ryder Lee
> ---
Applied to clk-next
On 30/11/2018 07:44, kbuild test robot wrote:
> Hi Juergen,
>
> FYI, the error/warning still remains.
This problem is one of gcc. It is in no way the (direct) result of my
patch. Please see my gcc bug report:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=908154
Juergen
>
> tree:
On Thu, Nov 29, 2018 at 11:13:57PM -0600, Eric W. Biederman wrote:
> Arnd Bergmann writes:
>
> > On Thu, Nov 29, 2018 at 9:14 PM Andy Lutomirski wrote:
> >> > On Nov 29, 2018, at 11:55 AM, Christian Brauner
> >> > wrote:
> >> >> On Thu, Nov 29, 2018 at 11:22:58AM -0800, Andy Lutomirski wrote:
Drop the halt check of the UFS symbol clocks, in accordance with other
platforms. This makes clk_disable_unused() happy and makes it possible
to turn the clocks on again without an error.
Signed-off-by: Bjorn Andersson
---
drivers/clk/qcom/gcc-msm8998.c | 6 +++---
1 file changed, 3
Drop the halt check of the UFS symbol clocks, in accordance with other
platforms. This makes clk_disable_unused() happy and makes it possible
to turn the clocks on again without an error.
Signed-off-by: Bjorn Andersson
---
drivers/clk/qcom/gcc-msm8998.c | 6 +++---
1 file changed, 3
Add clkref clocks for usb3, hdmi, ufs, pcie, and usb2. They are all
sourced off CXO_IN, so parent them off "xo" until a proper link to the
rpmcc can be described in DT.
Signed-off-by: Bjorn Andersson
---
drivers/clk/qcom/gcc-msm8998.c | 75
Keep the two clocks enabled, so that the platform passes
clk_disable_unused().
Signed-off-by: Bjorn Andersson
---
drivers/clk/qcom/gcc-msm8998.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/clk/qcom/gcc-msm8998.c b/drivers/clk/qcom/gcc-msm8998.c
index 9f0ae403d5f5..d89f8e7c2a59
Mark critical clocks critical, don't halt-check UFS clocks and add clkref
branches.
Bjorn Andersson (3):
clk: qcom: gcc-msm8998: Mark hmss_dvm and lpass_at critical
clk: qcom: gcc-msm8998: Disable halt check of UFS clocks
clk: qcom: gcc-msm8998: Add clkref clocks
Add clkref clocks for usb3, hdmi, ufs, pcie, and usb2. They are all
sourced off CXO_IN, so parent them off "xo" until a proper link to the
rpmcc can be described in DT.
Signed-off-by: Bjorn Andersson
---
drivers/clk/qcom/gcc-msm8998.c | 75
Keep the two clocks enabled, so that the platform passes
clk_disable_unused().
Signed-off-by: Bjorn Andersson
---
drivers/clk/qcom/gcc-msm8998.c | 2 ++
1 file changed, 2 insertions(+)
diff --git a/drivers/clk/qcom/gcc-msm8998.c b/drivers/clk/qcom/gcc-msm8998.c
index 9f0ae403d5f5..d89f8e7c2a59
Mark critical clocks critical, don't halt-check UFS clocks and add clkref
branches.
Bjorn Andersson (3):
clk: qcom: gcc-msm8998: Mark hmss_dvm and lpass_at critical
clk: qcom: gcc-msm8998: Disable halt check of UFS clocks
clk: qcom: gcc-msm8998: Add clkref clocks
Quoting matthias@kernel.org (2018-11-16 10:09:00)
> From: Jasper Mattsson
>
> This is required to mark gates as CLK_IS_CRITICAL.
>
> Fixes: 96596aa06628 ("clk: mediatek: add clk support for MT6797")
> Signed-off-by: Jasper Mattsson
> Signed-off-by: Matthias Brugger
> ---
These other two
Quoting matthias@kernel.org (2018-11-16 10:09:00)
> From: Jasper Mattsson
>
> This is required to mark gates as CLK_IS_CRITICAL.
>
> Fixes: 96596aa06628 ("clk: mediatek: add clk support for MT6797")
> Signed-off-by: Jasper Mattsson
> Signed-off-by: Matthias Brugger
> ---
These other two
Quoting matthias@kernel.org (2018-11-16 10:09:01)
> From: Jasper Mattsson
>
> This marks MUXes axi_sel and ddrphycfg_sel as well as gates
> infra_dramc_f26m and infra_dramc_b_f26m as with CLK_IS_CRITICAL.
>
> Fixes: 96596aa06628 ("clk: mediatek: add clk support for MT6797")
> Signed-off-by:
> +
> +/*
> + * USBSS-DEV register interface.
> + * This corresponds to the USBSS Device Controller Interface */
> +/**
> + * struct xhci_cap_regs - xHCI Host Controller Capability Registers.
struct cdns3_usb_regs - device controller registers
> +struct cdns3_device;
> +
> +struct
Quoting matthias@kernel.org (2018-11-16 10:09:01)
> From: Jasper Mattsson
>
> This marks MUXes axi_sel and ddrphycfg_sel as well as gates
> infra_dramc_f26m and infra_dramc_b_f26m as with CLK_IS_CRITICAL.
>
> Fixes: 96596aa06628 ("clk: mediatek: add clk support for MT6797")
> Signed-off-by:
> +
> +/*
> + * USBSS-DEV register interface.
> + * This corresponds to the USBSS Device Controller Interface */
> +/**
> + * struct xhci_cap_regs - xHCI Host Controller Capability Registers.
struct cdns3_usb_regs - device controller registers
> +struct cdns3_device;
> +
> +struct
The ASUS laptops start to support the airplane mode radio management
to replace the original machanism of airplane mode toggle hotkey.
On the ASUS P5440FF, it presents as a HID device connecting via
I2C, name i2c-AMPD0001. When pressing hotkey, the Embedded Controller
send hid report up via I2C
The ASUS laptops start to support the airplane mode radio management
to replace the original machanism of airplane mode toggle hotkey.
On the ASUS P5440FF, it presents as a HID device connecting via
I2C, name i2c-AMPD0001. When pressing hotkey, the Embedded Controller
send hid report up via I2C
Quoting matthias@kernel.org (2018-11-16 10:08:58)
> From: Matthias Brugger
>
> Jasper send this series some month ago. As there was no reaction from
> his side, I'll do a friendly take-over.
> I tested the patches on my Helios X20 boards and they fix the issue.
> I didn't add a Tested-by tag
Quoting matthias@kernel.org (2018-11-16 10:08:58)
> From: Matthias Brugger
>
> Jasper send this series some month ago. As there was no reaction from
> his side, I'll do a friendly take-over.
> I tested the patches on my Helios X20 boards and they fix the issue.
> I didn't add a Tested-by tag
Hi Juergen,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 94f371cb73944b410a269d570d6946c042f2ddd0
commit: 6da63eb241a05b0e676d68975e793c0521387141 x86/paravirt: Move the
pv_irq_ops under the PARAVIRT_XXL
Hi Juergen,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: 94f371cb73944b410a269d570d6946c042f2ddd0
commit: 6da63eb241a05b0e676d68975e793c0521387141 x86/paravirt: Move the
pv_irq_ops under the PARAVIRT_XXL
On Fri, Nov 30, 2018 at 09:15:13AM +0800, Chao Fan wrote:
>On Thu, Nov 29, 2018 at 12:32:46PM -0500, Masayoshi Mizuma wrote:
>>Hi Chao,
>>
>>Thank you for your continued working.
>
>Thanks for your test.
>
>>
>>Could you please build your patches before sending?
>
>Sorry for the mistake, I build
On Wed, Nov 28, 2018 at 10:12 PM Malathi Gottam wrote:
>
> This adds video nodes to sdm845 based on the examples
> in the bindings.
>
> Signed-off-by: Malathi Gottam
> ---
> arch/arm64/boot/dts/qcom/sdm845.dtsi | 35 +++
> 1 file changed, 35 insertions(+)
>
>
On Fri, Nov 30, 2018 at 09:15:13AM +0800, Chao Fan wrote:
>On Thu, Nov 29, 2018 at 12:32:46PM -0500, Masayoshi Mizuma wrote:
>>Hi Chao,
>>
>>Thank you for your continued working.
>
>Thanks for your test.
>
>>
>>Could you please build your patches before sending?
>
>Sorry for the mistake, I build
On Wed, Nov 28, 2018 at 10:12 PM Malathi Gottam wrote:
>
> This adds video nodes to sdm845 based on the examples
> in the bindings.
>
> Signed-off-by: Malathi Gottam
> ---
> arch/arm64/boot/dts/qcom/sdm845.dtsi | 35 +++
> 1 file changed, 35 insertions(+)
>
>
1 - 100 of 2748 matches
Mail list logo
