From: dillon min
Art-pi based on stm32h750xbh6, with following resources:
-8MiB QSPI flash
-16MiB SPI flash
-32MiB SDRAM
-AP6212 wifi, bt, fm
detail information can be found at:
https://art-pi.gitee.io/website/
Signed-off-by: dillon min
---
v2: no changes
Documentation/devicetree/bindings/a
From: dillon min
This patchset intend to add art-pi board support, this board developed
by rt-thread(https://www.rt-thread.org/).
Board resources:
8MiB QSPI flash
16MiB SPI flash
32MiB SDRAM
AP6212 wifi,bt,fm comb
sw context:
- as stm32h750 just has 128k bytes internal flash, so running a fw o
From: dillon min
This patch add stm32h750-pinctrl.dtsi which just
reference stm32h7-pinctrl.dtsi
Signed-off-by: dillon min
---
v2: no changes
arch/arm/boot/dts/stm32h750-pinctrl.dtsi | 11 +++
1 file changed, 11 insertions(+)
create mode 100644 arch/arm/boot/dts/stm32h750-pinctrl.dts
From: dillon min
This patch is intend to add support stm32h750 value line,
just add stm32h7-pinctrl.dtsi for extending, with following changes:
- rename stm32h743-pinctrl.dtsi to stm32h7-pinctrl.dtsi
- move compatible string "st,stm32h743-pinctrl" from stm32h7-pinctrl.dtsi
to stm32h743-pinctrl
From: dillon min
This patch adds STM32H750 pinctrl and GPIO support
since stm32h750 has the same pin alternate functions
with stm32h743, so just reuse the stm32h743's pinctrl
driver
Signed-off-by: dillon min
---
v2:
- add compatible string st,stm32h750-pinctrl to pinctl-stm32h743.c as they
ha
From: dillon min
This patchset has following changes:
- introduce stm32h750.dtsi to support stm32h750 value line
- add stm32h750i-art-pi.dtb (arch/arm/boot/dts/Makefile)
- add dts binding usart3 for bt, uart4 for console
usart3/uart4 pinctrl in stm32h7-pinctrl.dtsi
usart3/uart4 register in s
From: dillon min
The STM32H750 is a Cortex-M7 MCU running at 480MHz and containing 128KBytes
internal flash, 1MiB SRAM.
Signed-off-by: dillon min
---
v2: no changes
arch/arm/mach-stm32/board-dt.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/mach-stm32/board-dt.c b/arch/arm/mac
Hi Len,
thank you for your reply.
On Thu, Mar 11, 2021 at 3:19 PM Len Brown wrote:
>
> Thanks for the close read, Doug.
>
> This field size actually varies from system to system,
> but the reality is that the offset is never that big, and so the
> smaller mask is sufficient.
Disagree.
I want
Hi Ira,
On Thu, Mar 11, 2021 at 08:02:20AM -0800, Ira Weiny wrote:
> On Tue, Mar 09, 2021 at 08:53:04PM +, Chaitanya Kulkarni wrote:
> > Ira,
> >
> > On 3/4/21 00:23, kernel test robot wrote:
> > > Greeting,
> > >
> > > FYI, we noticed the following commit (built with gcc-9):
> > >
> > > comm
On Fri, Mar 12, 2021 at 5:13 AM wrote:
>
> From: Zqiang
>
> BUG: using smp_processor_id() in preemptible [] code:
> syz-executor.0/15841
> caller is debug_smp_processor_id+0x20/0x24
> lib/smp_processor_id.c:64
>
> The smp_processor_id() is used in a code segment when
> preemption has been
Hi,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on linux/master]
[also build test WARNING on linus/master hnaz-linux-mm/master v5.12-rc2
next-20210311]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting patch, we
On 2021/3/11 9:52 下午, Stefano Garzarella wrote:
When the 'v->config_ctx' eventfd_ctx reference is released we didn't
set it to NULL. So if the same character device (e.g. /dev/vhost-vdpa-0)
is re-opened, the 'v->config_ctx' is invalid and calling again
vhost_vdpa_config_put() causes use-after-f
On Thursday 11 Mar 2021 at 19:36:39 (+), Will Deacon wrote:
> On Wed, Mar 10, 2021 at 05:57:30PM +, Quentin Perret wrote:
> > diff --git a/arch/arm64/kernel/cpufeature.c b/arch/arm64/kernel/cpufeature.c
> > index 066030717a4c..f2d8b479ff74 100644
> > --- a/arch/arm64/kernel/cpufeature.c
> >
On Thu, Mar 11, 2021 at 09:24:42PM -0800, Badhri Jagan Sridharan wrote:
> This change adds chip callbacks for the following operations:
> 1. Notifying port role
> 2. Notifying orientation
This should be 2 different patches, one per callback, right?
And where is the code using these callbacks? We
On 2021/3/11 9:52 下午, Stefano Garzarella wrote:
In vhost_vdpa_set_config_call() if eventfd_ctx_fdget() fails the
'v->config_ctx' contains an error instead of a valid pointer.
Since we consider 'v->config_ctx' valid if it is not NULL, we should
set it to NULL in this case to avoid to use an inv
On Fri, Mar 12, 2021 at 07:33:45AM +0100, Greg Kroah-Hartman wrote:
> On Thu, Mar 11, 2021 at 09:24:42PM -0800, Badhri Jagan Sridharan wrote:
> > This change adds chip callbacks for the following operations:
> > 1. Notifying port role
> > 2. Notifying orientation
>
> This should be 2 different pat
This series includes 1 patches:
1.add lock in mtk_rmw function.
Zhiyong Tao (1):
pinctrl: add lock in mtk_rmw function.
drivers/pinctrl/mediatek/pinctrl-mtk-common-v2.c | 4
drivers/pinctrl/mediatek/pinctrl-mtk-common-v2.h | 2 ++
drivers/pinctrl/mediatek/pinctrl-paris.c | 2 ++
3
When multiple threads operate on the same register resource
which include multiple pin, It will make the register resource
wrong to control. So we add lock to avoid the case.
Signed-off-by: Zhiyong Tao
---
drivers/pinctrl/mediatek/pinctrl-mtk-common-v2.c | 4
drivers/pinctrl/mediatek/pinctr
On Fri, Mar 12, 2021 at 3:30 AM Andy Lutomirski wrote:
>
> Your warning is odd, but I see the bug. It's in KVM.
Hi Andy,
By "your" you mean "kernel", right? ;)
> On Thu, Mar 11, 2021 at 4:37 PM syzbot
> wrote:
> >
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:
Hi all,
Tomorrow's linux-next merge of the akpm-current tree will get a
conflict in:
Documentation/admin-guide/kernel-parameters.txt
between commit:
f6e5aedf470b ("riscv: Add support for memtest")
from the risc-v tree and commit:
6b8f5ba8661b ("mm,memory_hotplug: add kernel boot option
syzbot has found a reproducer for the following issue on:
HEAD commit:47142ed6 net: dsa: bcm_sf2: Qualify phydev->dev_flags base..
git tree: net
console output: https://syzkaller.appspot.com/x/log.txt?x=11ccd12ad0
kernel config: https://syzkaller.appspot.com/x/.config?x=eec733599e95
On 3/11/21 9:24 PM, Badhri Jagan Sridharan wrote:
> The change exposes the data_role and the orientation as a extcon
> interface for configuring the USB data controller.
>
> Signed-off-by: Badhri Jagan Sridharan
> ---
> Changes since V1:
> - Dropped changes related to get_/set_current_limit and p
On 3/12/2021 1:52 PM, Jason Wang wrote:
On 2021/3/11 3:19 下午, Zhu, Lingshan wrote:
On 3/11/2021 2:20 PM, Jason Wang wrote:
On 2021/3/11 12:16 下午, Zhu Lingshan wrote:
On 3/11/2021 11:20 AM, Jason Wang wrote:
On 2021/3/10 5:00 下午, Zhu Lingshan wrote:
vDPA requres VIRTIO_F_ACCESS_PLAT
Hello,
Here is the 2nd version of the series to fix the stacktrace with kretprobe.
The 1st series is here;
https://lore.kernel.org/bpf/161495873696.346821.10161501768906432924.stgit@devnote2/
In this version I merged the ORC unwinder fix for kretprobe which discussed in
the
previous thread. [3
Commit e792ff804f49 ("ia64: kprobes: Use generic kretprobe trampoline handler")
missed to pass the wrong trampoline address (it passes the descriptor address
instead of function entry address).
This fixes it to pass correct trampoline address to
__kretprobe_trampoline_handler().
This also changes
Replace arch_deref_entry_point() with dereference_function_descriptor()
because those are doing same thing.
Signed-off-by: Masami Hiramatsu
---
arch/ia64/kernel/kprobes.c|5 -
arch/powerpc/kernel/kprobes.c | 11 ---
include/linux/kprobes.h |1 -
kernel/kprobes.c
Remove trampoline_address from kretprobe_trampoline_handler().
Instead of passing the address, kretprobe_trampoline_handler()
can use new kretprobe_trampoline_addr().
Signed-off-by: Masami Hiramatsu
---
Changes in v2:
- Remove arch_deref_entry_point() from comment.
---
arch/arc/kernel/kprobe
Recover the return address on the stack which changed by the
kretprobe. Note that this does not recover the address on the
!current stack trace if CONFIG_ARCH_STACKWALK=n because old
stack trace interface doesn't lock the stack in the generic
stack_trace_save*() functions.
So with this patch, ftra
From: Josh Poimboeuf
Add UNWIND_HINT_FUNC on kretporbe_trampoline code so that ORC
information is generated on the kretprobe_trampoline correctly.
Signed-off-by: Josh Poimboeuf
---
[MH] Add patch description.
---
arch/x86/include/asm/unwind_hints.h |5 +
arch/x86/kernel/kprobes/core.c
Add instruction_pointer_set() API for arc.
Signed-off-by: Masami Hiramatsu
---
arch/arc/include/asm/ptrace.h |5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arc/include/asm/ptrace.h b/arch/arc/include/asm/ptrace.h
index 4c3c9be5bd16..cca8d6583e31 100644
--- a/arch/arc/include/as
Add instruction_pointer_set() API for ia64.
Signed-off-by: Masami Hiramatsu
---
arch/ia64/include/asm/ptrace.h |6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/ia64/include/asm/ptrace.h b/arch/ia64/include/asm/ptrace.h
index b3aa46090101..dbd9e85cbc77 100644
--- a/arch/ia64/incl
On Thu, Mar 11, 2021 at 6:25 PM Dmitry Vyukov wrote:
>
> On Thu, Mar 11, 2021 at 2:30 PM Arnd Bergmann wrote:
> >
> > On Thu, Mar 11, 2021 at 12:38 PM Dmitry Vyukov wrote:
> > >
> > > The instances found few arm64-specific issues that we have not
> > > observed on other instances:
> >
> > I've h
To simplify the stacktrace with pt_regs from kretprobe handler,
set the correct return address to the instruction pointer in
the pt_regs before calling kretprobe handlers.
Suggested-by: Josh Poimboeuf
Signed-off-by: Masami Hiramatsu
---
kernel/kprobes.c |3 +++
1 file changed, 3 insertions(
Since the kretprobe replaces the function return address with
the kretprobe_trampoline on the stack, the ORC unwinder can not
continue the stack unwinding at that point.
To fix this issue, correct state->ip as like as function-graph
tracer in the unwind_next_frame().
Signed-off-by: Masami Hiramat
Since the stacktrace API fixup the kretprobed address correctly,
there is no need to convert the "kretprobe_trampoline" to
"[unknown/kretprobe'd]" anymore. Remove it.
Signed-off-by: Masami Hiramatsu
Acked-by: Steven Rostedt (VMware)
---
kernel/trace/trace_output.c | 27 --
On 3/11/21 10:31 PM, Viresh Kumar wrote:
> On 11-03-21, 17:27, Frank Rowand wrote:
>> On 3/9/21 11:35 PM, Viresh Kumar wrote:
>>> Viresh Kumar (4):
>>> kbuild: Simplify builds with CONFIG_OF_ALL_DTBS
>>> kbuild: Allow .dtso format for overlay source files
>>> of: unittest: Create overlay_comm
Current implementation only supports DT, now add ACPI support.
Note that compared to device of 'fsl,qoriq-gpio', LS1028A and
LS1088A's GPIO have no extra programming, so simplify related checking.
Signed-off-by: Ran Wang
---
drivers/gpio/gpio-mpc8xxx.c | 50 +++--
Hi Laurent
On Fri, Mar 12, 2021 at 12:30 AM Laurent Pinchart
wrote:
>
> Hi Ricardo,
>
> On Thu, Mar 11, 2021 at 11:59:27PM +0100, Ricardo Ribalda Delgado wrote:
> > On Thu, Mar 11, 2021 at 11:53 PM Laurent Pinchart wrote:
> > > On Thu, Mar 11, 2021 at 11:19:43PM +0100, Ricardo Ribalda wrote:
> >
So with the new kmap_local interface is it possible / advisable to
use local kmaps over code that might schedule(), e.g. to wait for I/O?
On Thu, Mar 11, 2021 at 09:41:03PM +0100, Loic Poulain wrote:
> This change introduces initial support for a WWAN subsystem. Given the
> complexity and heterogeneity of existing WWAN hardwares and interfaces,
> there is no strict definition of what a WWAN device is and how it should
> be represente
On 2021/3/12 2:40 下午, Zhu, Lingshan wrote:
On 3/12/2021 1:52 PM, Jason Wang wrote:
On 2021/3/11 3:19 下午, Zhu, Lingshan wrote:
On 3/11/2021 2:20 PM, Jason Wang wrote:
On 2021/3/11 12:16 下午, Zhu Lingshan wrote:
On 3/11/2021 11:20 AM, Jason Wang wrote:
On 2021/3/10 5:00 下午, Zhu Lings
On Thu, Mar 11, 2021 at 10:04 PM Aditya wrote:
>
> On 10/3/21 11:49 am, Lukas Bulwahn wrote:
> > On Tue, Mar 9, 2021 at 10:24 PM Aditya wrote:
> >>
> >> On 9/3/21 7:00 pm, Markus Heiser wrote:
> >>>
> >>> Am 09.03.21 um 13:53 schrieb Aditya Srivastava:
> Starting commented lines in a file mo
allyesconfig
powerpc allmodconfig
powerpc allnoconfig
x86_64 randconfig-a006-20210311
x86_64 randconfig-a001-20210311
x86_64 randconfig-a005-20210311
x86_64 randconfig-a002-20210311
x86_64
Hi Viresh,
On 3/11/21 10:47 PM, Viresh Kumar wrote:
> On 10-03-21, 20:24, Masahiro Yamada wrote:
>> Even without "-I dts",
>>
>>inform = guess_input_format(arg, "dts");
>>
>> seems to fall back to "dts" anyway,
>> but I guess you wanted to make this explicit, correct?
>
>
>>> +# Required for
Hello, Dear Sami Tolvanen.
Thank you for reply.
> I agree that we shouldn't allow this, at least not without a warning, but
> out of curiosity, do you actually have a situation where this could happen?
> One ideally shouldn't be passing untrusted parameters to dm-verity.
Of course, I don't think
On Thu, Mar 11, 2021 at 10:39 PM Guenter Roeck wrote:
>
> On 3/11/21 9:24 PM, Badhri Jagan Sridharan wrote:
> > The change exposes the data_role and the orientation as a extcon
> > interface for configuring the USB data controller.
> >
> > Signed-off-by: Badhri Jagan Sridharan
> > ---
> > Changes
On Thu, Mar 11, 2021 at 10:34 PM Greg Kroah-Hartman
wrote:
>
> On Fri, Mar 12, 2021 at 07:33:45AM +0100, Greg Kroah-Hartman wrote:
> > On Thu, Mar 11, 2021 at 09:24:42PM -0800, Badhri Jagan Sridharan wrote:
> > > This change adds chip callbacks for the following operations:
> > > 1. Notifying port
Hello,
syzbot found the following issue on:
HEAD commit:05a59d79 Merge git://git.kernel.org:/pub/scm/linux/kernel/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=15b8820ad0
kernel config: https://syzkaller.appspot.com/x/.config?x=750735fdbc630971
das
On 11/03/2021 23:19, Ricardo Ribalda wrote:
> Fixes v4l2-compliance:
>
> Format ioctls (Input 0):
> warn: v4l2-test-formats.cpp(1339): S_PARM is supported but
> doesn't report V4L2_CAP_TIMEPERFRAME
> fail: v4l2-test-formats.cpp(1241): node->has_frmintervals &&
> !
On 11/03/2021 23:19, Ricardo Ribalda wrote:
> The device is doing something unspected with the control. Either because
> the protocol is not properly implemented or there has been a HW error.
>
> Fixes v4l2-compliance:
>
> Control ioctls (Input 0):
> fail: v4l2-test-controls.cpp(4
Random spelling fixes throughout the file.
Signed-off-by: Bhaskar Chowdhury
---
drivers/net/ethernet/dec/tulip/pnic2.c | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git a/drivers/net/ethernet/dec/tulip/pnic2.c
b/drivers/net/ethernet/dec/tulip/pnic2.c
index 412adaa7fdf8
On 3/12/2021 3:00 PM, Jason Wang wrote:
On 2021/3/12 2:40 下午, Zhu, Lingshan wrote:
On 3/12/2021 1:52 PM, Jason Wang wrote:
On 2021/3/11 3:19 下午, Zhu, Lingshan wrote:
On 3/11/2021 2:20 PM, Jason Wang wrote:
On 2021/3/11 12:16 下午, Zhu Lingshan wrote:
On 3/11/2021 11:20 AM, Jason Wa
On 3/12/21 1:03 AM, Frank Rowand wrote:
> Hi Viresh,
>
> On 3/11/21 10:47 PM, Viresh Kumar wrote:
>> On 10-03-21, 20:24, Masahiro Yamada wrote:
>>> Even without "-I dts",
>>>
>>>inform = guess_input_format(arg, "dts");
>>>
>>> seems to fall back to "dts" anyway,
>>> but I guess you wanted to m
On 12-03-21, 01:09, Frank Rowand wrote:
> I suggested having the .dtso files include the .dts file because that is a
> relatively
> small and easy change to test. What would probably make more sense is the
> rename
> the existing overlay .dts files to be .dtso files and then for each overlay
>
On 11/03/2021 23:19, Ricardo Ribalda wrote:
> According to the doc:
> The, in hindsight quite poor, solution for that is to set error_idx to
> count if the validation failed.
I think this needs a bit more explanation. How about this:
"If an error is found when validating the list of controls pass
On Thu, Mar 11, 2021 at 9:12 PM Johannes Weiner wrote:
>
> On Tue, Mar 09, 2021 at 06:07:15PM +0800, Muchun Song wrote:
> > We want to reuse the obj_cgroup APIs to charge the kmem pages.
> > If we do that, we should store an object cgroup pointer to
> > page->memcg_data for the kmem pages.
> >
> >
On 12/03/2021 00:38, Laurent Pinchart wrote:
> Hi Ricardo,
>
> Thank you for the patch.
>
> On Thu, Mar 11, 2021 at 11:19:46PM +0100, Ricardo Ribalda wrote:
>> All the entities must have a unique name.
>>
>> Fixes v4l2-compliance:
>> Media Controller ioctls:
>> fail: v4l2-test-med
>>> > This is a patch for managing L2P map in HPB module.
>>> >
>>> > The HPB divides logical addresses into several regions. A region
>>> > consists
>>> > of several sub-regions. The sub-region is a basic unit where L2P
>>> > mapping is
>>> > managed. The driver loads L2P mapping data of each sub-
Hello,
On 2021/3/12 13:49, Namhyung Kim wrote:
Hi,
On Fri, Mar 12, 2021 at 12:24 PM Yang Jihong wrote:
Hello, Namhyung
On 2021/3/11 22:42, Namhyung Kim wrote:
Hi,
On Thu, Mar 11, 2021 at 5:48 PM Yang Jihong wrote:
Hello,
On 2021/3/6 16:28, Yang Jihong wrote:
In hist__find_annotation
From: Junlin Yang
r is "u32" always >= 0,mipi_dsi_create_packet may return little than zero.
so r < 0 condition is never accessible.
Fixes coccicheck warnings:
./drivers/gpu/drm/omapdrm/dss/dsi.c:2155:5-6:
WARNING: Unsigned expression compared with zero: r < 0
Signed-off-by: Junlin Yang
---
d
-20210312
i386 randconfig-a004-20210312
i386 randconfig-a006-20210312
i386 randconfig-a001-20210311
i386 randconfig-a003-20210311
i386 randconfig-a002-20210311
i386 randconfig-a004-20210311
i386
On 3/11/21 11:05 PM, Bhaskar Chowdhury wrote:
>
> Random spelling fixes throughout the file.
>
> Signed-off-by: Bhaskar Chowdhury
> ---
> drivers/net/ethernet/dec/tulip/pnic2.c | 8
> 1 file changed, 4 insertions(+), 4 deletions(-)
>
> diff --git a/drivers/net/ethernet/dec/tulip/pnic2
Rob Herring wrote on Thu, 11 Mar 2021 16:40:56 -0700:
> The example for the Silvaco I3C master doesn't match the schema's
> compatible string. Fix it.
>
> Cc: Miquel Raynal
> Cc: Conor Culhane
> Cc: Alexandre Belloni
> Cc: linux-...@lists.infradead.org
> Signed-off-by: Rob Herring
> ---
>
Hi Laurent,
On Fri, Mar 12, 2021 at 03:25:11AM +0200, Laurent Pinchart wrote:
> Hi Rob,
>
> Thank you for the patch.
>
> On Thu, Mar 11, 2021 at 04:40:42PM -0700, Rob Herring wrote:
> > Now that we have the graph schema, convert the video-mux binding to DT
> > schema.
> >
> > Cc: Sakari Ailus
All comment lines inside the comment block have been aligned.
Every line of comment starts with a * (uniformity in code).
Signed-off-by: Shubhankar Kuranagatti
---
net/ipv4/route.c | 97
1 file changed, 49 insertions(+), 48 deletions(-)
diff --gi
Static analyzer tool found that the ret variable is not initialized but
code expects ret value >=0 when pinconf is skipped in the first pinmux
loop. The same expectation is for pinmux in a pinconf loop.
That's why initialize ret to 0 to avoid uninitialized ret value in first
loop or reusing ret val
This patchset intends to reduce time needed for processing memory
hotplug/hotunplug in hash guests.
The first one, makes sure guests with pagesize over 4k don't need to
go through HPT resize-downs after memory hotplug.
The second and third patches make hotplug / hotunplug perform a single
HPT res
Because hypervisors may need to create HPTs without knowing the guest
page size, the smallest used page-size (4k) may be chosen, resulting in
a HPT that is possibly bigger than needed.
On a guest with bigger page-sizes, the amount of entries for HTP may be
too high, causing the guest to ask for a
During memory hotunplug, after each LMB is removed, the HPT may be
resized-down if it would map a max of 4 times the current amount of memory.
(2 shifts, due to introduced histeresis)
It usually is not an issue, but it can take a lot of time if HPT
resizing-down fails. This happens because resize
Every time a memory hotplug happens, and the memory limit crosses a 2^n
value, it may be necessary to perform HPT resizing-up, which can take
some time (over 100ms in my tests).
It usually is not an issue, but it can take some time if a lot of memory
is added to a guest with little starting memory
On Thu, Mar 11, 2021 at 08:42:16AM -0800, Alexander Duyck wrote:
> > @@ -4919,6 +4934,9 @@ static inline bool prepare_alloc_pages(gfp_t
> > gfp_mask, unsigned int order,
> > struct alloc_context *ac, gfp_t *alloc_mask,
> > unsigned int *alloc_flags)
> > {
> > +
Updates binding document since the avc and vp8 hardware encoder in
MT8173 are now separated. Separate "mediatek,mt8173-vcodec-enc" to
"mediatek,mt8173-vcodec-enc-vp8" and "mediatek,mt8173-vcodec-enc".
This patch separates the two devices, it's a preparing patch for adding
device_link between the l
MTK H264 Encoder(VENC_SYS) and VP8 Encoder(VENC_LT_SYS) are two
independent hardware instance. They have their owner interrupt,
register mapping, and special clocks.
This patch separates them into two devices. This is a preparing
patch for adding device_link between the larbs and venc-device.
It's
There are two separate hardware encoder blocks inside MT8173.
Split the current mtk-vcodec-enc node to match the hardware architecture.
Acked-by: Tiffany Lin
Signed-off-by: Hsin-Yi Wang
Signed-off-by: Maoguang Meng
Signed-off-by: Irui Wang
---
arch/arm64/boot/dts/mediatek/mt8173.dtsi | 60 +++
The probe() function returns an uninitialized variable in the success
path. There is no need for the "err" variable at all, just delete it.
Fixes: b014e9fae7e7 ("regulator: Support ROHM BD9576MUF and BD9573MUF")
Signed-off-by: Dan Carpenter
---
drivers/regulator/bd9576-regulator.c | 11
There are a couple of issues in qat error handling. Those drivers tries to
release resources that is not initialized. This patch series tries to fix
crashes caused by incorrect error handling.
Tong Zhang (2):
crypto: qat - dont release uninitialized resources
crypto: qat: ADF_STATUS_PF_RUNNING
adf_vf_isr_resource_alloc() is not unwinding correctly when error
happens and it trys to release uninitialized resources.
To fix this, only release initialized resources.
[1.792594] [ cut here ]
[1.792845] Trying to free already-free IRQ 11
[1.793091] WARNING: C
ADF_STATUS_PF_RUNNING is (only) used and checked by adf_vf2pf_shutdown()
before calling adf_iov_putmsg()->mutex_lock(vf2pf_lock), however the
vf2pf_lock is initialized in adf_dev_init(), which can fail and when it
fail, the vf2pf_lock is either not initialized or destroyed, a subsequent
use of vf2
Hi,
Guenter Roeck wrote on Thu, Sep 17, 2020 at 07:16:17PM -0700:
> On 9/17/20 5:47 AM, Laurent Pinchart wrote:
> > On Wed, Sep 16, 2020 at 07:25:42PM -0700, Guenter Roeck wrote:
> >> Something seems to have gone wrong with v3 of this patch series.
> >> I am sure I sent it out, but I don't find it
Hello,
syzbot found the following issue on:
HEAD commit:28806e4d Merge tag 'media/v5.12-2' of git://git.kernel.org..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=11192342d0
kernel config: https://syzkaller.appspot.com/x/.config?x=6bcf96204c1b8e77
das
发件人: Dmitry Vyukov
发送时间: 2021年3月12日 14:30
收件人: Zhang, Qiang
抄送: Russell King - ARM Linux; Andrew Morton; LKML; Linux ARM; syzkaller-bugs
主题: Re: [PATCH] ARM: Fix incorrect use of smp_processor_id() by syzbot report
[Please note: This e-mail is from an EX
On 2021/3/12 14:10, Viresh Kumar wrote:
I saw your email about wrong version being sent, I already wrote some
reviews. Sending them anyway for FWIW :)
On 12-03-21, 21:33, Jie Deng wrote:
+struct virtio_i2c {
+ struct virtio_device *vdev;
+ struct completion completion;
+ str
Noticed missing header when build bpfilter helper:
CC [U] net/bpfilter/main.o
In file included from /usr/include/linux/errno.h:1,
from /usr/include/bits/errno.h:26,
from /usr/include/errno.h:28,
from net/bpfilter/main.c:4:
tools/inc
Uses the dma_set_mask_and_coherent helper to set venc
DMA bit mask to support 4GB~8GB range iova space.
Signed-off-by: Irui Wang
---
drivers/media/platform/mtk-vcodec/mtk_vcodec_enc_drv.c | 3 +++
1 file changed, 3 insertions(+)
diff --git a/drivers/media/platform/mtk-vcodec/mtk_vcodec_enc_drv.
Add MT8192 H264 venc driver and support H264 4K encoding on MT8192.
Signed-off-by: Irui Wang
---
This patch dependents on
"dt-bindings: media: mtk-vcodec: Separating mtk vcodec encoder node" [1]
We need "core_id" variable in device private data to indicate
current encoder driver.
Please also acc
From: Wei Yongjun
Fix to return negative error code -ENOMEM from the error handling
case instead of 0, as done elsewhere in this function.
Fixes: 53c218da220c ("driver/perf: Add PMU driver for the ARM DMC-620 memory
controller")
Reported-by: Hulk Robot
Signed-off-by: Wei Yongjun
---
drivers/
Add MT8192 venc driver's compatible and device private data.
Signed-off-by: Irui Wang
---
.../media/platform/mtk-vcodec/mtk_vcodec_drv.h| 1 +
.../platform/mtk-vcodec/mtk_vcodec_enc_drv.c | 15 +++
2 files changed, 16 insertions(+)
diff --git a/drivers/media/platform/mtk-v
Supports H264 4K (3840x2176) and level 5.1 encoding on MT8192.
Signed-off-by: Irui Wang
---
.../platform/mtk-vcodec/mtk_vcodec_enc.c | 58 ++-
.../platform/mtk-vcodec/venc/venc_h264_if.c | 4 ++
2 files changed, 47 insertions(+), 15 deletions(-)
diff --git a/drivers/medi
Updates binding document for mt8192 encoder driver.
Signed-off-by: Irui Wang
---
Documentation/devicetree/bindings/media/mediatek-vcodec.txt | 1 +
1 file changed, 1 insertion(+)
diff --git a/Documentation/devicetree/bindings/media/mediatek-vcodec.txt
b/Documentation/devicetree/bindings/media/
The mt8192 iommu support 0~16GB iova. We separate it to four banks:
0~4G; 4G~8G; 8G~12G; 12G~16G.
The "dma-ranges" could be used to adjust the bank we locate.
If we don't set this property. The default range always is 0~4G.
Here we don't have actual bus/parent concept here. And the iova
requirem
On 2021-03-11 6:50 AM, Chris Chiu wrote:
On Tue, Mar 9, 2021 at 11:29 PM Cezary Rojewski
wrote:
...
Topologies for most common skylake driver configurations:
- skl/kbl with i2s rt286
- apl/glk with i2s rt298
- with hda dsp
can be found in alsa-topology-conf [2].
Standard, official tool c
In register_test_dev_kmod, it calls free_test_dev_kmod() to free
test_dev. But free_test_dev_kmod() can't set the original pointer
test_dev to NULL, because the test_dev was passed by it's value
not reference.
Signed-off-by: Lv Yunlong
---
lib/test_kmod.c | 2 +-
1 file changed, 1 insertion(+),
> > diff --git a/drivers/scsi/ufs/ufshpb.c b/drivers/scsi/ufs/ufshpb.c
> > index 044fec9854a0..a8f8d13af21a 100644
> > --- a/drivers/scsi/ufs/ufshpb.c
> > +++ b/drivers/scsi/ufs/ufshpb.c
> > @@ -16,6 +16,8 @@
> > #include "ufshpb.h"
> > #include "../sd.h"
> >
> > +#define ACTIVATION_THRESHOLD 4 /
> > diff --git a/drivers/scsi/ufs/ufshpb.c b/drivers/scsi/ufs/ufshpb.c
> > index a8f8d13af21a..6f4fd22eaf2f 100644
> > --- a/drivers/scsi/ufs/ufshpb.c
> > +++ b/drivers/scsi/ufs/ufshpb.c
> > @@ -17,6 +17,7 @@
> > #include "../sd.h"
> >
> > #define ACTIVATION_THRESHOLD 4 /* 4 IOs */
> > +#define E
On 2021-03-11 16:04, Avri Altman wrote:
> diff --git a/drivers/scsi/ufs/ufshpb.c b/drivers/scsi/ufs/ufshpb.c
> index 044fec9854a0..a8f8d13af21a 100644
> --- a/drivers/scsi/ufs/ufshpb.c
> +++ b/drivers/scsi/ufs/ufshpb.c
> @@ -16,6 +16,8 @@
> #include "ufshpb.h"
> #include "../sd.h"
>
> +#define
-r021-20210311 (attached as .config)
compiler: mipsel-linux-gcc (GCC) 9.3.0
reproduce (this is a W=1 build):
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O
~/bin/make.cross
chmod +x ~/bin/make.cross
#
https://git.kernel.org/pub/scm/linux
> > From: Stefan Chulski
> >
> > According to Armada SoC architecture and design, all the PPv2 ports
> > which are populated on the same communication processor silicon die
> > (CP11x) share the same Classifier and Parser engines.
> >
> > Armada is an embedded platform and therefore there is a nee
On Thu, Mar 11, 2021 at 01:22:53PM +0530, Anshuman Khandual wrote:
>
> On 3/8/21 2:25 PM, Mike Rapoport wrote:
> > Hi Anshuman,
> >
> > On Mon, Mar 08, 2021 at 08:57:53AM +0530, Anshuman Khandual wrote:
> >> Platforms like arm and arm64 have redefined pfn_valid() because their early
> >> memory s
: 6 months ago
config: arm-randconfig-r005-20210311 (attached as .config)
compiler: clang version 13.0.0 (https://github.com/llvm/llvm-project
574a9dabc63ba1e7a04c08d4bde2eacd61b44ce1)
reproduce (this is a W=1 build):
wget
https://raw.githubusercontent.com/intel/lkp-tests/master/sbin
Hello,
syzbot found the following issue on:
HEAD commit:05a59d79 Merge git://git.kernel.org:/pub/scm/linux/kernel/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=100de152d0
kernel config: https://syzkaller.appspot.com/x/.config?x=b28ee088c7349c4d
das
401 - 500 of 1513 matches
Mail list logo
