Hi Linus
There is one arch/nios2 update for v4.19-rc2.
Please consider pulling.
Regards
Ley Foon
The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
are available in the git repository at:
Hi Linus
There is one arch/nios2 update for v4.19-rc2.
Please consider pulling.
Regards
Ley Foon
The following changes since commit 5b394b2ddf0347bef56e50c69a58773c94343ff3:
Linux 4.19-rc1 (2018-08-26 14:11:59 -0700)
are available in the git repository at:
From: Wanpeng Li
Dan Carpenter reported that the untrusted data returns from kvm_register_read()
results in the following static checker warning:
arch/x86/kvm/lapic.c:576 kvm_pv_send_ipi()
error: buffer underflow 'map->phys_map' 's32min-s32max'
KVM guest can easily trigger this by executing
From: Wanpeng Li
Dan Carpenter reported that the untrusted data returns from kvm_register_read()
results in the following static checker warning:
arch/x86/kvm/lapic.c:576 kvm_pv_send_ipi()
error: buffer underflow 'map->phys_map' 's32min-s32max'
KVM guest can easily trigger this by executing
From: Wanpeng Li
Dan Carpenter reported that the untrusted data returns from kvm_register_read()
results in the following static checker warning:
arch/x86/kvm/lapic.c:576 kvm_pv_send_ipi()
error: buffer underflow 'map->phys_map' 's32min-s32max'
KVM guest can easily trigger this by executing
From: Wanpeng Li
Dan Carpenter reported that the untrusted data returns from kvm_register_read()
results in the following static checker warning:
arch/x86/kvm/lapic.c:576 kvm_pv_send_ipi()
error: buffer underflow 'map->phys_map' 's32min-s32max'
KVM guest can easily trigger this by executing
Some i.MX platforms like i.MX7S/D uses generic ARM cpuidle
driver and psci method to support cpuidle feature, select
CONFIG_ARM_CPUIDLE by default for such platforms.
Signed-off-by: Anson Huang
---
arch/arm/configs/imx_v6_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
Some i.MX platforms like i.MX7S/D uses generic ARM cpuidle
driver and psci method to support cpuidle feature, select
CONFIG_ARM_CPUIDLE by default for such platforms.
Signed-off-by: Anson Huang
---
arch/arm/configs/imx_v6_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git
Enable cpuidle for i.MX7S/D using generic ARM cpuidle
driver, below 2 idle states enabled:
1. ARM WFI;
2. SoC WAIT mode.
Signed-off-by: Anson Huang
---
arch/arm/boot/dts/imx7d.dtsi | 1 +
arch/arm/boot/dts/imx7s.dtsi | 14 ++
2 files changed, 15 insertions(+)
diff --git
Enable cpuidle for i.MX7S/D using generic ARM cpuidle
driver, below 2 idle states enabled:
1. ARM WFI;
2. SoC WAIT mode.
Signed-off-by: Anson Huang
---
arch/arm/boot/dts/imx7d.dtsi | 1 +
arch/arm/boot/dts/imx7s.dtsi | 14 ++
2 files changed, 15 insertions(+)
diff --git
Hi Julien,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.19-rc1 next-20180828]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day
Hi Julien,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linus/master]
[also build test WARNING on v4.19-rc1 next-20180828]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day
Hi,
Cc-ing Benjamin on this.
On (08/29/18 03:23), Dmitry Safonov wrote:
> BUG: unable to handle kernel paging request at 2260
> IP: [..] n_tty_receive_buf_common+0x5f/0x86d
> Workqueue: events_unbound flush_to_ldisc
> Call Trace:
> [..] n_tty_receive_buf2
> [..]
Hi,
Cc-ing Benjamin on this.
On (08/29/18 03:23), Dmitry Safonov wrote:
> BUG: unable to handle kernel paging request at 2260
> IP: [..] n_tty_receive_buf_common+0x5f/0x86d
> Workqueue: events_unbound flush_to_ldisc
> Call Trace:
> [..] n_tty_receive_buf2
> [..]
On 8/29/2018 3:59 AM, Stephen Boyd wrote:
> Quoting Akshu Agrawal (2018-08-20 23:51:57)
>> System clk provided in ST soc can be set to:
>> 48Mhz, non-spread
>> 25Mhz, spread
>> To get accurate rate, we need it to set it at non-spread
>> option which is 48Mhz.
>>
>> Signed-off-by: Akshu Agrawal
On 8/29/2018 3:59 AM, Stephen Boyd wrote:
> Quoting Akshu Agrawal (2018-08-20 23:51:57)
>> System clk provided in ST soc can be set to:
>> 48Mhz, non-spread
>> 25Mhz, spread
>> To get accurate rate, we need it to set it at non-spread
>> option which is 48Mhz.
>>
>> Signed-off-by: Akshu Agrawal
On Sunday, August 26, 2018 9:37:09 PM CEST Doug Smythies wrote:
> On 2018.08.25 04:22 Rafael J. Wysocki wrote:
> > On Fri, Aug 24, 2018 at 5:52 PM Doug Smythies wrote:
> >> On 2018.08.24 02:44 Rafael J. Wysocki wrote:
> >>> On Tuesday, August 21, 2018 10:44:10 AM CEST Rafael J. Wysocki wrote:
>
On Sunday, August 26, 2018 9:37:09 PM CEST Doug Smythies wrote:
> On 2018.08.25 04:22 Rafael J. Wysocki wrote:
> > On Fri, Aug 24, 2018 at 5:52 PM Doug Smythies wrote:
> >> On 2018.08.24 02:44 Rafael J. Wysocki wrote:
> >>> On Tuesday, August 21, 2018 10:44:10 AM CEST Rafael J. Wysocki wrote:
>
The 'm' kcore_list item can point to kclist_head, and it is incorrect to
look at m->addr / m->size in this case.
There is no choice but to run through the list of entries for every address
if we did not find any entry in the previous iteration
Fixes: bf991c2231117 ("proc/kcore: optimize multiple
The 'm' kcore_list item can point to kclist_head, and it is incorrect to
look at m->addr / m->size in this case.
There is no choice but to run through the list of entries for every address
if we did not find any entry in the previous iteration
Fixes: bf991c2231117 ("proc/kcore: optimize multiple
On 28-08-18, 14:03, Radhey Shyam Pandey wrote:
> > On 27-07-18, 16:20, Radhey Shyam Pandey wrote:
> > > In AXI CDMA simple mode also pass MSB bits of source and destination
> > > address to xilinx_write function. This fixes simple CDMA operation
> > > mode using 64-bit addressing.
> > >
> > >
On 28-08-18, 14:03, Radhey Shyam Pandey wrote:
> > On 27-07-18, 16:20, Radhey Shyam Pandey wrote:
> > > In AXI CDMA simple mode also pass MSB bits of source and destination
> > > address to xilinx_write function. This fixes simple CDMA operation
> > > mode using 64-bit addressing.
> > >
> > >
On Tue, Aug 28, 2018 at 10:56 AM, Rik van Riel wrote:
> On Mon, 27 Aug 2018 16:04:16 -0700
> Andy Lutomirski wrote:
>
>> The 0day bot is still chewing on this, but I've tested it a bit locally
>> and it seems to do the right thing.
>
> Hi Andy,
>
> the version of the patch below should fix the
On Tue, Aug 28, 2018 at 10:56 AM, Rik van Riel wrote:
> On Mon, 27 Aug 2018 16:04:16 -0700
> Andy Lutomirski wrote:
>
>> The 0day bot is still chewing on this, but I've tested it a bit locally
>> and it seems to do the right thing.
>
> Hi Andy,
>
> the version of the patch below should fix the
On Tue, Aug 28, 2018 at 6:46 PM, Nadav Amit wrote:
> Hello Andy,
>
> Is there a reason for __flush_tlb_one_kernel() to flush the PTE not only in
> the kernel address space, but also in the user one (as part of
> __flush_tlb_one_user)? [ I obviously regard the case when PTI is on ].
In most
On Tue, Aug 28, 2018 at 6:46 PM, Nadav Amit wrote:
> Hello Andy,
>
> Is there a reason for __flush_tlb_one_kernel() to flush the PTE not only in
> the kernel address space, but also in the user one (as part of
> __flush_tlb_one_user)? [ I obviously regard the case when PTI is on ].
In most
Hi all,
Changes since 20180828:
Removed tree: libata (merged into the block tree)
Dropped trees: xarray, ida (temporarily)
The spi tree gained a build failure so I used the version from
next-20180828.
Non-merge commits (relative to Linus' tree): 875
1002 files changed, 29529 insertions
Hi all,
Changes since 20180828:
Removed tree: libata (merged into the block tree)
Dropped trees: xarray, ida (temporarily)
The spi tree gained a build failure so I used the version from
next-20180828.
Non-merge commits (relative to Linus' tree): 875
1002 files changed, 29529 insertions
From: Rajesh Bhagat
Add "configure-gfladj" boolean property to USB3 node. This property
is used to determine whether frame length adjustment is required or
not
Signed-off-by: Rajesh Bhagat
Signed-off-by: Ran Wang
Signed-off-by: Yinbo Zhu
---
Change in v2:
Modified some word
From: Rajesh Bhagat
Add "configure-gfladj" boolean property to USB3 node. This property
is used to determine whether frame length adjustment is required or
not
Signed-off-by: Rajesh Bhagat
Signed-off-by: Ran Wang
Signed-off-by: Yinbo Zhu
---
Change in v2:
Modified some word
Hi Julien,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.19-rc1 next-20180828]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Hi Julien,
Thank you for the patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.19-rc1 next-20180828]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
Add display ports for display-subsystem and add reset property
for vop node, if missing this two define, drm driver can't
probe sucess.
Signed-off-by: Sandy Huang
---
arch/arm64/boot/dts/rockchip/px30.dtsi | 13 +
1 file changed, 13 insertions(+)
diff --git
Add display ports for display-subsystem and add reset property
for vop node, if missing this two define, drm driver can't
probe sucess.
Signed-off-by: Sandy Huang
---
arch/arm64/boot/dts/rockchip/px30.dtsi | 13 +
1 file changed, 13 insertions(+)
diff --git
When programming inbound/outbound atu, we call usleep_range() after
each checking PCIE_ATU_ENABLE bit. Unfortunately, the atu programming
can be called in atomic context:
inbound atu programming could be called through
pci_epc_write_header()
=>dw_pcie_ep_write_header()
When programming inbound/outbound atu, we call usleep_range() after
each checking PCIE_ATU_ENABLE bit. Unfortunately, the atu programming
can be called in atomic context:
inbound atu programming could be called through
pci_epc_write_header()
=>dw_pcie_ep_write_header()
Quoting A.s. Dong (2018-08-16 19:33:52)
> Hi Stephen,
>
> Do you want me to resend this series for review?
> It seems have been pending for quite a long time.
>
> Thor just pinged me for its status as he wants to use it.
>
I was waiting for someone to try them out or review them. Good that it
Quoting A.s. Dong (2018-08-16 19:33:52)
> Hi Stephen,
>
> Do you want me to resend this series for review?
> It seems have been pending for quite a long time.
>
> Thor just pinged me for its status as he wants to use it.
>
I was waiting for someone to try them out or review them. Good that it
On Tue, Aug 28, 2018 at 04:34:04PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Since this header is in "include/uapi/linux/", apparently people
> want to use it in userspace programs -- even in C++ ones.
> However, the header uses a C++ reserved keyword ("private"),
> so change that to
On Tue, Aug 28, 2018 at 04:34:04PM -0700, Randy Dunlap wrote:
> From: Randy Dunlap
>
> Since this header is in "include/uapi/linux/", apparently people
> want to use it in userspace programs -- even in C++ ones.
> However, the header uses a C++ reserved keyword ("private"),
> so change that to
Hi,
I am doing the following simple collection with callchain and load profiling:
$ perf record -g -d -e cpu/event=0xd0,umask=0x81/pp my_test_program
But when I type:
$ perf script -F ip,addr
9d4821346878
9d58df25
9d58e054
9d5965bb
Hi,
I am doing the following simple collection with callchain and load profiling:
$ perf record -g -d -e cpu/event=0xd0,umask=0x81/pp my_test_program
But when I type:
$ perf script -F ip,addr
9d4821346878
9d58df25
9d58e054
9d5965bb
It's safe to not lock both here - done to silence attempt lockdep assert in
tty_ldisc_open(), which will be added with following patch.
Cc: Greg Kroah-Hartman
Cc: Jiri Slaby
Signed-off-by: Dmitry Safonov
---
drivers/tty/tty_io.c| 5 ++---
drivers/tty/tty_ldisc.c | 6 ++
It's safe to not lock both here - done to silence attempt lockdep assert in
tty_ldisc_open(), which will be added with following patch.
Cc: Greg Kroah-Hartman
Cc: Jiri Slaby
Signed-off-by: Dmitry Safonov
---
drivers/tty/tty_io.c| 5 ++---
drivers/tty/tty_ldisc.c | 6 ++
Two fixes for potential and real issues.
Looks worth to have in stables as we've hit it on v4.9 stable.
And for linux-next - adding lockdep asserts for line discipline changing
code, verifying that write ldisc sem will be held forthwith.
I couldn't verify that holding write lock fixes the issue
It should nicely document that each change to line discipline should
held write semaphor. Otherwise potential reader will have a good time.
Cc: Greg Kroah-Hartman
Cc: Jiri Slaby
Signed-off-by: Dmitry Safonov
---
drivers/tty/tty_ldisc.c | 6 ++
1 file changed, 6 insertions(+)
diff --git
tty_ldisc_reinit() doesn't race with neither tty_ldisc_hangup()
nor set_ldisc() nor tty_ldisc_release() as they use tty lock.
But it races with anyone who expects line discipline to be the same
after hoding read semaphore in tty_ldisc_ref().
We've seen the following crash on v4.9.108 stable:
In case of tty_ldisc_reinit() failure, tty->count should be decremented
back, otherwise we will never release_tty().
Never seen it in the real life, but it seems not really hard to hit.
Cc: Greg Kroah-Hartman
Cc: Jiri Slaby
Cc: sta...@vger.kernel.org
Signed-off-by: Dmitry Safonov
---
Two fixes for potential and real issues.
Looks worth to have in stables as we've hit it on v4.9 stable.
And for linux-next - adding lockdep asserts for line discipline changing
code, verifying that write ldisc sem will be held forthwith.
I couldn't verify that holding write lock fixes the issue
It should nicely document that each change to line discipline should
held write semaphor. Otherwise potential reader will have a good time.
Cc: Greg Kroah-Hartman
Cc: Jiri Slaby
Signed-off-by: Dmitry Safonov
---
drivers/tty/tty_ldisc.c | 6 ++
1 file changed, 6 insertions(+)
diff --git
tty_ldisc_reinit() doesn't race with neither tty_ldisc_hangup()
nor set_ldisc() nor tty_ldisc_release() as they use tty lock.
But it races with anyone who expects line discipline to be the same
after hoding read semaphore in tty_ldisc_ref().
We've seen the following crash on v4.9.108 stable:
In case of tty_ldisc_reinit() failure, tty->count should be decremented
back, otherwise we will never release_tty().
Never seen it in the real life, but it seems not really hard to hit.
Cc: Greg Kroah-Hartman
Cc: Jiri Slaby
Cc: sta...@vger.kernel.org
Signed-off-by: Dmitry Safonov
---
In memory KASLR, __PHYSICAL_MASK_SHIFT is taken to calculate the
initial size of the direct mapping region. This is right in the
old code where __PHYSICAL_MASK_SHIFT was equal to MAX_PHYSMEM_BITS,
46bit, and only 4-level mode was supported.
Later, in commit:
b83ce5ee91471d ("x86/mm/64: Make
In memory KASLR, __PHYSICAL_MASK_SHIFT is taken to calculate the
initial size of the direct mapping region. This is right in the
old code where __PHYSICAL_MASK_SHIFT was equal to MAX_PHYSMEM_BITS,
46bit, and only 4-level mode was supported.
Later, in commit:
b83ce5ee91471d ("x86/mm/64: Make
Vmemmap area has different base and size depending on paging mode.
Now we just hardcode its size as 1TB in memory KASLR, it's not
right for 5-level paging mode.
Adjust it according to paging mode and use it during memory KASLR.
Signed-off-by: Baoquan He
---
Vmemmap area has different base and size depending on paging mode.
Now we just hardcode its size as 1TB in memory KASLR, it's not
right for 5-level paging mode.
Adjust it according to paging mode and use it during memory KASLR.
Signed-off-by: Baoquan He
---
On Tue, Aug 28, 2018 at 9:55 AM Rob Herring wrote:
>
> In preparation to remove the node name pointer from struct device_node,
> convert printf users to use the %pOFn format specifier.
>
> Cc: Linus Walleij
> Cc: Dong Aisheng
> Cc: Fabio Estevam
> Cc: Shawn Guo
> Cc: Stefan Agner
> Cc:
On Tue, Aug 28, 2018 at 9:55 AM Rob Herring wrote:
>
> In preparation to remove the node name pointer from struct device_node,
> convert printf users to use the %pOFn format specifier.
>
> Cc: Linus Walleij
> Cc: Dong Aisheng
> Cc: Fabio Estevam
> Cc: Shawn Guo
> Cc: Stefan Agner
> Cc:
On Mon, 2018-08-27 at 20:52 -0500, Rob Herring wrote:
> In preparation to remove the node name pointer from struct device_node,
> convert printf users to use the %pOFn format specifier.
>
> Cc: Linus Walleij
> Cc: Dong Aisheng
> Cc: Fabio Estevam
> Cc: Shawn Guo
> Cc: Stefan Agner
> Cc:
On Mon, 2018-08-27 at 20:52 -0500, Rob Herring wrote:
> In preparation to remove the node name pointer from struct device_node,
> convert printf users to use the %pOFn format specifier.
>
> Cc: Linus Walleij
> Cc: Dong Aisheng
> Cc: Fabio Estevam
> Cc: Shawn Guo
> Cc: Stefan Agner
> Cc:
Arnd Bergmann 於 2018年8月24日 週五 下午8:48寫道：
>
> On Fri, Aug 24, 2018 at 10:23 AM Masami Hiramatsu wrote:
> >
> > On Fri, 24 Aug 2018 13:32:06 +1000
> > Stephen Rothwell wrote:
> >
> > > Hi all,
> > >
> > > After merging the origin tree, today's linux-next build (powerpc
> > > allyesconfig) produced
Arnd Bergmann 於 2018年8月24日 週五 下午8:48寫道：
>
> On Fri, Aug 24, 2018 at 10:23 AM Masami Hiramatsu wrote:
> >
> > On Fri, 24 Aug 2018 13:32:06 +1000
> > Stephen Rothwell wrote:
> >
> > > Hi all,
> > >
> > > After merging the origin tree, today's linux-next build (powerpc
> > > allyesconfig) produced
> Dear Rob,
>
> On 2018년 08월 28일 10:52, Rob Herring wrote:
> > In preparation to remove the node name pointer from struct device_node,
> > convert printf users to use the %pOFn format specifier.
> >
> > Cc: Chanwoo Choi
> > Cc: MyungJoo Ham
> > Cc: Kyungmin Park
> > Cc: Kukjin Kim
> > Cc:
> Dear Rob,
>
> On 2018년 08월 28일 10:52, Rob Herring wrote:
> > In preparation to remove the node name pointer from struct device_node,
> > convert printf users to use the %pOFn format specifier.
> >
> > Cc: Chanwoo Choi
> > Cc: MyungJoo Ham
> > Cc: Kyungmin Park
> > Cc: Kukjin Kim
> > Cc:
On 08/23/2018 07:22 PM, Andre Tomt wrote:
> On 23. aug. 2018 17:44, Andi Kleen wrote:
>> On Thu, Aug 23, 2018 at 03:44:18PM +0200, Vlastimil Babka wrote:
>>> Two users have reported [1] that they have an "extremely unlikely"
>>> system
>>> with more than MAX_PA/2 memory and L1TF mitigation is
On 08/23/2018 07:22 PM, Andre Tomt wrote:
> On 23. aug. 2018 17:44, Andi Kleen wrote:
>> On Thu, Aug 23, 2018 at 03:44:18PM +0200, Vlastimil Babka wrote:
>>> Two users have reported [1] that they have an "extremely unlikely"
>>> system
>>> with more than MAX_PA/2 memory and L1TF mitigation is
This patch enables i.MX7D SDB board's below GPIO buttons
as wakeup sources:
S1(FUNC1): KEY_VOLUMEUP
S3(FUNC2): KEY_VOLUMEDOWN
Signed-off-by: Anson Huang
---
arch/arm/boot/dts/imx7d-sdb.dts | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/imx7d-sdb.dts
This patch enables i.MX7D SDB board's below GPIO buttons
as wakeup sources:
S1(FUNC1): KEY_VOLUMEUP
S3(FUNC2): KEY_VOLUMEDOWN
Signed-off-by: Anson Huang
---
arch/arm/boot/dts/imx7d-sdb.dts | 2 ++
1 file changed, 2 insertions(+)
diff --git a/arch/arm/boot/dts/imx7d-sdb.dts
Hello Andy,
Is there a reason for __flush_tlb_one_kernel() to flush the PTE not only in
the kernel address space, but also in the user one (as part of
__flush_tlb_one_user)? [ I obviously regard the case when PTI is on ].
Thanks,
Nadav
Hello Andy,
Is there a reason for __flush_tlb_one_kernel() to flush the PTE not only in
the kernel address space, but also in the user one (as part of
__flush_tlb_one_user)? [ I obviously regard the case when PTI is on ].
Thanks,
Nadav
more)
>
> Caused by commit
>
> e7d973a31c24 ("spi: sprd: Add SPI driver for Spreadtrum SC9860")
>
> I have used the spi tree from next-20180828 for today.
You missed one patch (spi: Introduce one new field to set word delay),
could you apply this patch into your next branc
more)
>
> Caused by commit
>
> e7d973a31c24 ("spi: sprd: Add SPI driver for Spreadtrum SC9860")
>
> I have used the spi tree from next-20180828 for today.
You missed one patch (spi: Introduce one new field to set word delay),
could you apply this patch into your next branc
Hi, Shawn
I saw v4.19-rc1 is created, can you please apply this patch?
Anson Huang
Best Regards!
> -Original Message-
> From: Shawn Guo
> Sent: Thursday, July 12, 2018 10:52 AM
> To: Anson Huang
> Cc: s.ha...@pengutronix.de; ker...@pengutronix.de; Fabio Estevam
> ;
Hi, Shawn
I saw v4.19-rc1 is created, can you please apply this patch?
Anson Huang
Best Regards!
> -Original Message-
> From: Shawn Guo
> Sent: Thursday, July 12, 2018 10:52 AM
> To: Anson Huang
> Cc: s.ha...@pengutronix.de; ker...@pengutronix.de; Fabio Estevam
> ;
Hi Randy
2018-08-29 4:55 GMT+09:00 Randy Dunlap :
> On 08/23/2018 09:20 PM, Masahiro Yamada wrote:
>> Hi Randy,
>>
>>
>> 2018-08-24 3:13 GMT+09:00 Randy Dunlap :
>>> From: Randy Dunlap
>>>
>>> When $DEPMOD is not found, only print a warning instead of exiting
>>> with an error message and error
On Tue, 2018-08-28 at 09:34 +0200, Paul Kocialkowski wrote:
> This introduces the Cedrus VPU driver that supports the VPU found in
> Allwinner SoCs, also known as Video Engine. It is implemented through
> a v4l2 m2m decoder device and a media device (used for media requests).
> So far, it only
Hi Randy
2018-08-29 4:55 GMT+09:00 Randy Dunlap :
> On 08/23/2018 09:20 PM, Masahiro Yamada wrote:
>> Hi Randy,
>>
>>
>> 2018-08-24 3:13 GMT+09:00 Randy Dunlap :
>>> From: Randy Dunlap
>>>
>>> When $DEPMOD is not found, only print a warning instead of exiting
>>> with an error message and error
On Tue, 2018-08-28 at 09:34 +0200, Paul Kocialkowski wrote:
> This introduces the Cedrus VPU driver that supports the VPU found in
> Allwinner SoCs, also known as Video Engine. It is implemented through
> a v4l2 m2m decoder device and a media device (used for media requests).
> So far, it only
On Tue, Aug 28, 2018 at 10:54:19AM -0700, Florian Fainelli wrote:
> Document the Broadcom roboswitch Switch Register Access Block interrupt
> lines and additional register base addresses for port mux configuration
> and SGMII status/configuration registers.
>
> Signed-off-by: Florian Fainelli
>
On Tue, Aug 28, 2018 at 10:54:19AM -0700, Florian Fainelli wrote:
> Document the Broadcom roboswitch Switch Register Access Block interrupt
> lines and additional register base addresses for port mux configuration
> and SGMII status/configuration registers.
>
> Signed-off-by: Florian Fainelli
>
On Tue, 28 Aug 2018 17:36:28 PDT (-0700), li...@roeck-us.net wrote:
On 08/28/2018 05:09 PM, Palmer Dabbelt wrote:
On Tue, 28 Aug 2018 15:12:38 PDT (-0700), li...@roeck-us.net wrote:
On Tue, Aug 28, 2018 at 03:03:00PM -0700, Palmer Dabbelt wrote:
On Tue, 28 Aug 2018 14:59:59 PDT (-0700),
On Tue, 28 Aug 2018 17:36:28 PDT (-0700), li...@roeck-us.net wrote:
On 08/28/2018 05:09 PM, Palmer Dabbelt wrote:
On Tue, 28 Aug 2018 15:12:38 PDT (-0700), li...@roeck-us.net wrote:
On Tue, Aug 28, 2018 at 03:03:00PM -0700, Palmer Dabbelt wrote:
On Tue, 28 Aug 2018 14:59:59 PDT (-0700),
On Fri, 24 Aug 2018 18:48:58 +0530, Sibi Sankar wrote:
> Add additional pdc_reset binding required for Q6V5 Modem PIL on
> SDM845 SoCs.
>
> Signed-off-by: Sibi Sankar
> ---
> Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt | 4
> 1 file changed, 4 insertions(+)
>
Reviewed-by:
On Fri, 24 Aug 2018 18:48:58 +0530, Sibi Sankar wrote:
> Add additional pdc_reset binding required for Q6V5 Modem PIL on
> SDM845 SoCs.
>
> Signed-off-by: Sibi Sankar
> ---
> Documentation/devicetree/bindings/remoteproc/qcom,q6v5.txt | 4
> 1 file changed, 4 insertions(+)
>
Reviewed-by:
From: Channagoud Kadabi
Add error reporting driver for Single Bit Errors (SBEs) and Double Bit
Errors (DBEs). As of now, this driver supports error reporting for
Last Level Cache Controller (LLCC) of Tag RAM and Data RAM. Interrupts
are triggered when the errors happen in the cache, the driver
From: Channagoud Kadabi
Add error reporting driver for Single Bit Errors (SBEs) and Double Bit
Errors (DBEs). As of now, this driver supports error reporting for
Last Level Cache Controller (LLCC) of Tag RAM and Data RAM. Interrupts
are triggered when the errors happen in the cache, the driver
On Fri, 24 Aug 2018 18:48:55 +0530, Sibi Sankar wrote:
> Add PDC Global(Power Domain Controller) binding for SDM845 SoCs.
>
> Signed-off-by: Sibi Sankar
> ---
> .../bindings/reset/qcom,pdc-global.txt| 52 +++
> include/dt-bindings/reset/qcom,sdm845-pdc.h | 20 +++
>
Add reg-names and interrupts for LLCC documentation and the usage
examples. llcc broadcast base is added in addition to llcc base,
which is used for llcc broadcast writes.
Signed-off-by: Venkata Narendra Kumar Gutta
---
.../devicetree/bindings/arm/msm/qcom,llcc.txt | 19
Cache error reporting controller detects and reports single and
double bit errors on Last Level Cache Controller (LLCC) cache.
Add required support to register LLCC EDAC driver as platform driver,
from LLCC driver.
Signed-off-by: Venkata Narendra Kumar Gutta
---
drivers/soc/qcom/llcc-slice.c
Currently, broadcast base is set to end of the LLCC banks, which may
not be correct always. As the number of banks may vary for each chipset
and the broadcast base could be at a different address as well. This info
depends on the chipset, so get the broadcast base info from the device
tree (DT).
On Fri, 24 Aug 2018 18:48:55 +0530, Sibi Sankar wrote:
> Add PDC Global(Power Domain Controller) binding for SDM845 SoCs.
>
> Signed-off-by: Sibi Sankar
> ---
> .../bindings/reset/qcom,pdc-global.txt| 52 +++
> include/dt-bindings/reset/qcom,sdm845-pdc.h | 20 +++
>
Add reg-names and interrupts for LLCC documentation and the usage
examples. llcc broadcast base is added in addition to llcc base,
which is used for llcc broadcast writes.
Signed-off-by: Venkata Narendra Kumar Gutta
---
.../devicetree/bindings/arm/msm/qcom,llcc.txt | 19
Cache error reporting controller detects and reports single and
double bit errors on Last Level Cache Controller (LLCC) cache.
Add required support to register LLCC EDAC driver as platform driver,
from LLCC driver.
Signed-off-by: Venkata Narendra Kumar Gutta
---
drivers/soc/qcom/llcc-slice.c
Currently, broadcast base is set to end of the LLCC banks, which may
not be correct always. As the number of banks may vary for each chipset
and the broadcast base could be at a different address as well. This info
depends on the chipset, so get the broadcast base info from the device
tree (DT).
This series implements EDAC driver for QCOM SoCs. As of now, this driver
supports EDAC for Last Level Cache Controller (LLCC). LLCC EDAC driver is
to detect and report single and double bit errors on Last Level Cache
Controller (LLCC) cache. Interrupts are triggered when the errors happen
in the
This series implements EDAC driver for QCOM SoCs. As of now, this driver
supports EDAC for Last Level Cache Controller (LLCC). LLCC EDAC driver is
to detect and report single and double bit errors on Last Level Cache
Controller (LLCC) cache. Interrupts are triggered when the errors happen
in the
On Mon, Aug 27, 2018 at 04:55:20PM +0800, Hanjie Lin wrote:
>
>
> On 2018/8/24 16:22, Jerome Brunet wrote:
> > On Fri, 2018-08-24 at 15:36 +0800, Hanjie Lin wrote:
> >> From: Yue Wang
> >>
> >> The Amlogic Meson PCIe host controller is based on the Synopsys DesignWare
> >> PCI core. This patch
On Mon, Aug 27, 2018 at 04:55:20PM +0800, Hanjie Lin wrote:
>
>
> On 2018/8/24 16:22, Jerome Brunet wrote:
> > On Fri, 2018-08-24 at 15:36 +0800, Hanjie Lin wrote:
> >> From: Yue Wang
> >>
> >> The Amlogic Meson PCIe host controller is based on the Synopsys DesignWare
> >> PCI core. This patch
On 08/28/2018 05:09 PM, Palmer Dabbelt wrote:
On Tue, 28 Aug 2018 15:12:38 PDT (-0700), li...@roeck-us.net wrote:
On Tue, Aug 28, 2018 at 03:03:00PM -0700, Palmer Dabbelt wrote:
On Tue, 28 Aug 2018 14:59:59 PDT (-0700), li...@roeck-us.net wrote:
>On Tue, Aug 28, 2018 at 11:46:09PM +0200,
On 08/28/2018 05:09 PM, Palmer Dabbelt wrote:
On Tue, 28 Aug 2018 15:12:38 PDT (-0700), li...@roeck-us.net wrote:
On Tue, Aug 28, 2018 at 03:03:00PM -0700, Palmer Dabbelt wrote:
On Tue, 28 Aug 2018 14:59:59 PDT (-0700), li...@roeck-us.net wrote:
>On Tue, Aug 28, 2018 at 11:46:09PM +0200,
1 - 100 of 1380 matches
Mail list logo
