On Thu, Mar 21, 2019 at 09:26:38AM +0300, Dan Carpenter wrote:
> Colin King reported a bug in read_bbreg_hdl():
>
> memcpy(pcmd->rsp, (u8 *)&val, pcmd->rspsz);
>
> The problem is that "val" is uninitialized.
>
> This code is obviously not useful, but so far as I can tell
> "pcmd->cmdcode"
Hi all,
On 03/20/19 at 05:58am, Matthew Wilcox wrote:
> On Wed, Mar 20, 2019 at 02:36:58PM +0200, Mike Rapoport wrote:
> > There are more than a thousand -EEXIST in the kernel, I really doubt all of
> > them mean "File exists" ;-)
>
> And yet that's what the user will see if it's ever printed wit
On Wed, Mar 13, 2019 at 12:19:31PM +0800, Pingfan Liu wrote:
I tested it in Qemu test with 12G memory, and set crashkernel=6G@6G.
Without this PATCH, it successed to reserve memory just 4 times(total
10 times).
With this PATCH, it successed to reserve memory 15 times(total 15
times).
So I think i
--
Goedendag,
Wij zijn Simple Federal Credit Union die leningen verstrekt per
postadvertentie. Wij bieden verschillende soorten leningen of projecten
leningen (korte en lange termijn leningen, persoonlijke leningen,
leningen aan bedrijven, enz.) Met 3% rente. dus als u financiële
Colin King reported a bug in read_bbreg_hdl():
memcpy(pcmd->rsp, (u8 *)&val, pcmd->rspsz);
The problem is that "val" is uninitialized.
This code is obviously not useful, but so far as I can tell
"pcmd->cmdcode" is never GEN_CMD_CODE(_Read_BBREG) so it's not harmful
either. For now the e
On Thu, 21 Mar 2019 03:37:33 +0100,
Kailang wrote:
>
> Yes, you could use Reviewed-by.
OK, applied now. Thanks.
Takashi
>
> -Original Message-
> From: Jian-Hong Pan
> Sent: Wednesday, March 20, 2019 1:06 PM
> To: Takashi Iwai
> Cc: Kailang ; alsa-de...@alsa-project.org; Linux
> U
On Thu, Mar 21, 2019 at 7:08 AM NeilBrown wrote:
>
> On Wed, Mar 20 2019, syzbot wrote:
>
> > syzbot has bisected this bug to:
> >
> > commit dee160df820de41ff2f59a715643680822a0ab06
> > Author: NeilBrown
> > Date: Mon Nov 5 01:30:47 2018 +
> >
> > locks: use properly initialized file_
On Wed, Mar 20 2019, syzbot wrote:
> syzbot has bisected this bug to:
>
> commit dee160df820de41ff2f59a715643680822a0ab06
> Author: NeilBrown
> Date: Mon Nov 5 01:30:47 2018 +
>
> locks: use properly initialized file_lock when unlocking.
This commit did not make it to mainline.
It was
On Tue, Mar 19, 2019 at 4:02 PM Weiyi Lu wrote:
>
> Try to stop extending the clk_id or clk_names if there are
> more and more new BASIC clocks. To get its own clocks by the
> basic_clk_name of each power domain.
>
> Signed-off-by: Weiyi Lu
> ---
> drivers/soc/mediatek/mtk-scpsys.c | 27
On Tue, Mar 19, 2019 at 01:38:34PM -0500, Aditya Pakki wrote:
> uuid in add_switch is allocted via kmemdup which can fail. The patch
> logs the error in such a scenario.
>
> Signed-off-by: Aditya Pakki
> ---
> drivers/thunderbolt/icm.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/dr
On Tue, Mar 19, 2019 at 4:02 PM Weiyi Lu wrote:
>
> Both MT8183 & MT6765 have more control steps of bus protection
> than previous project. And there add more bus protection registers
> reside at infracfg & smi-common. Also add new APIs for multiple
> step bus protection control with more customiz
On Thu, 14 Mar 2019 at 21:28, Stephen Boyd wrote:
>
> Quoting Vaishali Thakkar (2019-03-14 04:25:16)
> > On Fri, 1 Mar 2019 at 03:02, Stephen Boyd wrote:
> > >
> > > Why can't we use the debugfs_create_u32 function? It would make things
> > > clearer if there was either a debugfs_create_le32() fu
On Tue, Mar 12, 2019 at 02:24:08AM +, Anson Huang wrote:
> Freescale MMDC (Multi Mode DDR Controller) driver is supported
> since i.MX6Q, but not yet documented, this patch adds binding
> doc for MMDC module driver.
>
> Signed-off-by: Anson Huang
Applied all, thanks.
On Thu, Mar 21, 2019 at 02:09:41AM +0530, Mukesh Ojha wrote:
>
> On 3/20/2019 9:59 PM, Mika Westerberg wrote:
> > On Wed, Mar 20, 2019 at 11:24:45AM -0500, Aditya Pakki wrote:
> > > In enumerate_services, ida_simple_get on failure can return an error and
> > > leaks memory during device_register f
On 03/21/2019 10:31 AM, Zi Yan wrote:
> On 20 Mar 2019, at 21:13, Anshuman Khandual wrote:
>
>> pfn_valid_within() calls pfn_valid() when CONFIG_HOLES_IN_ZONE making it
>> redundant for both definitions (w/wo CONFIG_MEMORY_HOTPLUG) of the helper
>> pfn_to_online_page() which either calls pfn_va
Hi, Wangyan:
On Wed, 2019-03-06 at 18:13 +0800, CK Hu wrote:
> Hi, Wangyan:
>
> On Mon, 2019-02-25 at 10:09 +0800, wangyan wang wrote:
> > From: chunhui dai
> >
> > We should not change the rate of parent for hdmi phy when
> > doing round_rate for this clock. The parent clock of hdmi
> > phy mu
syzbot has bisected this bug to:
commit dee160df820de41ff2f59a715643680822a0ab06
Author: NeilBrown
Date: Mon Nov 5 01:30:47 2018 +
locks: use properly initialized file_lock when unlocking.
bisection log: https://syzkaller.appspot.com/x/bisect.txt?x=13f39fd720
start commit: dee
On Wed, Mar 20, 2019 at 03:13:56PM -0600, Daniel Díaz wrote:
> From: Arnaldo Carvalho de Melo
>
> commit 7d7d1bf1d1dabe435ef50efb051724b8664749cb upstream.
>
> We can't access kernel files directly from tools/, so copy the required
> bits, and make sure that we detect when the original files, in
On 21. 03. 19, 4:59, hariprasadk wrote:
> fix warning reported by checkpatch tool
>
> Signed-off-by: hariprasadk
Please use your real name as per
Documentation/process/submitting-patches.rst.
> ---
> drivers/tty/serial/serial_core.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
>
On 20 Mar 2019, at 21:13, Anshuman Khandual wrote:
pfn_valid_within() calls pfn_valid() when CONFIG_HOLES_IN_ZONE making
it
redundant for both definitions (w/wo CONFIG_MEMORY_HOTPLUG) of the
helper
pfn_to_online_page() which either calls pfn_valid() or
pfn_valid_within().
pfn_valid_within() be
On Thu, Mar 21, 2019 at 12:27 PM Alex G wrote:
>
> On 3/20/19 4:44 PM, Linus Torvalds wrote:
> > On Wed, Mar 20, 2019 at 1:52 PM Bjorn Helgaas wrote:
> >>
> >> AFAICT, the consensus there was that it would be better to find some
> >> sort of platform solution instead of dealing with it in individ
Hi Shawn,
> -Original Message-
> From: Aisheng Dong
> Sent: 2019年3月15日 18:24
> To: Peng Fan ; robh...@kernel.org;
> mark.rutl...@arm.com; shawn...@kernel.org; s.ha...@pengutronix.de;
> ker...@pengutronix.de; feste...@gmail.com; dl-linux-imx
> ; Anson Huang ; Daniel Baluta
> ; devicet...@vg
Hi Shawn,
> -Original Message-
> From: Aisheng Dong
> Sent: 2019年3月15日 18:24
> To: Peng Fan ; robh...@kernel.org;
> mark.rutl...@arm.com; shawn...@kernel.org; s.ha...@pengutronix.de;
> ker...@pengutronix.de; feste...@gmail.com; dl-linux-imx
> ; Anson Huang ; Daniel Baluta
> ; devicet...@vg
When debugging with CONFIG_PAGE_OWNER, I noticed that the min_low_pfn
on arm64 is always zero and the page owner scanning has to start from zero.
We have to loop a while before we see the first valid pfn.
(see: read_page_owner())
Setup min_low_pfn to save some loops.
Before setting min_low_pfn:
pfn_valid_within() calls pfn_valid() when CONFIG_HOLES_IN_ZONE making it
redundant for both definitions (w/wo CONFIG_MEMORY_HOTPLUG) of the helper
pfn_to_online_page() which either calls pfn_valid() or pfn_valid_within().
pfn_valid_within() being 1 when !CONFIG_HOLES_IN_ZONE is irrelevant either
wa
at 01:18, Andy Shevchenko wrote:
On Wed, Mar 20, 2019 at 6:55 PM Kai-Heng Feng
wrote:
at 23:39, Hans de Goede wrote:
On 3/20/19 3:37 PM, Benjamin Tissoires wrote:
Benjamin, what I find interesting here is that the BOGUS_IRQ quirk
is also used on Elan devices, I suspect that these Elan de
MADV_DONTNEED is handled with mmap_sem taken in read mode.
We call page_mkclean without holding mmap_sem.
MADV_DONTNEED implies that pages in the region are unmapped and subsequent
access to the pages in that range is handled as a new page fault.
This implies that if we don't have parallel access
fix warning reported by checkpatch tool
Signed-off-by: hariprasadk
---
drivers/tty/serial/serial_core.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/tty/serial/serial_core.c b/drivers/tty/serial/serial_core.c
index 351843f..69f4871 100644
--- a/drivers/tty/serial/s
On Tue, Mar 19, 2019 at 12:04:01AM -0400, Kimberly Brown wrote:
There are two methods for signaling the host: the monitor page mechanism
and hypercalls. The monitor page mechanism is used by performance
critical channels (storage, networking, etc.) because it provides
improved throughput. However
hash_for_each_safe() and hash_for_each_possible_safe()
need to be passed a temp 'struct hlist_node' pointer, but
do not say that in the documentation - they just say
a 'struct'.
Also the documentation for hlist_for_each_entry_safe()
describes @n as "another" hlist_node, but in reality it is
the o
On Wed, Mar 20, 2019 at 01:06:19PM -0700, Stephen Hemminger wrote:
> On Sat, 16 Mar 2019 21:49:28 -0400
> Kimberly Brown wrote:
>
> > On Thu, Mar 14, 2019 at 03:45:33PM -0700, Stephen Hemminger wrote:
> > > On Thu, 14 Mar 2019 13:05:15 -0700
> > > "Kimberly Brown" wrote:
> > >
> > > > Fix a r
Thank you for the comment.
On Wed, 20 Mar 2019 12:05:25 -0700, Andrew Morton
wrote:
> On Wed, 20 Mar 2019 18:29:29 +0900 Masatake YAMATO wrote:
>
>> Finding endpoints of an IPC channel is one of essential task to
>> understand how a user program works. Procfs and netlink socket provide
>> enou
> (I previously wrote that this would be easier to test with the patch
> applied, because the package power is reported with the -Dump option,
> but I'm not sure that's actually the case - the value might still only
> be collected once per package?)
Right -- we'd have to move it to a per-core or p
On Mon, Mar 11, 2019 at 07:57:04PM +0530, Nishad Kamdar wrote:
> This patch corrects the SPDX License Identifier style
> in imx6ull-pinfunc-snvs.h.
>
> Changes made by using a script provided by Joe Perches here:
> https://lkml.org/lkml/2019/2/7/46
> and making some manual changes.
>
> Suggested-
Hi Tetsuo,
Thanks for implementing this, it's really helpful.
Tetsuo Handa writes:
...
> From 91f85d2bd494df2f73c605d8b4747e8cc0a61ae2 Mon Sep 17 00:00:00 2001
> From: Tetsuo Handa
> Date: Tue, 18 Dec 2018 05:53:04 +0900
> Subject: [PATCH] printk: Add caller information to printk() output.
>
>
On Mon, Mar 04, 2019 at 03:50:50PM +0800, Yuantian Tang wrote:
> Ls1088a has 2 thermal sensors, core cluster and SoC platform. Core cluster
> sensor is used to monitor the temperature of core and SoC platform is for
> platform. The current dts only support the first sensor.
> This patch adds the se
Yes, you could use Reviewed-by.
-Original Message-
From: Jian-Hong Pan
Sent: Wednesday, March 20, 2019 1:06 PM
To: Takashi Iwai
Cc: Kailang ; alsa-de...@alsa-project.org; Linux
Upstreaming Team ; Linux Kernel
Subject: Re: [PATCH v2] ALSA: hda/realtek: Enable headset MIC of Acer AIO w
When we use the gpio to control some peripheral devices,and try to
export the gpio first,then unexport the gpio, we test the signal with
oscilloscope,and find the signal can't meet the requirements,because
after we unexported the gpio,the gpio's register(tx and rx)value can't
be recovered,and this
From: YueHaibing
'err' is set in err path, but it's not returned to callers.
Don't always return -EINVAL, return err.
Fixes: cd8bfd8c973e ("perf tools: Add processing of coresight metadata")
Signed-off-by: YueHaibing
---
tools/perf/util/cs-etm.c | 10 +++---
1 file changed, 7 insertions(+)
From: YueHaibing
intlist__findnew() doesn't uses ERR_PTR() as a return mechanism
so its callers shouldn't try to extract the error using PTR_ERR(
ret) from intlist__findnew(), make cs_etm__process_auxtrace_info
return -ENOMEM instead.
Fixes: cd8bfd8c973e ("perf tools: Add processing of coresight
From: YueHaibing
v2:
- patch 1 fix commilt log
- patch 2 use correct Fixes tag
This patch series fixes two issue:
1. fix pass-zero-to-ERR_PTR warning
2. return correct errcode to upstream callers
YueHaibing (2):
perf cs-etm: Remove errnoeous ERR_PTR() usage in in
cs_etm__process_auxtrace_
+ Caesar Wang
On 2019/3/21 1:48, Alexander Kochetkov wrote:
I've found that sometimes dw_mmc in my rk3188 based board stop transfer
any data with error:
kernel: dwmmc_rockchip 1021c000.dwmmc: Unexpected command timeout, state 3
Further digging into problem showed that sometimes one of EDMA-bas
i.MX8QXP is an ARMv8 SoC which has a Cortex-M4 system controller
inside, the system controller is in charge of controlling power,
clock and watchdog etc..
This patch adds i.MX system controller watchdog driver support,
watchdog operation needs to be done in secure EL3 mode via
ARM-Trusted-Firmware
Enable CONFIG_IMX_SC_WDT as module to support i.MX system
controller watchdog.
Signed-off-by: Anson Huang
---
no changes.
---
arch/arm64/configs/defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/configs/defconfig b/arch/arm64/configs/defconfig
index f575401..b4000aa 100644
Add i.MX8QXP system controller watchdog support.
Signed-off-by: Anson Huang
---
Changes since V8:
- add timeout property.
---
arch/arm64/boot/dts/freescale/imx8qxp.dtsi | 5 +
1 file changed, 5 insertions(+)
diff --git a/arch/arm64/boot/dts/freescale/imx8qxp.dtsi
b/arch/arm64/boot/
i.MX8QXP is an ARMv8 Cortex-A35 SoC with a Cortex-M4 system controller
inside, the system controller manages overall power, clock, secure RTC
and watchdog etc., so Linux kernel running on A35 needs to communicate
with system controller for watchdog operation, this system controller
watchdog will ca
Add i.MX system controller watchdog binding doc.
Signed-off-by: Anson Huang
---
Changes since V8:
- add optional property "timeout-sec" according to driver change.
---
.../bindings/watchdog/fsl-imx-sc-wdt.txt | 24 ++
1 file changed, 24 insertions(+)
create
Fix a few spelling and grammar errors, and two places where fast/safe
in the documentation did not match the function.
Signed-off-by: Tom Levy
Cc: Andrew Morton
---
include/linux/lz4.h | 18 +-
1 file changed, 9 insertions(+), 9 deletions(-)
diff --git a/include/linux/lz4.h b/i
Hi all,
Changes since 20190320:
The amdgpu tree still had its build failure for which I reverted a commit.
The scsi tree still had its build failure for which I applied a patch.
Non-merge commits (relative to Linus' tree): 2187
1820 files changed, 61493 insertions(+), 30479 dele
On Wed, Mar 20, 2019 at 5:11 PM Rafael J. Wysocki wrote:
>
> On Wed, Mar 20, 2019 at 11:34 PM Furquan Shaikh wrote:
> >
> > Commit 18996f2db918 ("ACPICA: Events: Stop unconditionally
> > clearing ACPI IRQs during suspend/resume") was added to stop clearing
> > of event status bits unconditionally
From: Steven Rostedt (VMware)
He Zhe reported a crash by enabling trace events and selecting
"userstacktrace" which will read the stack of userspace for every trace
event recorded. Zhe narrowed it down to:
c3bc8fd637a9 ("tracing: Centralize preemptirq tracepoints and unify their
usage")
With
On Wed, 13 Mar 2019 14:13:31 -0700 Nick Desaulniers
wrote:
> A recent optimization in Clang (r355672) lowers comparisons of the
> return value of memcmp against zero to comparisons of the return value
> of bcmp against zero. This helps some platforms that implement bcmp
> more efficiently than
--
I need your quick reply for a business transaction of $7Million USD,
it is a genuine transaction and 100 percent risk free. You will have
40 percent share of the fund. please reply back to me urgently for the
full details if you are capable.
On Mon, Mar 11, 2019 at 10:26 PM Enrico Weigelt, metux IT consult
wrote:
>
> Formatting of Kconfig files doesn't look so pretty, so let the
> Great White Handkerchief come around and clean it up.
>
> Signed-off-by: Enrico Weigelt, metux IT consult
> ---
> net/Kconfig | 14 +--
>
On 3/20/19 8:53 PM, Jason Wang wrote:
>
> On 2019/3/19 上午10:22, Dongli Zhang wrote:
>> Hi Jason,
>>
>> On 3/18/19 3:47 PM, Jason Wang wrote:
>>> On 2019/3/15 下午8:41, Cornelia Huck wrote:
On Fri, 15 Mar 2019 12:50:11 +0800
Jason Wang wrote:
> Or something like I proposed seve
Hi Suzuki,
On Wed, Mar 20, 2019 at 01:52:58PM +, Suzuki K Poulose wrote:
>
>
> On 20/03/2019 12:38, Wanglai Shi wrote:
> > From: Leo Yan
> >
> > Since CoreSight hardware topology can use a 'hidden' funnel in the
> > trace data path, this kind funnel doesn't have register for accessing
> >
On 2019/3/21 0:16, Mathieu Poirier wrote:
> On Wed, 20 Mar 2019 at 00:37, Yue Haibing wrote:
>>
>> From: YueHaibing
>>
>> This patch series fixes two issue:
>> 1. fix pass-zero-to-ERR_PTR warning
>> 2. return correct errcode to upstream callers
>>
>> YueHaibing (2):
>> perf cs-etm: Remove errno
Preserves the bitfields of PMCR_EL0(AArch64) during PMU reset.
Reset routine should write a 1 to PMCR.C and PMCR.P fields only
to reset the counters. Other fields should not be changed
as they could be set before PMU initialization and their
value must be preserved even after reset.
Signed-off-by:
From: YueHaibing
Fix sparse warnings:
sound/soc/codecs/wm_adsp.c:309:20: warning: symbol 'wm_adsp1_ops' was not
declared. Should it be static?
sound/soc/codecs/wm_adsp.c:310:20: warning: symbol 'wm_adsp2_ops' was not
declared. Should it be static?
sound/soc/codecs/wm_adsp.c:311:20: warning: sy
On Mon, Mar 11, 2019 at 10:23 PM Enrico Weigelt, metux IT consult
wrote:
>
> Formatting of Kconfig files doesn't look so pretty, so let the
> Great White Handkerchief come around and clean it up.
>
> Signed-off-by: Enrico Weigelt, metux IT consult
> ---
> drivers/char/Kconfig | 24
On Mon, Mar 11, 2019 at 10:29 PM Enrico Weigelt, metux IT consult
wrote:
>
> Formatting of Kconfig files doesn't look so pretty, so let the
> Great White Handkerchief come around and clean it up.
>
> Signed-off-by: Enrico Weigelt, metux IT consult
> ---
> arch/arm/Kconfig | 24 +
subscribe linux-kernel
Pls ignore this, sorry.
On 2019/3/21 9:43, Yue Haibing wrote:
> From: YueHaibing
>
> Fix sparse warnings:
>
> sound/soc/codecs/wm_adsp.c:309:20: warning: symbol 'wm_adsp1_ops' was not
> declared. Should it be static?
> sound/soc/codecs/wm_adsp.c:310:20: warning: symbol 'wm_adsp2_ops' was not
From: YueHaibing
Fix sparse warnings:
sound/soc/codecs/wm_adsp.c:309:20: warning: symbol 'wm_adsp1_ops' was not
declared. Should it be static?
sound/soc/codecs/wm_adsp.c:310:20: warning: symbol 'wm_adsp2_ops' was not
declared. Should it be static?
sound/soc/codecs/wm_adsp.c:311:20: warning: sy
From e38df43127fd9a5db167f5873aee882b60f63f37 Mon Sep 17 00:00:00 2001
From: Alec Ari
Date: Wed, 20 Mar 2019 20:19:48 -0500
Subject: drm/Kconfig: Remove selection of BACKLIGHT_* options for
DRM_RADEON
Backlight support is not required for base DRM_RADEON
functionality. Tested on Acer Aspire On
Hi Andy,
On 19. 3. 19. 오후 11:30, Andy Shevchenko wrote:
> On Intel Merrifield platforms the Basin Cove PMIC responsible for USB DR
> detection among other things.
>
> Here is the extcon driver to support USB DR and charger detection.
>
> Since v2:
> - rebase on top of extcon-next
> - update copy
On Wed, Mar 20, 2019 at 03:29:17PM -0700, Josh Hunt wrote:
>
> Herbert
>
> We're seeing this pretty regularly on 4.14 LTS kernels. I didn't see your
> change in any of the regular trees. Are there plans to submit this? If so,
> can it get queued up for 4.14 stable too?
Hi Josh:
Thanks for remind
(Whoops, resending this message. Forgot that Gmail defaulted to
HTML...)
On Wed, 2019-03-20 at 19:36 -0400, Len Brown wrote:
> Hi Calvin,
> I'm inclined to apply this -- because it will not break anything,
> and it would at least enable testing by people, who have this
> hardware.
Hi Len,
By all
The following error was thrown when compiling `tools/perf` using OpenCSD
v0.11.1. This patch fixes said error.
```
CC util/intel-pt-decoder/intel-pt-log.o
CC util/cs-etm-decoder/cs-etm-decoder.o
util/cs-etm-decoder/cs-etm-decoder.c: In function
‘cs_etm_decoder__buffer_range’:
util/c
On 3/20/19 4:44 PM, Linus Torvalds wrote:
On Wed, Mar 20, 2019 at 1:52 PM Bjorn Helgaas wrote:
AFAICT, the consensus there was that it would be better to find some
sort of platform solution instead of dealing with it in individual
drivers. The PCI core isn't really a driver, but I think the s
On Tue, Mar 19, 2019 at 1:03 PM Masahiro Yamada
wrote:
>
> Commit 2b50f7ab6368 ("kbuild: add workaround for Debian make-kpkg")
> annoyed people who want to wrap the top Makefile with GNUmakefile
> or something in order to customize it for their use.
>
> On second thought, we do not need to run the
> -Original Message-
> From: Shawn Guo
> Sent: 2019年3月20日 22:49
> To: Andy Tang
> Cc: Daniel Lezcano ; mark.rutl...@arm.com;
> devicet...@vger.kernel.org; linux...@vger.kernel.org;
> linux-kernel@vger.kernel.org; Leo Li ;
> edubez...@gmail.com; robh...@kernel.org; rui.zh...@intel.com;
>
Dear Friend,
I am Mrs Clara David. am sending you this brief letter to solicit your
partnership to transfer $18.5 million US Dollars.I shall send you more
information and procedures when I receive positive response from you.
please send me a message in my Email box (mrsclarad...@gmail.com)
as i wa
i.MX7ULP has TPM(Low Power Timer/Pulse Width Modulation Module)
inside, it can support multiple PWM channels, all the channels
share same counter and period setting, but each channel can
configure its duty and polarity independently.
There are several TPM modules in i.MX7ULP, the number of channel
Add i.MX7ULP EVK board PWM0 support.
Signed-off-by: Anson Huang
---
no changes.
---
arch/arm/boot/dts/imx7ulp.dtsi | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/imx7ulp.dtsi b/arch/arm/boot/dts/imx7ulp.dtsi
index eb349fd..15d04fb 100644
--- a/arch/arm/boot/dts
This patch adds i.MX7ULP EVK board MIPI-DSI backlight support.
Signed-off-by: Anson Huang
---
no changes.
---
arch/arm/boot/dts/imx7ulp-evk.dts | 21 +
1 file changed, 21 insertions(+)
diff --git a/arch/arm/boot/dts/imx7ulp-evk.dts
b/arch/arm/boot/dts/imx7ulp-evk.dts
index
Select CONFIG_PWM_IMX_TPM by default to support i.MX7ULP
TPM PWM.
Signed-off-by: Anson Huang
---
no changes.
---
arch/arm/configs/imx_v6_v7_defconfig | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm/configs/imx_v6_v7_defconfig
b/arch/arm/configs/imx_v6_v7_defconfig
index 5586a50..57
Add i.MX TPM(Low Power Timer/Pulse Width Modulation Module) PWM binding.
Signed-off-by: Anson Huang
---
no changes.
---
.../devicetree/bindings/pwm/imx-tpm-pwm.txt| 22 ++
1 file changed, 22 insertions(+)
create mode 100644 Documentation/devicetree/bindings/pwm/imx-t
i.MX7ULP EVK board has MIPI-DSI display, its backlight is supplied by
TPM PWM module, this patch set enables i.MX7ULP TPM PWM driver support
and also add backlight support for MIPI-DSI display.
Changes since V7:
- ONLY change the pwm driver patch.
Anson Huang (5):
dt-bindings: pwm: Add
On 3/20/2019 10:39 AM, Greg KH wrote:
On Tue, Jan 15, 2019 at 02:41:17PM -0800, James Smart wrote:
On 1/14/2019 5:15 PM, Kees Cook wrote:
On Sat, Jan 12, 2019 at 7:29 AM Willy Tarreau wrote:
From: Silvio Cesare
Change snprintf to scnprintf. There are generally two cases where using
snprintf
wow. Commit 70b62c25665f636c9f6c700b26af7df296b0887e
from last Sept. 14, 2018, total commit description says:
LoadPin: Initialize as ordered LSM
This converts LoadPin from being a direct "minor" LSM into an ordered LSM.
Nowhere does it say anything like "this also deletes any notion
Hi, Guenter
Best Regards!
Anson Huang
> -Original Message-
> From: Guenter Roeck [mailto:groe...@gmail.com] On Behalf Of Guenter
> Roeck
> Sent: 2019年3月21日 8:32
> To: Anson Huang
> Cc: w...@linux-watchdog.org; robh...@kernel.org; mark.rutl...@arm.com;
> shawn...@kernel.org; s.ha...@pengu
Recently I added an RCU annotation check to rcu_assign_pointer(). All
pointers assigned to RCU protected data are to be annotated with __rcu
inorder to be able to use rcu_assign_pointer() similar to checks in
other RCU APIs.
This resulted in a sparse error: kernel//sched/cpufreq.c:41:9: sparse:
er
This fixes the following sparse errors in sched/fair.c:
fair.c:6506:14: error: incompatible types in comparison expression
fair.c:8642:21: error: incompatible types in comparison expression
Using __rcu will also help sparse catch any future bugs.
[From an RCU perspective]
Reviewed-by: Paul E. Mc
This suppresses sparse error generated due to the recently added
rcu_assign_pointer sparse check.
percpu-rwsem.c:162:9: sparse: error: incompatible types in comparison expression
exit.c:316:16: sparse: error: incompatible types in comparison expression
[From an RCU perspective]
Reviewed-by: Paul
The scheduler uses RCU API in various places to access sched_domain
pointers. These cause sparse errors as below.
Many new errors show up because of an annotation check I added to
rcu_assign_pointer(). Let us annotate the pointers correctly which also
will help sparse catch any potential future bu
This is just a resend with scheduler patches split from the driver fixes and
Paul's Reviewed-by(s) added.
These patches fix various sparse errors ccaused as a result of the recent check
to add rcu_check_sparse() to rcu_assign_pointer(). The errors are due to
missing annotations. The annotations a
On 3/20/19 5:22 PM, Anson Huang wrote:
Hi, Guenter
Best Regards!
Anson Huang
-Original Message-
From: Guenter Roeck [mailto:groe...@gmail.com] On Behalf Of Guenter
Roeck
Sent: 2019年3月20日 21:44
To: Anson Huang
Cc: w...@linux-watchdog.org; robh...@kernel.org; mark.rutl...@arm.com;
shawn
Hi, Guenter
Best Regards!
Anson Huang
> -Original Message-
> From: Guenter Roeck [mailto:groe...@gmail.com] On Behalf Of Guenter
> Roeck
> Sent: 2019年3月20日 21:44
> To: Anson Huang
> Cc: w...@linux-watchdog.org; robh...@kernel.org; mark.rutl...@arm.com;
> shawn...@kernel.org; s.ha...@peng
> On Wed, Mar 20, 2019 at 12:57:52PM -0700, Xing, Cedric wrote:
> > > Using the untrusted stack as a way to exchange data is very
> > > convenient, but that doesn't mean it's a good idea. Here are some
> > > problems it
> > > causes:
> > >
> > > - It prevents using a normal function to wrap encla
On 3/20/19 7:12 PM, Guenter Roeck wrote:
> On 3/20/19 11:16 AM, Gustavo A. R. Silva wrote:
>> In preparation to enabling -Wimplicit-fallthrough, mark switch
>> cases where we are expecting to fall through.
>>
>> This patch fixes the following warning:
>>
>> drivers/watchdog/alim7101_wdt.c: In fu
This patch adds a binding that describes the HDMI controller for
rk3066.
Signed-off-by: Johan Jonker
Reviewed-by: Rob Herring
---
.../display/rockchip/rockchip,rk3066-hdmi.txt | 72 ++
1 file changed, 72 insertions(+)
create mode 100644
Documentation/devicetree/bindin
On 3/20/19 11:16 AM, Gustavo A. R. Silva wrote:
In preparation to enabling -Wimplicit-fallthrough, mark switch
cases where we are expecting to fall through.
This patch fixes the following warning:
drivers/watchdog/alim7101_wdt.c: In function ‘fop_ioctl’:
drivers/watchdog/alim7101_wdt.c:279:3: w
On Wed, Mar 20, 2019 at 4:49 PM Christoph Hellwig wrote:
>
> On Wed, Mar 20, 2019 at 10:39:52PM +, Alistair Francis wrote:
> > According to the FU540 and E31 manuals the PLIC source priority
> > address starts at an offset of 0x04 and not 0x00. To aviod confusion
> > update the address and sou
dev is indirectly controlled by user-space, hence leading to
a potential exploitation of the Spectre variant 1 vulnerability.
This issue was detected with the help of Smatch:
sound/core/seq/oss/seq_oss_synth.c:626 snd_seq_oss_synth_make_info() warn:
potential spectre issue 'dp->synths' [w] (loca
From: Rafael J. Wysocki
The current handling of MSR_IA32_ENERGY_PERF_BIAS in the kernel is
problematic, because it may cause changes made by user space to that
MSR (with the help of the x86_energy_perf_policy tool, for example)
to be lost every time a CPU goes offline and then back online as well
Currently, there are no topology defined for RISC-V.
Parse the cpu-map node from device tree and setup the
cpu topology.
CPU topology after applying the patch.
$cat /sys/devices/system/cpu/cpu2/topology/core_siblings_list
0-3
$cat /sys/devices/system/cpu/cpu3/topology/core_siblings_list
0-3
$cat /
cpu-map binding can be used to described cpu topology for both
RISC-V & ARM. It makes more sense to move the binding to document
to a common place.
The relevant discussion can be found here.
https://lkml.org/lkml/2018/11/6/19
Signed-off-by: Atish Patra
Reviewed-by: Sudeep Holla
---
.../topolog
From: Sudeep Holla
The current ARM DT topology description provides the operating system
with a topological view of the system that is based on leaf nodes
representing either cores or threads (in an SMT system) and a
hierarchical set of cluster nodes that creates a hierarchical topology
view of h
On Wed, Mar 20, 2019 at 10:39:52PM +, Alistair Francis wrote:
> According to the FU540 and E31 manuals the PLIC source priority
> address starts at an offset of 0x04 and not 0x00. To aviod confusion
> update the address and source offset to match the documentation. This
> causes no difference i
1 - 100 of 769 matches
Mail list logo
