[PATCH] vcodec: mediatek: Add V4L2_CAP_TIMEPERFRAME capability setting

This patch setting V4L2_CAP_TIMEPERFRAME capability in vidioc_venc_s/g_parm functions Signed-off-by: Tiffany Lin --- drivers/media/platform/mtk-vcodec/mtk_vcodec_enc.c |3 +++ 1 file changed, 3 insertions(+) diff --git

[PATCH] vcodec: mediatek: Add V4L2_CAP_TIMEPERFRAME capability setting

This patch setting V4L2_CAP_TIMEPERFRAME capability in vidioc_venc_s/g_parm functions Signed-off-by: Tiffany Lin --- drivers/media/platform/mtk-vcodec/mtk_vcodec_enc.c |3 +++ 1 file changed, 3 insertions(+) diff --git a/drivers/media/platform/mtk-vcodec/mtk_vcodec_enc.c

[PATCH 1/2] perf tools: Introduce memory mapping macros in mman-fix.h

tools/perf/trace/beauty/mmap.c, tools/perf/util/event.c and tools/perf/util/map.c depend on several macros in mman.h, which are lost on old systems like ubuntu 12.04. They are architecture dependened macros. Importing ./arch/*/include/uapi/asm/mman.h into tools/ is not easy because mman.h for some

[PATCH 1/2] perf tools: Introduce memory mapping macros in mman-fix.h

tools/perf/trace/beauty/mmap.c, tools/perf/util/event.c and tools/perf/util/map.c depend on several macros in mman.h, which are lost on old systems like ubuntu 12.04. They are architecture dependened macros. Importing ./arch/*/include/uapi/asm/mman.h into tools/ is not easy because mman.h for some

[PATCH 0/2] Fix mman macros using mman-fix.h

Macros in mman like MAP_HUGETLB are missed in some old systems, causes building error like this: CC /tmp/build/perf/arch/x86/util/perf_regs.o util/event.c: In function 'perf_event__synthesize_mmap_events': util/event.c:350: error: 'MAP_HUGETLB' undeclared (first use in this function)

[PATCH 2/2] perf tools: Fix mman macros using mman-fix.h

Use mman-fix.h to fix potential undefined macros in mman.h for building perf in old systems. Signed-off-by: Wang Nan Cc: Nilay Vaish Cc: Hou Pengyang Cc: He Kuang Cc: Arnaldo Carvalho de Melo

[PATCH 0/2] Fix mman macros using mman-fix.h

Macros in mman like MAP_HUGETLB are missed in some old systems, causes building error like this: CC /tmp/build/perf/arch/x86/util/perf_regs.o util/event.c: In function 'perf_event__synthesize_mmap_events': util/event.c:350: error: 'MAP_HUGETLB' undeclared (first use in this function)

[PATCH 2/2] perf tools: Fix mman macros using mman-fix.h

Use mman-fix.h to fix potential undefined macros in mman.h for building perf in old systems. Signed-off-by: Wang Nan Cc: Nilay Vaish Cc: Hou Pengyang Cc: He Kuang Cc: Arnaldo Carvalho de Melo --- tools/perf/trace/beauty/mmap.c | 63 +-

linux-next: Tree for Sep 6

