The command 'perf annotate' parses the output of objdump and also
investigates the comments produced by objdump. For example the
output of objdump produces (on x86):
23eee: 4c 8b 3d 13 01 21 00 mov 0x210113(%rip),%r15
# 234008
and the
The command 'perf annotate' parses the output of objdump and also
investigates the comments produced by objdump. For example the
output of objdump produces (on x86):
23eee: 4c 8b 3d 13 01 21 00 mov 0x210113(%rip),%r15
# 234008
and the function mov__parse() is
From: Joonsoo Kim
Hello,
This patchset introduces a new tool, valid access checker.
Vchecker is a dynamic memory error detector. It provides a new debug feature
that can find out an un-intended access to valid area. Valid area here means
the memory which is allocated
From: Joonsoo Kim
Hello,
This patchset introduces a new tool, valid access checker.
Vchecker is a dynamic memory error detector. It provides a new debug feature
that can find out an un-intended access to valid area. Valid area here means
the memory which is allocated and allowed to be accessed
From: Joonsoo Kim
To prepare per object memory for vchecker, we need to change the layout
of the object when kmem_cache initialization. Add such code on
vchecker_cache_create() which is called when kmem_cache initialization.
And, this memory should be initialized when
From: Joonsoo Kim
To prepare per object memory for vchecker, we need to change the layout
of the object when kmem_cache initialization. Add such code on
vchecker_cache_create() which is called when kmem_cache initialization.
And, this memory should be initialized when object is populated. Do it
On Mon, Nov 27, 2017 at 09:37:38PM -0800, Eric Biggers wrote:
> On Mon, Nov 27, 2017 at 10:56:47AM -0800, syzbot wrote:
> > Hello,
> >
> > syzkaller hit the following crash on
> > 1ea8d039f9edcfefb20d8ddfe136930f6e551529
> > git://git.cmpxchg.org/linux-mmots.git/master
> > compiler: gcc (GCC)
From: Joonsoo Kim
They will be used for the vchecker in the following patch.
Make it non-static and add declairation in header files.
Signed-off-by: Joonsoo Kim
---
include/linux/kasan.h | 1 +
mm/kasan/kasan.c | 2 +-
mm/kasan/kasan.h
From: Joonsoo Kim
They will be used for the vchecker in the following patch.
Make it non-static and add declairation in header files.
Signed-off-by: Joonsoo Kim
---
include/linux/kasan.h | 1 +
mm/kasan/kasan.c | 2 +-
mm/kasan/kasan.h | 2 ++
mm/kasan/report.c | 2 +-
4 files
On Mon, Nov 27, 2017 at 09:37:38PM -0800, Eric Biggers wrote:
> On Mon, Nov 27, 2017 at 10:56:47AM -0800, syzbot wrote:
> > Hello,
> >
> > syzkaller hit the following crash on
> > 1ea8d039f9edcfefb20d8ddfe136930f6e551529
> > git://git.cmpxchg.org/linux-mmots.git/master
> > compiler: gcc (GCC)
From: Joonsoo Kim
Vchecker is a dynamic memory error detector. It provides a new debug
feature that can find out an un-intended access to valid area. Valid
area here means the memory which is allocated and allowed to be
accessed by memory owner and un-intended access
From: Joonsoo Kim
Vchecker is a dynamic memory error detector. It provides a new debug
feature that can find out an un-intended access to valid area. Valid
area here means the memory which is allocated and allowed to be
accessed by memory owner and un-intended access means the read/write
that is
From: Joonsoo Kim
There is a usecase that check if stack trace is new or not during specific
period. Since stackdepot library doesn't support removal of stack trace,
it's impossible to know above thing. Since removal of stack trace is not
easy in the design of stackdepot
From: Joonsoo Kim
There is a usecase that check if stack trace is new or not during specific
period. Since stackdepot library doesn't support removal of stack trace,
it's impossible to know above thing. Since removal of stack trace is not
easy in the design of stackdepot library, we need another
The driver has been in the tree for a while, but its binding document
is missing. Hence, here it is.
Signed-off-by: Masahiro Yamada
---
.../pinctrl/socionext,uniphier-pinctrl.txt | 27 ++
MAINTAINERS
The driver has been in the tree for a while, but its binding document
is missing. Hence, here it is.
Signed-off-by: Masahiro Yamada
---
.../pinctrl/socionext,uniphier-pinctrl.txt | 27 ++
MAINTAINERS| 1 +
2 files changed,
From: Joonsoo Kim
Since there is a different callpath even in the vchecker, static skip
value doesn't always exclude vchecker's stacktrace. Fix it through
checking stacktrace dynamically.
v2: skip two depth of stack at default, it's safe!
Signed-off-by: Joonsoo Kim
From: Joonsoo Kim
Since there is a different callpath even in the vchecker, static skip
value doesn't always exclude vchecker's stacktrace. Fix it through
checking stacktrace dynamically.
v2: skip two depth of stack at default, it's safe!
Signed-off-by: Joonsoo Kim
---
mm/kasan/vchecker.c |
On 11/27/2017 09:22 PM, Andy Lutomirski wrote:
> On Mon, Nov 27, 2017 at 2:49 AM, Ingo Molnar wrote:
>> From: Dave Hansen
>>
>> Short summary: Use x86 PCID feature to avoid flushing the TLB at all
>> interrupts and syscalls. Speed them up. Makes
On 11/27/2017 09:22 PM, Andy Lutomirski wrote:
> On Mon, Nov 27, 2017 at 2:49 AM, Ingo Molnar wrote:
>> From: Dave Hansen
>>
>> Short summary: Use x86 PCID feature to avoid flushing the TLB at all
>> interrupts and syscalls. Speed them up. Makes context switches
>> and TLB flushing slower.
>
From: Namhyung Kim
Since we're finding a cause of broken data, it'd be desired not to miss
any suspects. It doesn't use GFP_ATOMIC since it includes __GFP_HIGH
which is for system making forward progress.
It also adds a WARN_ON whenever it fails to allocate pages even with
From: Joonsoo Kim
Getting full callstack is heavy job so it's sometimes better to
reduce this overhead by limiting callstack depth. So, this patch
makes the callstack depth configurable by using debugfs interface.
Signed-off-by: Joonsoo Kim
---
From: Namhyung Kim
Since we're finding a cause of broken data, it'd be desired not to miss
any suspects. It doesn't use GFP_ATOMIC since it includes __GFP_HIGH
which is for system making forward progress.
It also adds a WARN_ON whenever it fails to allocate pages even with
__GFP_ATOMIC.
From: Joonsoo Kim
Getting full callstack is heavy job so it's sometimes better to
reduce this overhead by limiting callstack depth. So, this patch
makes the callstack depth configurable by using debugfs interface.
Signed-off-by: Joonsoo Kim
---
mm/kasan/vchecker.c | 81
From: Joonsoo Kim
kmalloc() is used everywhere in the kernel and it doesn't distiniguish
the callers since it doesn't much help to efficiently manage the memory.
However, there is a difference in the view of the debugging. A bug usually
happens on the objects allocated
From: Joonsoo Kim
Vchecker requires kmalloc caller address to support validation on
*specific* kmalloc user. Therefore, this patch passes slab allocation
caller address to vchecker hook. This caller address will be used in the
following patch.
Signed-off-by: Joonsoo Kim
From: Joonsoo Kim
kmalloc() is used everywhere in the kernel and it doesn't distiniguish
the callers since it doesn't much help to efficiently manage the memory.
However, there is a difference in the view of the debugging. A bug usually
happens on the objects allocated by specific allocation
From: Joonsoo Kim
Vchecker requires kmalloc caller address to support validation on
*specific* kmalloc user. Therefore, this patch passes slab allocation
caller address to vchecker hook. This caller address will be used in the
following patch.
Signed-off-by: Joonsoo Kim
---
From: Joonsoo Kim
It's not easy to understand what can be done by the vchecker.
This sample could explain it and help to understand the vchecker.
Signed-off-by: Joonsoo Kim
---
lib/Kconfig.kasan | 9
lib/Makefile| 1 +
From: Joonsoo Kim
It's not easy to understand what can be done by the vchecker.
This sample could explain it and help to understand the vchecker.
Signed-off-by: Joonsoo Kim
---
lib/Kconfig.kasan | 9
lib/Makefile| 1 +
lib/vchecker_test.c | 117
From: Namhyung Kim
The is_new argument is to check whether the given stack trace was
already in the stack depot or newly added. It'll be used by vchecker
callstack in the next patch.
Also add WARN_ONCE if stack depot failed to allocate stack slab for some
reason. This is
From: Namhyung Kim
The is_new argument is to check whether the given stack trace was
already in the stack depot or newly added. It'll be used by vchecker
callstack in the next patch.
Also add WARN_ONCE if stack depot failed to allocate stack slab for some
reason. This is unusual as it
From: Joonsoo Kim
There is no reason not to support inline KASAN build. Support it.
Note that vchecker_check() function is now placed on kasan report function
to support inline build because gcc generates the inline check code and
then directly jump to kasan report
From: Namhyung Kim
By default, callstack checker only collects callchains. When a user
writes 'on' to the callstack file in debugfs, it checks and reports new
callstacks. Writing 'off' to disable it again.
# cd /sys/kernel/debug/vchecker
# echo 0 8 >
From: Namhyung Kim
The callstack checker is to find invalid code paths accessing to a
certain field in an object. Currently it only saves all stack traces at
the given offset. Reporting will be added in the next patch.
The below example checks callstack of anon_vma:
#
From: Joonsoo Kim
There is no reason not to support inline KASAN build. Support it.
Note that vchecker_check() function is now placed on kasan report function
to support inline build because gcc generates the inline check code and
then directly jump to kasan report function when poisoned value
From: Namhyung Kim
By default, callstack checker only collects callchains. When a user
writes 'on' to the callstack file in debugfs, it checks and reports new
callstacks. Writing 'off' to disable it again.
# cd /sys/kernel/debug/vchecker
# echo 0 8 > anon_vma/callstack
# echo 1 >
From: Namhyung Kim
The callstack checker is to find invalid code paths accessing to a
certain field in an object. Currently it only saves all stack traces at
the given offset. Reporting will be added in the next patch.
The below example checks callstack of anon_vma:
# cd
From: Joonsoo Kim
This is a main document for vchecker user.
Signed-off-by: Joonsoo Kim
---
Documentation/dev-tools/vchecker.rst | 200 +++
1 file changed, 200 insertions(+)
create mode 100644
From: Joonsoo Kim
This is a main document for vchecker user.
Signed-off-by: Joonsoo Kim
---
Documentation/dev-tools/vchecker.rst | 200 +++
1 file changed, 200 insertions(+)
create mode 100644 Documentation/dev-tools/vchecker.rst
diff --git
From: Joonsoo Kim
The purpose of the value checker is finding invalid user writing
invalid value at the moment that the value is written. However, there is
not enough infrastructure so that we cannot easily detect this case
in time.
However, by following way, we can
From: Joonsoo Kim
Since stack depot library doesn't support removal operation,
after removing and adding again callstack cb, callstack checker cannot
correctly judge whether this callstack is new or not for current cb
if the same callstack happens for previous cb.
This
From: Joonsoo Kim
The purpose of the value checker is finding invalid user writing
invalid value at the moment that the value is written. However, there is
not enough infrastructure so that we cannot easily detect this case
in time.
However, by following way, we can emulate similar effect.
1.
From: Joonsoo Kim
Since stack depot library doesn't support removal operation,
after removing and adding again callstack cb, callstack checker cannot
correctly judge whether this callstack is new or not for current cb
if the same callstack happens for previous cb.
This problem can be fixed by
From: Joonsoo Kim
Mark/unmark the shadow of the objects that is allocated before the
vchecker is enabled/disabled. It is necessary to fully debug the system.
Since there is no synchronization way to prevent slab object free,
we cannot synchronously mark/unmark the shadow
From: Joonsoo Kim
Mark/unmark the shadow of the objects that is allocated before the
vchecker is enabled/disabled. It is necessary to fully debug the system.
Since there is no synchronization way to prevent slab object free,
we cannot synchronously mark/unmark the shadow of the allocated object.
On Tue, 28 Nov 2017, SF Markus Elfring wrote:
> >> It seems that I got no responses so far for clarification requests
> >> according to the documentation in a direction I hoped for.
> >
> > That's because you are pretty unresponsive to direction.
>
> From which places did you get this
On Tue, 28 Nov 2017, SF Markus Elfring wrote:
> >> It seems that I got no responses so far for clarification requests
> >> according to the documentation in a direction I hoped for.
> >
> > That's because you are pretty unresponsive to direction.
>
> From which places did you get this
On Tue, Nov 28, 2017 at 5:05 AM, Zhouyi Zhou wrote:
> When there are huge amount of quarantined cache allocates in system,
> number of entries in global_quarantine[i] will be great. Meanwhile,
> there is no relax in while loop in function qlist_move_cache which
> hold
On Tue, Nov 28, 2017 at 5:05 AM, Zhouyi Zhou wrote:
> When there are huge amount of quarantined cache allocates in system,
> number of entries in global_quarantine[i] will be great. Meanwhile,
> there is no relax in while loop in function qlist_move_cache which
> hold quarantine_lock. As a
On Thu, 16 Nov 2017 20:30:24 +0100,
SF Markus Elfring wrote:
>
> >> There is a general source code transformation pattern involved.
> >> So I find that it is systematic.
> >>
> >> But I did not dare to develop a script variant for the semantic patch
> >> language (Coccinelle software) which can
On Thu, 16 Nov 2017 20:30:24 +0100,
SF Markus Elfring wrote:
>
> >> There is a general source code transformation pattern involved.
> >> So I find that it is systematic.
> >>
> >> But I did not dare to develop a script variant for the semantic patch
> >> language (Coccinelle software) which can
From: Patrick Bruenn
Neither rtc-imxdi nor rtc-mxc are compatible with i.MX53.
Add a modernized version of mxc_v2 from here:
http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/tree/drivers/rtc/rtc-mxc_v2.c?h=imx_2.6.35_11.09.01
Changes to that version:
- updated
From: Patrick Bruenn
Neither rtc-imxdi nor rtc-mxc are compatible with i.MX53.
Add a modernized version of mxc_v2 from here:
http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/tree/drivers/rtc/rtc-mxc_v2.c?h=imx_2.6.35_11.09.01
Changes to that version:
- updated to v4.15-rc1
- removed
Am Dienstag, 28. November 2017, 08:29:44 CET schrieb Eric Biggers:
Hi Eric,
>
> Sometimes you have to reboot to get the reproducer to work, because the bug
> has to do with referencing counting of the "null skcipher" which is a
> global resource. Here's a patch that fixes it, it seems:
>
>
Am Dienstag, 28. November 2017, 08:29:44 CET schrieb Eric Biggers:
Hi Eric,
>
> Sometimes you have to reboot to get the reproducer to work, because the bug
> has to do with referencing counting of the "null skcipher" which is a
> global resource. Here's a patch that fixes it, it seems:
>
>
Hi,
On 11/28/2017 03:29 PM, Greg Kroah-Hartman wrote:
> On Tue, Nov 28, 2017 at 12:52:24PM +0800, Lu Baolu wrote:
>> This corrects the endpiont type value set to the DbC bulk in endpoint.
>> The previous value doesn't cause any problems because that we now only
>> use the bulk out endpoint. Set
Hi,
On 11/28/2017 03:29 PM, Greg Kroah-Hartman wrote:
> On Tue, Nov 28, 2017 at 12:52:24PM +0800, Lu Baolu wrote:
>> This corrects the endpiont type value set to the DbC bulk in endpoint.
>> The previous value doesn't cause any problems because that we now only
>> use the bulk out endpoint. Set
>> It seems that I got no responses so far for clarification requests
>> according to the documentation in a direction I hoped for.
>
> That's because you are pretty unresponsive to direction.
>From which places did you get this impression?
> You've gotten _many_ replies to your patches
I got
>> It seems that I got no responses so far for clarification requests
>> according to the documentation in a direction I hoped for.
>
> That's because you are pretty unresponsive to direction.
>From which places did you get this impression?
> You've gotten _many_ replies to your patches
I got
Hi Alex,
>>>
> Hi Gang,
>
> On 2017/11/28 13:33, Gang He wrote:
>> Hello Alex,
>>
>>
>
>>> Hi Gang,
>>>
>>> On 2017/11/27 17:46, Gang He wrote:
Add ocfs2_overwrite_io function, which is used to judge if
overwrite allocated blocks, otherwise, the write will bring extra
Hi Alex,
>>>
> Hi Gang,
>
> On 2017/11/28 13:33, Gang He wrote:
>> Hello Alex,
>>
>>
>
>>> Hi Gang,
>>>
>>> On 2017/11/27 17:46, Gang He wrote:
Add ocfs2_overwrite_io function, which is used to judge if
overwrite allocated blocks, otherwise, the write will bring extra
On 11/27/2017 09:16 PM, Andy Lutomirski wrote:
> We need to split up __flush_tlb_one() into __flush_tlb_one() and
> __flush_tlb_one_kernel(). We've gotten away with having a single
> function for both this long because we've never had PCID on and
> nonglobal kernel mappings around. So we're
On 11/27/2017 09:16 PM, Andy Lutomirski wrote:
> We need to split up __flush_tlb_one() into __flush_tlb_one() and
> __flush_tlb_one_kernel(). We've gotten away with having a single
> function for both this long because we've never had PCID on and
> nonglobal kernel mappings around. So we're
On Thu, 16 Nov 2017 12:52:41 +0100,
SF Markus Elfring wrote:
>
> From: Markus Elfring
> Date: Thu, 16 Nov 2017 11:22:26 +0100
>
> The function "release_firmware" is called in the current implementation of
> the function "_request_firmware" after a failure was
On Thu, 16 Nov 2017 12:52:41 +0100,
SF Markus Elfring wrote:
>
> From: Markus Elfring
> Date: Thu, 16 Nov 2017 11:22:26 +0100
>
> The function "release_firmware" is called in the current implementation of
> the function "_request_firmware" after a failure was detected.
> Link:
>
On 2017/11/28 13:44, Gang He wrote:
> Hi Changwei,
>
>
>> Hi,
>> Gang
>>
>> On 2017/11/27 17:48, Gang He wrote:
>>> Add ocfs2_overwrite_io function, which is used to judge if
>>> overwrite allocated blocks, otherwise, the write will bring extra
>>> block allocation overhead.
>>>
>>
>> Can
Signed-off-by: Masahiro Yamada
---
Documentation/devicetree/bindings/arm/uniphier.txt | 40 ++
MAINTAINERS| 1 +
2 files changed, 41 insertions(+)
create mode 100644
On 2017/11/28 13:44, Gang He wrote:
> Hi Changwei,
>
>
>> Hi,
>> Gang
>>
>> On 2017/11/27 17:48, Gang He wrote:
>>> Add ocfs2_overwrite_io function, which is used to judge if
>>> overwrite allocated blocks, otherwise, the write will bring extra
>>> block allocation overhead.
>>>
>>
>> Can
Signed-off-by: Masahiro Yamada
---
Documentation/devicetree/bindings/arm/uniphier.txt | 40 ++
MAINTAINERS| 1 +
2 files changed, 41 insertions(+)
create mode 100644 Documentation/devicetree/bindings/arm/uniphier.txt
diff --git
This series is based on v4.15-rc1 and composed of
scpsys control (PATCH 1-4) and device tree (PATCH 5-6)
changes since v6:
- Rebase to v4.15-rc1.
changes since v5:
- Refine bus protection with proper variable name
and better implementation for the if statement.
changes since v4:
- Refine
This series is based on v4.15-rc1 and composed of
scpsys control (PATCH 1-4) and device tree (PATCH 5-6)
changes since v6:
- Rebase to v4.15-rc1.
changes since v5:
- Refine bus protection with proper variable name
and better implementation for the if statement.
changes since v4:
- Refine
Add power dt-bindings for MT2712.
Acked-by: Rob Herring
Signed-off-by: Weiyi Lu
---
.../devicetree/bindings/soc/mediatek/scpsys.txt| 3 +++
include/dt-bindings/power/mt2712-power.h | 26 ++
2 files changed, 29
Add power dt-bindings for MT2712.
Acked-by: Rob Herring
Signed-off-by: Weiyi Lu
---
.../devicetree/bindings/soc/mediatek/scpsys.txt| 3 +++
include/dt-bindings/power/mt2712-power.h | 26 ++
2 files changed, 29 insertions(+)
create mode 100644
On Tue, Nov 28, 2017 at 07:30:46AM +0100, Stephan Mueller wrote:
> Am Montag, 27. November 2017, 23:43:08 CET schrieb Eric Biggers:
>
> Hi Eric,
>
> > No, that doesn't help. I tested v4.15-rc1 with all the extra commits from
> > crypto-2.6.git/master applied:
> >
> > crypto: algif_aead -
MT2712 add "set/clear" bus control register to each control register set
instead of providing only one "enable" control register, we could avoid
the read-modify-write racing by declaring "bus_prot_reg_update" as "false"
in scp_soc_data or declaring as "true" to use the legacy update method.
By
Add clock controller nodes for MT2712, include topckgen, infracfg,
pericfg, mcucfg and apmixedsys. This patch also add six oscillators that
provide clocks for MT2712.
Signed-off-by: Weiyi Lu
---
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 115
On Tue, Nov 28, 2017 at 07:30:46AM +0100, Stephan Mueller wrote:
> Am Montag, 27. November 2017, 23:43:08 CET schrieb Eric Biggers:
>
> Hi Eric,
>
> > No, that doesn't help. I tested v4.15-rc1 with all the extra commits from
> > crypto-2.6.git/master applied:
> >
> > crypto: algif_aead -
MT2712 add "set/clear" bus control register to each control register set
instead of providing only one "enable" control register, we could avoid
the read-modify-write racing by declaring "bus_prot_reg_update" as "false"
in scp_soc_data or declaring as "true" to use the legacy update method.
By
Add clock controller nodes for MT2712, include topckgen, infracfg,
pericfg, mcucfg and apmixedsys. This patch also add six oscillators that
provide clocks for MT2712.
Signed-off-by: Weiyi Lu
---
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 115 ++
1 file changed, 115
add scpsys driver for MT2712
Signed-off-by: Weiyi Lu
---
drivers/soc/mediatek/mtk-scpsys.c | 106 +++---
1 file changed, 100 insertions(+), 6 deletions(-)
diff --git a/drivers/soc/mediatek/mtk-scpsys.c
b/drivers/soc/mediatek/mtk-scpsys.c
This series is based on v4.15-rc1 and composed of
scpsys control (PATCH 1-4) and device tree (PATCH 5-6)
changes since v6:
- Rebase to v4.15-rc1.
changes since v5:
- Refine bus protection with proper variable name
and better implementation for the if statement.
changes since v4:
- Refine
This series is based on v4.15-rc1 and composed of
scpsys control (PATCH 1-4) and device tree (PATCH 5-6)
changes since v6:
- Rebase to v4.15-rc1.
changes since v5:
- Refine bus protection with proper variable name
and better implementation for the if statement.
changes since v4:
- Refine
add scpsys driver for MT2712
Signed-off-by: Weiyi Lu
---
drivers/soc/mediatek/mtk-scpsys.c | 106 +++---
1 file changed, 100 insertions(+), 6 deletions(-)
diff --git a/drivers/soc/mediatek/mtk-scpsys.c
b/drivers/soc/mediatek/mtk-scpsys.c
index c0f3219..435ce5e
add power controller node for MT2712
Signed-off-by: Weiyi Lu
---
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
b/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
index
add power controller node for MT2712
Signed-off-by: Weiyi Lu
---
arch/arm64/boot/dts/mediatek/mt2712e.dtsi | 16
1 file changed, 16 insertions(+)
diff --git a/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
b/arch/arm64/boot/dts/mediatek/mt2712e.dtsi
index 5703793..61dd763 100644
On Tue, Nov 28, 2017 at 12:52:24PM +0800, Lu Baolu wrote:
> This corrects the endpiont type value set to the DbC bulk in endpoint.
> The previous value doesn't cause any problems because that we now only
> use the bulk out endpoint. Set the hardware with the correct value any
> way.
>
>
There are dependent clock jpgdec/audio in scpsys on MT2712,
and will exist three dependent clocks on MT2712 VDEC.
Signed-off-by: Weiyi Lu
---
drivers/soc/mediatek/mtk-scpsys.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git
On Tue, Nov 28, 2017 at 12:52:24PM +0800, Lu Baolu wrote:
> This corrects the endpiont type value set to the DbC bulk in endpoint.
> The previous value doesn't cause any problems because that we now only
> use the bulk out endpoint. Set the hardware with the correct value any
> way.
>
>
There are dependent clock jpgdec/audio in scpsys on MT2712,
and will exist three dependent clocks on MT2712 VDEC.
Signed-off-by: Weiyi Lu
---
drivers/soc/mediatek/mtk-scpsys.c | 6 +-
1 file changed, 5 insertions(+), 1 deletion(-)
diff --git a/drivers/soc/mediatek/mtk-scpsys.c
On Wed, 22 Nov 2017 17:47:14 +0100,
SF Markus Elfring wrote:
>
> From: Markus Elfring
> Date: Wed, 22 Nov 2017 17:43:25 +0100
>
> Omit an extra message for a memory allocation failure in this function.
>
> This issue was detected by using the Coccinelle software.
On Wed, 22 Nov 2017 17:47:14 +0100,
SF Markus Elfring wrote:
>
> From: Markus Elfring
> Date: Wed, 22 Nov 2017 17:43:25 +0100
>
> Omit an extra message for a memory allocation failure in this function.
>
> This issue was detected by using the Coccinelle software.
>
> Signed-off-by: Markus
On Mon, Nov 27, 2017 at 09:12:39PM +, Chris Coffey wrote:
> This patch fixes build errors that occur when trying to build the
> MOST modules. For example, the cdev module build fails with:
>
> make[3]: *** No rule to make target 'drivers/staging/most/aim-cdev/cdev.o',
> needed by
On Mon, Nov 27, 2017 at 09:12:39PM +, Chris Coffey wrote:
> This patch fixes build errors that occur when trying to build the
> MOST modules. For example, the cdev module build fails with:
>
> make[3]: *** No rule to make target 'drivers/staging/most/aim-cdev/cdev.o',
> needed by
Hello Joseph,
>>>
>
> On 17/11/28 11:35, Gang He wrote:
>> Hello Joseph,
>>
>>
>
>>> Hi Gang,
>>>
>>> On 17/11/27 17:46, Gang He wrote:
Add ocfs2_overwrite_io function, which is used to judge if
overwrite allocated blocks, otherwise, the write will bring extra
block
Hello Joseph,
>>>
>
> On 17/11/28 11:35, Gang He wrote:
>> Hello Joseph,
>>
>>
>
>>> Hi Gang,
>>>
>>> On 17/11/27 17:46, Gang He wrote:
Add ocfs2_overwrite_io function, which is used to judge if
overwrite allocated blocks, otherwise, the write will bring extra
block
Commit-ID: 55d2d0ad2fb4325f615d1950486fbc5e6fba1769
Gitweb: https://git.kernel.org/tip/55d2d0ad2fb4325f615d1950486fbc5e6fba1769
Author: Chunyu Hu
AuthorDate: Mon, 27 Nov 2017 22:21:39 +0800
Committer: Thomas Gleixner
CommitDate: Tue, 28 Nov 2017
Hi Jiada
> register SSI_MODE is set when SSI works in TDM Extended,
> but it isn't reset when SSI starts to work in other modes,
> thus causes issues.
>
> This patch clearss SSI_MODE register when SSI works in modes
> other than TDM Extended.
>
> Fixes: 186fadc132f0 ("ASoC: rsnd: add TDM
Commit-ID: 55d2d0ad2fb4325f615d1950486fbc5e6fba1769
Gitweb: https://git.kernel.org/tip/55d2d0ad2fb4325f615d1950486fbc5e6fba1769
Author: Chunyu Hu
AuthorDate: Mon, 27 Nov 2017 22:21:39 +0800
Committer: Thomas Gleixner
CommitDate: Tue, 28 Nov 2017 08:15:40 +0100
x86/idt: Load idt early
Hi Jiada
> register SSI_MODE is set when SSI works in TDM Extended,
> but it isn't reset when SSI starts to work in other modes,
> thus causes issues.
>
> This patch clearss SSI_MODE register when SSI works in modes
> other than TDM Extended.
>
> Fixes: 186fadc132f0 ("ASoC: rsnd: add TDM
1 - 100 of 2688 matches
Mail list logo