Hi all, Changes since 20160905: The kbuild tree still had its build warnings for PowerPC, for which I reverted a commit. The tip tree gained a conflict against the kbuild tree. The akpm-current tree lost its build failure after I applied a supplied patch. Non-merge commits (relative to Linus

linux-next: Tree for Sep 6

Hi all, Changes since 20160905: The kbuild tree still had its build warnings for PowerPC, for which I reverted a commit. The tip tree gained a conflict against the kbuild tree. The akpm-current tree lost its build failure after I applied a supplied patch. Non-merge commits (relative to Linus

Re: [PATCH v16 0/4] Introduce usb charger framework to deal with the usb gadget power negotation

On Mon, Aug 29 2016, Baolin Wang wrote: > Hi Felipe, > > On 11 August 2016 at 11:14, Baolin Wang wrote: >> Hi Felipe, >> >> On 1 August 2016 at 15:09, Baolin Wang wrote: >>> Currently the Linux kernel does not provide any standard integration of

Re: [PATCH v16 0/4] Introduce usb charger framework to deal with the usb gadget power negotation

On Mon, Aug 29 2016, Baolin Wang wrote: > Hi Felipe, > > On 11 August 2016 at 11:14, Baolin Wang wrote: >> Hi Felipe, >> >> On 1 August 2016 at 15:09, Baolin Wang wrote: >>> Currently the Linux kernel does not provide any standard integration of this >>> feature that integrates the USB

RE: linux-next: manual merge of the char-misc tree with the net-next tree

> -Original Message- > From: Greg KH [mailto:g...@kroah.com] > Sent: Monday, September 5, 2016 5:04 PM > To: Stephen Rothwell > Cc: Arnd Bergmann ; David Miller ; > Networking ;

RE: linux-next: manual merge of the char-misc tree with the net-next tree

> -Original Message- > From: Greg KH [mailto:g...@kroah.com] > Sent: Monday, September 5, 2016 5:04 PM > To: Stephen Rothwell > Cc: Arnd Bergmann ; David Miller ; > Networking ; linux-n...@vger.kernel.org; linux- > ker...@vger.kernel.org; Stephen Hemminger ; > Vitaly Kuznetsov ; KY

[PATCH V2 2/2] mm: Add sysfs interface to dump each node's zonelist information

Each individual node in the system has a ZONELIST_FALLBACK zonelist and a ZONELIST_NOFALLBACK zonelist. These zonelists decide fallback order of zones during memory allocations. Sometimes it helps to dump these zonelists to see the priority order of various zones in them. Particularly platforms

[PATCH V2 1/2] mm: Export definition of 'zone_names' array through mmzone.h

zone_names[] is used to identify any zone given it's index which can be used in many other places. So exporting the definition through include/linux/mmzone.h header for it's broader access. Signed-off-by: Anshuman Khandual --- Changes in V2: - Removed the static and

[PATCH V2 2/2] mm: Add sysfs interface to dump each node's zonelist information

Each individual node in the system has a ZONELIST_FALLBACK zonelist and a ZONELIST_NOFALLBACK zonelist. These zonelists decide fallback order of zones during memory allocations. Sometimes it helps to dump these zonelists to see the priority order of various zones in them. Particularly platforms

[PATCH V2 1/2] mm: Export definition of 'zone_names' array through mmzone.h

zone_names[] is used to identify any zone given it's index which can be used in many other places. So exporting the definition through include/linux/mmzone.h header for it's broader access. Signed-off-by: Anshuman Khandual --- Changes in V2: - Removed the static and declared in mmzone.h per

[PATCH] x86: Put the num_processors++ code in a more suitable position

This is a code optimization. If checking the topology package map of apicid and cpu is failure, it will stop generating the processor info for that apicid and the disabled_cpus will plus one. However, the num-processors has already been added one above. That may cause the number of processors

[PATCH] x86: Put the num_processors++ code in a more suitable position

This is a code optimization. If checking the topology package map of apicid and cpu is failure, it will stop generating the processor info for that apicid and the disabled_cpus will plus one. However, the num-processors has already been added one above. That may cause the number of processors

RE: [PATCH v2] Btrfs: remove unnecessary code of chunk_root assignment in btrfs_read_chunk_tree.

Hi, Sean Fu > -Original Message- > From: Sean Fu [mailto:fxinr...@gmail.com] > Sent: Tuesday, September 06, 2016 11:51 AM > To: dste...@suse.com > Cc: c...@fb.com; anand.j...@oracle.com; fdman...@suse.com; > zhao...@cn.fujitsu.com; linux-kernel@vger.kernel.org; >

RE: [PATCH v2] Btrfs: remove unnecessary code of chunk_root assignment in btrfs_read_chunk_tree.

Hi, Sean Fu > -Original Message- > From: Sean Fu [mailto:fxinr...@gmail.com] > Sent: Tuesday, September 06, 2016 11:51 AM > To: dste...@suse.com > Cc: c...@fb.com; anand.j...@oracle.com; fdman...@suse.com; > zhao...@cn.fujitsu.com; linux-kernel@vger.kernel.org; >

Re: [PATCH v7 3/4] usb: dwc2: assert phy reset when waking up in rk3288 platform

Hi, On Sunday 04 September 2016 03:25 AM, Randy Li wrote: > On the rk3288 USB host-only port (the one that's not the OTG-enabled > port) the PHY can get into a bad state when a wakeup is asserted (not > just a wakeup from full system suspend but also a wakeup from > autosuspend). > > We can get

Re: [PATCH v7 3/4] usb: dwc2: assert phy reset when waking up in rk3288 platform

Hi, On Sunday 04 September 2016 03:25 AM, Randy Li wrote: > On the rk3288 USB host-only port (the one that's not the OTG-enabled > port) the PHY can get into a bad state when a wakeup is asserted (not > just a wakeup from full system suspend but also a wakeup from > autosuspend). > > We can get

Re: [PATCH] leds: Introduce userspace leds driver

Hi, > This driver creates a userspace leds driver similar to uinput. is the module really called leds-user as claimed by Kconfig? or rather uleds p. > New leds are created by opening /dev/uleds and writing a uleds_user_dev > struct. A new leds class device is registered with the name given in

Re: [PATCH] leds: Introduce userspace leds driver

Hi, > This driver creates a userspace leds driver similar to uinput. is the module really called leds-user as claimed by Kconfig? or rather uleds p. > New leds are created by opening /dev/uleds and writing a uleds_user_dev > struct. A new leds class device is registered with the name given in

[PATCH] sched/fair: Fix update_min_vruntime() to get proper min_vruntime

I am sorry for making you confused. The patch I posted one year ago, Commit 97a7142 'sched/fair: Make update_min_vruntime() more readable', has a bug, which you picked up. Please add this patch to fix it, or combine these two patches into one, or revert commit 97a7142. Whatever you want. Sorry.

[PATCH] sched/fair: Fix update_min_vruntime() to get proper min_vruntime

I am sorry for making you confused. The patch I posted one year ago, Commit 97a7142 'sched/fair: Make update_min_vruntime() more readable', has a bug, which you picked up. Please add this patch to fix it, or combine these two patches into one, or revert commit 97a7142. Whatever you want. Sorry.

[PATCH v2 0/3] perf report: Recognize hugetlb mapping as anon mapping

The requirement of this function is first proposed at 2015. Please refer to http://lkml.iu.edu/hypermail/linux/kernel/1506.2/02372.html http://lkml.iu.edu/hypermail/linux/kernel/1506.3/02290.html http://lkml.iu.edu/hypermail/linux/kernel/1506.3/03512.html For systems which use hugetlbfs, if a

[PATCH v2 1/3] perf tools: Recognize hugetlb mapping as anon mapping

Hugetlbfs mapping should be recognized as anon mapping so user has a chance to create /tmp/perf-.map file for symbol resolving. This patch utilizes MAP_HUGETLB to identify hugetlb mapping. After this patch, if perf is started before the program starts using huge pages (so perf gets MMAP2 events

[PATCH v2 1/3] perf tools: Recognize hugetlb mapping as anon mapping

Hugetlbfs mapping should be recognized as anon mapping so user has a chance to create /tmp/perf-.map file for symbol resolving. This patch utilizes MAP_HUGETLB to identify hugetlb mapping. After this patch, if perf is started before the program starts using huge pages (so perf gets MMAP2 events

[PATCH v2 0/3] perf report: Recognize hugetlb mapping as anon mapping

The requirement of this function is first proposed at 2015. Please refer to http://lkml.iu.edu/hypermail/linux/kernel/1506.2/02372.html http://lkml.iu.edu/hypermail/linux/kernel/1506.3/02290.html http://lkml.iu.edu/hypermail/linux/kernel/1506.3/03512.html For systems which use hugetlbfs, if a

[PATCH v2 2/3] tools lib api fs: Add hugetlbfs filesystem detector

Detect hugetlbfs. hugetlbfs__mountpoint() will be used during recording to help recorder identifying hugetlb mmaps: which should be recognized as anon mapping. Signed-off-by: Wang Nan Reviewed-by: Nilay Vaish Cc: Hou Pengyang

[PATCH v2 3/3] perf record: Mark MAP_HUGETLB during synthesizing mmap events

During synthesizing mmap events, add MAP_HUGETLB map flag if the source of mapping is file in hugetlbfs. After this patch, perf can identify hugetlb mapping even if perf is started after the mapping of huge pages (like perf top). Signed-off-by: Wang Nan Reviewed-by: Nilay

[PATCH v2 2/3] tools lib api fs: Add hugetlbfs filesystem detector

Detect hugetlbfs. hugetlbfs__mountpoint() will be used during recording to help recorder identifying hugetlb mmaps: which should be recognized as anon mapping. Signed-off-by: Wang Nan Reviewed-by: Nilay Vaish Cc: Hou Pengyang Cc: He Kuang Cc: Arnaldo Carvalho de Melo ---

[PATCH v2 3/3] perf record: Mark MAP_HUGETLB during synthesizing mmap events

During synthesizing mmap events, add MAP_HUGETLB map flag if the source of mapping is file in hugetlbfs. After this patch, perf can identify hugetlb mapping even if perf is started after the mapping of huge pages (like perf top). Signed-off-by: Wang Nan Reviewed-by: Nilay Vaish Cc: Hou

[PATCH 2/2] ASoC: rockchip: Add DP dai-links to the rk3399-gru machine driver

This patch adds DP audio output support to the rk3300-gru machine driver. Signed-off-by: Chris Zhong hyc...@chromium.org, broo...@kernel.org --- .../bindings/sound/rockchip,rk3399-gru-sound.txt | 13 +++--- sound/soc/rockchip/rk3399_gru_sound.c | 48

[PATCH 1/2] drm/rockchip: cdn-dp: support audio hot-plug

Issue hot-plug detection, EDID update, and ELD update notifications from DP drivers. Signed-off-by: Chris Zhong --- drivers/gpu/drm/rockchip/cdn-dp-core.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/gpu/drm/rockchip/cdn-dp-core.c

[PATCH 0/2] Add DP dai-links to the rk3399-gru machine driver

Hi This series patch is for the machine driver supporting for DP. It base on the DP drvier patches[0] and hdmi-notify patches[1], they are both in reviewing. [0] https://patchwork.kernel.org/patch/9315557/ https://patchwork.kernel.org/patch/9278077/ [1]

[PATCH 2/2] ASoC: rockchip: Add DP dai-links to the rk3399-gru machine driver

This patch adds DP audio output support to the rk3300-gru machine driver. Signed-off-by: Chris Zhong hyc...@chromium.org, broo...@kernel.org --- .../bindings/sound/rockchip,rk3399-gru-sound.txt | 13 +++--- sound/soc/rockchip/rk3399_gru_sound.c | 48 ++ 2

[PATCH 1/2] drm/rockchip: cdn-dp: support audio hot-plug

Issue hot-plug detection, EDID update, and ELD update notifications from DP drivers. Signed-off-by: Chris Zhong --- drivers/gpu/drm/rockchip/cdn-dp-core.c | 4 1 file changed, 4 insertions(+) diff --git a/drivers/gpu/drm/rockchip/cdn-dp-core.c b/drivers/gpu/drm/rockchip/cdn-dp-core.c

[PATCH 0/2] Add DP dai-links to the rk3399-gru machine driver

Hi This series patch is for the machine driver supporting for DP. It base on the DP drvier patches[0] and hdmi-notify patches[1], they are both in reviewing. [0] https://patchwork.kernel.org/patch/9315557/ https://patchwork.kernel.org/patch/9278077/ [1]

Re: [PATCH 0/7] perpcu rwsem, fs/locks and killing lglocks

On Mon, 2016-09-05 at 21:40 +0200, Peter Zijlstra wrote: > Hi all, > > Here are some patches that I've been sitting on for far too long now. Woohoo, goodbye to bad rubbish. FWIW, I plugged these into 4.8-rt (motto: if it's gonna go boom anywhere, it'll likely do so in rt), and am beating the

Re: [PATCH 0/7] perpcu rwsem, fs/locks and killing lglocks

On Mon, 2016-09-05 at 21:40 +0200, Peter Zijlstra wrote: > Hi all, > > Here are some patches that I've been sitting on for far too long now. Woohoo, goodbye to bad rubbish. FWIW, I plugged these into 4.8-rt (motto: if it's gonna go boom anywhere, it'll likely do so in rt), and am beating the

RE: [PATCH v10 5/5] drm/rockchip: Add dmc notifier in vop driver

> when in ddr frequency scaling process, vop can not do enable or > disable operation, since in dcf we check vop clock to see whether > vop work. If vop work, dcf do ddr frequency scaling when vop > in vblank status, and we need to read vop register to check whether > vop go into vblank status. If

RE: [PATCH v10 5/5] drm/rockchip: Add dmc notifier in vop driver

> when in ddr frequency scaling process, vop can not do enable or > disable operation, since in dcf we check vop clock to see whether > vop work. If vop work, dcf do ddr frequency scaling when vop > in vblank status, and we need to read vop register to check whether > vop go into vblank status. If

Re: [PATCH v2] ubifs: compress lines for immediate return

Hello Richard, Am 05.09.2016 um 15:32 schrieb Richard Weinberger: On 05.09.2016 15:05, Heiko Schocher wrote: @Richard: Should we just forget this patch? Let's drop it for now. It caused already a way more churn than a trivial style cleanup patch should... Yes! It was a too fast shoot ...

Re: [PATCH v2] ubifs: compress lines for immediate return

Hello Richard, Am 05.09.2016 um 15:32 schrieb Richard Weinberger: On 05.09.2016 15:05, Heiko Schocher wrote: @Richard: Should we just forget this patch? Let's drop it for now. It caused already a way more churn than a trivial style cleanup patch should... Yes! It was a too fast shoot ...

[v14.2 PATCH 5/5] drm/rockchip: cdn-dp: add cdn DP support for rk3399

Add support for cdn DP controller which is embedded in the rk3399 SoCs. The DP is compliant with DisplayPort Specification, Version 1.3, This IP is compatible with the rockchip type-c PHY IP. There is a uCPU in DP controller, it need a firmware to work, please put the firmware file to

[v14.2 PATCH 5/5] drm/rockchip: cdn-dp: add cdn DP support for rk3399

Add support for cdn DP controller which is embedded in the rk3399 SoCs. The DP is compliant with DisplayPort Specification, Version 1.3, This IP is compatible with the rockchip type-c PHY IP. There is a uCPU in DP controller, it need a firmware to work, please put the firmware file to

Re: [PATCH v4 2/3] mmc: core: Factor out the alignment of erase size

On Tue, Sep 06, 2016 at 10:55:11AM +0800, Baolin Wang wrote: > In order to clean up the mmc_erase() function and do some optimization > for erase size alignment, factor out the guts of erase size alignment > into mmc_align_erase_size() function. > > Signed-off-by: Baolin Wang

Re: [PATCH v4 2/3] mmc: core: Factor out the alignment of erase size

On Tue, Sep 06, 2016 at 10:55:11AM +0800, Baolin Wang wrote: > In order to clean up the mmc_erase() function and do some optimization > for erase size alignment, factor out the guts of erase size alignment > into mmc_align_erase_size() function. > > Signed-off-by: Baolin Wang > Tested-by: Shawn

Re: [PATCH 01/13] perf/core: Add perf_arch_regs and mask to perf_regs structure

On Thursday 01 September 2016 12:56 PM, Peter Zijlstra wrote: On Mon, Aug 29, 2016 at 02:30:46AM +0530, Madhavan Srinivasan wrote: It's a perennial request from hardware folks to be able to see the raw values of the pmu registers. Partly it's so that they can verify perf is doing what they

Re: [PATCH 01/13] perf/core: Add perf_arch_regs and mask to perf_regs structure

On Thursday 01 September 2016 12:56 PM, Peter Zijlstra wrote: On Mon, Aug 29, 2016 at 02:30:46AM +0530, Madhavan Srinivasan wrote: It's a perennial request from hardware folks to be able to see the raw values of the pmu registers. Partly it's so that they can verify perf is doing what they

Partnership Cooperation

Dear Friend, Your contact details came to me by recommendation, I am interested in investing in your country and I believe you have the capabilities of providing the needed assistance, solutions and advise in actualizing this, Let me know if you are willing to understake this task for me so we

Partnership Cooperation

Dear Friend, Your contact details came to me by recommendation, I am interested in investing in your country and I believe you have the capabilities of providing the needed assistance, solutions and advise in actualizing this, Let me know if you are willing to understake this task for me so we

Re: [PATCH] phy: da8xx-usb: Fix syscon device name

On Tuesday 06 September 2016 01:15 AM, David Lechner wrote: > The syscon device in board config/device tree has been renamed. > > Signed-off-by: David Lechner merged, thanks. -Kishon > --- > > This is a follow-up of the "da8xx USB PHY platform devices and clocks" patch

Re: [PATCH] phy: da8xx-usb: Fix syscon device name

On Tuesday 06 September 2016 01:15 AM, David Lechner wrote: > The syscon device in board config/device tree has been renamed. > > Signed-off-by: David Lechner merged, thanks. -Kishon > --- > > This is a follow-up of the "da8xx USB PHY platform devices and clocks" patch > series. Just a

Re: [v14 PATCH 2/5] phy: Add USB Type-C PHY driver for rk3399

On Wednesday 24 August 2016 10:47 AM, Chris Zhong wrote: > Add a PHY provider driver for the rk3399 SoC Type-c PHY. The USB > Type-C PHY is designed to support the USB3 and DP applications. > The USB3 operates in SuperSpeed mode and the DP can operate at RBR, > HBR and HBR2 data rates. This

Re: [v14 PATCH 2/5] phy: Add USB Type-C PHY driver for rk3399

On Wednesday 24 August 2016 10:47 AM, Chris Zhong wrote: > Add a PHY provider driver for the rk3399 SoC Type-c PHY. The USB > Type-C PHY is designed to support the USB3 and DP applications. > The USB3 operates in SuperSpeed mode and the DP can operate at RBR, > HBR and HBR2 data rates. This

Re: [v14 PATCH 2/5] phy: Add USB Type-C PHY driver for rk3399

Hi chanwoo, On Monday 05 September 2016 06:58 AM, Chanwoo Choi wrote: > Dear all, > > On 2016년 08월 24일 14:17, Chris Zhong wrote: >> Add a PHY provider driver for the rk3399 SoC Type-c PHY. The USB >> Type-C PHY is designed to support the USB3 and DP applications. >> The USB3 operates in

Re: [v14 PATCH 2/5] phy: Add USB Type-C PHY driver for rk3399

Hi chanwoo, On Monday 05 September 2016 06:58 AM, Chanwoo Choi wrote: > Dear all, > > On 2016년 08월 24일 14:17, Chris Zhong wrote: >> Add a PHY provider driver for the rk3399 SoC Type-c PHY. The USB >> Type-C PHY is designed to support the USB3 and DP applications. >> The USB3 operates in

[PATCH 3/4] drm/fsl-dcu: update all registers on flush

Use the UPDATE_MODE READREG bit to initiate a register transfer on flush. This makes sure that we flush all registers only once for all planes. Signed-off-by: Stefan Agner --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c | 3 +++ drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_plane.c | 5

[PATCH 3/4] drm/fsl-dcu: update all registers on flush

Use the UPDATE_MODE READREG bit to initiate a register transfer on flush. This makes sure that we flush all registers only once for all planes. Signed-off-by: Stefan Agner --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_crtc.c | 3 +++ drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_plane.c | 5 - 2 files

[PATCH 0/4] drm/fsl-dcu: add overlay and cursor plane support

This patchset adds overlay and cursor plane support. It also fixes some issues uncovered during implementation of this. However, the plane updates currently causes the display to flicker for unknown reasons. As far as I can tell, the CRTC atomic_flush should trigger the update correctly via

Re: [PATCH v2 3/8] regulator: axp20x: support AXP806 variant

Hi Lee, On Fri, Sep 2, 2016 at 4:23 AM, Mark Brown wrote: > On Sat, Aug 27, 2016 at 03:55:39PM +0800, Chen-Yu Tsai wrote: >> The X-Powers AXP806 PMIC has a new set of buck and LDO regulators, and >> also a switch. The buck regulators support teaming into multi-phase >>

[PATCH 1/4] drm/fsl-dcu: support overlay and cursor planes

Add support for overlay plane and a cursor plane. The driver uses the topmost plane as cursor plane. The DCU IP would have dedicated cursor support, but that lacks proper color support and hence is not practical to use for Linux systems. Signed-off-by: Stefan Agner ---

[PATCH 1/4] drm/fsl-dcu: support overlay and cursor planes

Add support for overlay plane and a cursor plane. The driver uses the topmost plane as cursor plane. The DCU IP would have dedicated cursor support, but that lacks proper color support and hence is not practical to use for Linux systems. Signed-off-by: Stefan Agner ---

[PATCH 0/4] drm/fsl-dcu: add overlay and cursor plane support

This patchset adds overlay and cursor plane support. It also fixes some issues uncovered during implementation of this. However, the plane updates currently causes the display to flicker for unknown reasons. As far as I can tell, the CRTC atomic_flush should trigger the update correctly via

Re: [PATCH v2 3/8] regulator: axp20x: support AXP806 variant

Hi Lee, On Fri, Sep 2, 2016 at 4:23 AM, Mark Brown wrote: > On Sat, Aug 27, 2016 at 03:55:39PM +0800, Chen-Yu Tsai wrote: >> The X-Powers AXP806 PMIC has a new set of buck and LDO regulators, and >> also a switch. The buck regulators support teaming into multi-phase >> groups, with A+B, A+B+C,

[PATCH 4/4] drm/fsl-dcu: do not update when modifying irq registers

The IRQ status and mask registers are not "double buffered" according to the reference manual. Hence, there is no extra transfer/update write needed when modifying these registers. Signed-off-by: Stefan Agner --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 4 1 file

[PATCH 2/4] drm/fsl-dcu: respect pos/size register sizes

Mask the size and position values to avoid mutual overwriting. Especially, a negative X position caused the Y position to be overwritten with 0xfff too. This has been observed when using a layer as cursor layer. Signed-off-by: Stefan Agner ---

[PATCH 4/4] drm/fsl-dcu: do not update when modifying irq registers

The IRQ status and mask registers are not "double buffered" according to the reference manual. Hence, there is no extra transfer/update write needed when modifying these registers. Signed-off-by: Stefan Agner --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.c | 4 1 file changed, 4 deletions(-)

[PATCH 2/4] drm/fsl-dcu: respect pos/size register sizes

Mask the size and position values to avoid mutual overwriting. Especially, a negative X position caused the Y position to be overwritten with 0xfff too. This has been observed when using a layer as cursor layer. Signed-off-by: Stefan Agner --- drivers/gpu/drm/fsl-dcu/fsl_dcu_drm_drv.h | 8

RE: [PATCH v3 0/3] Make core_pattern support namespace

Ping > -Original Message- > From: Zhao Lei [mailto:zhao...@cn.fujitsu.com] > Sent: Monday, August 29, 2016 8:07 PM > To: linux-kernel@vger.kernel.org > Cc: contain...@lists.linux-foundation.org; Eric W. Biederman > ; Mateusz Guzik ; > Kamezawa

RE: [PATCH v3 0/3] Make core_pattern support namespace

Ping > -Original Message- > From: Zhao Lei [mailto:zhao...@cn.fujitsu.com] > Sent: Monday, August 29, 2016 8:07 PM > To: linux-kernel@vger.kernel.org > Cc: contain...@lists.linux-foundation.org; Eric W. Biederman > ; Mateusz Guzik ; > Kamezawa Hiroyuki ; Stéphane Graber > ; Andrei Vagin ;

linux-next: manual merge of the tip tree with the kbuild tree

Hi all, Today's linux-next merge of the tip tree got a conflict in: arch/x86/lib/memcpy_64.S arch/x86/kernel/x8664_ksyms_64.c between commit: 784d5699eddc ("x86: move exports to actual definitions") from the kbuild tree and commit: 9a6fb28a355d ("x86/mce: Improve memcpy_mcsafe()")

linux-next: manual merge of the tip tree with the kbuild tree

Hi all, Today's linux-next merge of the tip tree got a conflict in: arch/x86/lib/memcpy_64.S arch/x86/kernel/x8664_ksyms_64.c between commit: 784d5699eddc ("x86: move exports to actual definitions") from the kbuild tree and commit: 9a6fb28a355d ("x86/mce: Improve memcpy_mcsafe()")

Re: [PATCH v10 5/5] drm/rockchip: Add dmc notifier in vop driver

tch --base= (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on] [Check https://git-scm.com/docs/git-format-patch for more information] url: https://github.com/0day-ci/linux/commits/Lin-Huang/rk3399-support-ddr-frequency-scaling/20160

Re: [PATCH v10 5/5] drm/rockchip: Add dmc notifier in vop driver

tch --base= (or --base=auto for convenience) to record what (public, well-known) commit your patch series was built on] [Check https://git-scm.com/docs/git-format-patch for more information] url: https://github.com/0day-ci/linux/commits/Lin-Huang/rk3399-support-ddr-frequency-scaling/20160

Re: ACPI-APEI-HEST: Fine-tuning for three function implementations

> Like in the other patch series I've just commented, Thanks for your quick response. > please put all label renames into one patch. Could you accept these update suggestions generally? I would prefer to avoid squashing special changes together by default. Regards, Markus

Re: ACPI-APEI-HEST: Fine-tuning for three function implementations

> Like in the other patch series I've just commented, Thanks for your quick response. > please put all label renames into one patch. Could you accept these update suggestions generally? I would prefer to avoid squashing special changes together by default. Regards, Markus

Re: [PATCH] Btrfs: remove unnecessary code of chunk_root assignment in btrfs_read_chunk_tree.

On 9/5/16 11:05 PM, Jeff Mahoney wrote: > On 9/5/16 3:56 AM, Qu Wenruo wrote: >> >> >> At 09/05/2016 09:19 AM, Zhao Lei wrote: >>> Hi, Sean Fu >>> From: Sean Fu [mailto:fxinr...@gmail.com] Sent: Sunday, September 04, 2016 7:54 PM To: dste...@suse.com Cc: c...@fb.com;

Re: [PATCH] Btrfs: remove unnecessary code of chunk_root assignment in btrfs_read_chunk_tree.

On 9/5/16 11:05 PM, Jeff Mahoney wrote: > On 9/5/16 3:56 AM, Qu Wenruo wrote: >> >> >> At 09/05/2016 09:19 AM, Zhao Lei wrote: >>> Hi, Sean Fu >>> From: Sean Fu [mailto:fxinr...@gmail.com] Sent: Sunday, September 04, 2016 7:54 PM To: dste...@suse.com Cc: c...@fb.com;

Re: [PATCH] ASoC: sun4i-codec: Distinguish sun4i from sun7i

On Tue, Sep 6, 2016 at 3:24 AM, Danny Milosavljevic wrote: > ASoC: sun4i-codec: Distinguish sun4i from sun7i > > Introduce mechanism to detect sun7i and provide a different regmap, codec > and different controls for it - different compared to sun4i Allwinner A10. > > The

Re: [PATCH] speakup: Add spinlock in synth_direct_store

On Monday 05 September 2016 06:47 PM, Pavel Andrianov wrote: > All operations with synth buffer should be protected, > as there are global pointers, which should be modified atomically. > > Found by Linux Driver Verification project (linuxtesting.org) > > Signed-off-by: Pavel Andrianov

Re: [PATCH] ASoC: sun4i-codec: Distinguish sun4i from sun7i

On Tue, Sep 6, 2016 at 3:24 AM, Danny Milosavljevic wrote: > ASoC: sun4i-codec: Distinguish sun4i from sun7i > > Introduce mechanism to detect sun7i and provide a different regmap, codec > and different controls for it - different compared to sun4i Allwinner A10. > > The controls will be extended

Re: [PATCH] speakup: Add spinlock in synth_direct_store

On Monday 05 September 2016 06:47 PM, Pavel Andrianov wrote: > All operations with synth buffer should be protected, > as there are global pointers, which should be modified atomically. > > Found by Linux Driver Verification project (linuxtesting.org) > > Signed-off-by: Pavel Andrianov

Re: [PATCH v2 3/3] arm: dts: thermal: add thermal/auxadc node.

Dear Rui, On Tue, 2016-09-06 at 08:30 +0800, Zhang Rui wrote: > On 二, 2016-09-06 at 08:24 +0800, Zhang Rui wrote: > > On 四, 2016-08-18 at 11:50 +0800, Dawei Chien wrote: > > > > > > This adds the thermal controller and auxadc nodes > > > to the Mediatek MT2701 dtsi file. > > > > > >

Re: ACPI-video: Fine-tuning for several function implementations

> I'd prefer this to be combined into fewer patches > that each will address several issues of one type, I understand your concern a bit in principle. > ie. put all label renames into one patch, Are any of my update suggestions controversial here? > all size determination improvements into

Re: [PATCH v2 3/3] arm: dts: thermal: add thermal/auxadc node.

Dear Rui, On Tue, 2016-09-06 at 08:30 +0800, Zhang Rui wrote: > On 二, 2016-09-06 at 08:24 +0800, Zhang Rui wrote: > > On 四, 2016-08-18 at 11:50 +0800, Dawei Chien wrote: > > > > > > This adds the thermal controller and auxadc nodes > > > to the Mediatek MT2701 dtsi file. > > > > > >

Re: ACPI-video: Fine-tuning for several function implementations

> I'd prefer this to be combined into fewer patches > that each will address several issues of one type, I understand your concern a bit in principle. > ie. put all label renames into one patch, Are any of my update suggestions controversial here? > all size determination improvements into

[PATCH] mfd: Add HiSilicon Flash Memory Controller(FMC) driver

From: Shunquan Lin This patch adds driver support for HiSilicon Flash Memory Controller(FMC). HiSilicon FMC is a multi-functions device which supports SPI Nor flash controller, SPI nand Flash controller and parallel nand flash controller. Signed-off-by: Shunquan Lin

[PATCH] mfd: Add HiSilicon Flash Memory Controller(FMC) driver

From: Shunquan Lin This patch adds driver support for HiSilicon Flash Memory Controller(FMC). HiSilicon FMC is a multi-functions device which supports SPI Nor flash controller, SPI nand Flash controller and parallel nand flash controller. Signed-off-by: Shunquan Lin ---

drivers/nvme/host/nvme.h:217:20: error: 'REQ_OP_DISCARD' undeclared

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: c6935931c1894ff857616ff8549b61236a19148f commit: aa71987472a974f4f6dc4be377720564079ef42e nvme: fabrics drivers don't need the nvme-pci driver date: 2 weeks ago config: i386-randconfig-h0-09052023

drivers/nvme/host/nvme.h:217:20: error: 'REQ_OP_DISCARD' undeclared

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: c6935931c1894ff857616ff8549b61236a19148f commit: aa71987472a974f4f6dc4be377720564079ef42e nvme: fabrics drivers don't need the nvme-pci driver date: 2 weeks ago config: i386-randconfig-h0-09052023

Re: [PATCH] Btrfs: remove unnecessary code of chunk_root assignment in btrfs_read_chunk_tree.

On 9/5/16 3:56 AM, Qu Wenruo wrote: > > > At 09/05/2016 09:19 AM, Zhao Lei wrote: >> Hi, Sean Fu >> >>> From: Sean Fu [mailto:fxinr...@gmail.com] >>> Sent: Sunday, September 04, 2016 7:54 PM >>> To: dste...@suse.com >>> Cc: c...@fb.com; anand.j...@oracle.com; fdman...@suse.com; >>>

drivers/nvme/host/core.c:202:2: note: in expansion of macro 'spin_lock_irqsave'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: c6935931c1894ff857616ff8549b61236a19148f commit: aa71987472a974f4f6dc4be377720564079ef42e nvme: fabrics drivers don't need the nvme-pci driver date: 2 weeks ago config: x86_64-randconfig-n0-09052021

Re: [PATCH v2 4/7] dts: sun8i-h3: add UART1-3 to Orange Pi Plus

On Tue, Sep 6, 2016 at 3:31 AM, Maxime Ripard wrote: > Hi Jorik, > > On Sat, Sep 03, 2016 at 02:09:32PM +0200, Jorik Jonker wrote: >> On Fri, Sep 02, 2016 at 09:04:25AM +0200, Maxime Ripard wrote: >> >Unfortunately, these pins can be used for other purposes as

drivers/nvme/host/nvme.h:226:12: error: dereferencing pointer to incomplete type 'struct request'

tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git master head: c6935931c1894ff857616ff8549b61236a19148f commit: aa71987472a974f4f6dc4be377720564079ef42e nvme: fabrics drivers don't need the nvme-pci driver date: 2 weeks ago config: x86_64-randconfig-n0-09052021

  1   2   3   4   5   6   7   8   9   10   >