Hi Florian,
On Tue, 2019-01-22 at 16:33 -0800, Florian Fainelli wrote:
> On 32-bit architectures defining resource_size_t as 64-bit (because of
> PAE), we can run into a linker failure because of the modulo and the
> division against resource_size(), replace the two problematic operations
> with
On Wed, 23 Jan 2019 at 09:56, Julien Thierry wrote:
>
>
>
> On 22/01/2019 20:18, Ard Biesheuvel wrote:
> > On Mon, 21 Jan 2019 at 16:36, Julien Thierry wrote:
> >>
> >> CPU does not received signals for interrupts with a priority masked by
> >> ICC_PMR_EL1. This means the CPU might not come back
On Tue, Nov 6, 2018 at 3:03 PM Kirill Tkhai wrote:
>
> Hi, Miklos,
>
> this is not a well-tested patch, this is a concept,
> showing the places, where it looks we have a problem.
>
> Commit 7879c4e58b7c made io->async careless about inode size,
> and this is wrong. Asyncronuos background requests
On Wed, 23 Jan 2019 at 09:50, Vincent Guittot
wrote:
>
> On Wed, 23 Jan 2019 at 09:14, Ulf Hansson wrote:
> >
> > On Tue, 22 Jan 2019 at 15:24, Vincent Guittot
> > wrote:
> > >
> > > Initializing accounting_timestamp to something different from 0 during
> > > pm_runtime_init() doesn't make
On Tue, 22 Jan 2019, Greg Kroah-Hartman wrote:
> When calling debugfs functions, there is no need to ever check the
> return value. The function can work or not, but the code logic should
> never do something different based on this.
>
> Cc: Martin Schwidefsky
> Cc: Heiko Carstens
> Cc:
On Tue, Jan 22, 2019 at 05:33:37PM +0100, Greg Kroah-Hartman wrote:
> On Tue, Jan 22, 2019 at 05:24:54PM +0100, Heiko Carstens wrote:
> > On Tue, Jan 22, 2019 at 04:21:02PM +0100, Greg Kroah-Hartman wrote:
> > > When calling debugfs functions, there is no need to ever check the
> > > return value.
On Tue, Jan 22, 2019 at 10:49:08PM -0500, Waiman Long wrote:
> Four queue nodes per cpu are allocated to enable up to 4 nesting levels
> using the per-cpu nodes. Nested NMIs are possible in some architectures.
> Still it is very unlikely that we will ever hit more than 4 nested
> levels with
Hi Joel,
On Tue, 2019-01-22 at 16:53 -0500, Joel Fernandes wrote:
> Could you CC me on the other patches as well, next time? I am quite
> interested and recently have worked on the latency tracer.
>
Sure, I will.
>
> > +MODULE_PARM_DESC(burst_size, "The size of a burst (default 1)");
>
>
In case DOC_CHIPID_G3, mtd->name is not freed in err handling path,
which is alloced by kasprintf(). Fix this by using devm_kasprintf().
Fixes: ae9d4934b2d7 ("mtd: docg3: add multiple floor support")
Signed-off-by: YueHaibing
---
v3: use devm_kasprintf
---
drivers/mtd/devices/docg3.c | 4 ++--
On Tuesday 22 Jan 2019 at 19:41:36 (+0100), Greg KH wrote:
> On Tue, Jan 22, 2019 at 04:42:47PM +, Quentin Perret wrote:
> > The recently introduced Energy Model (EM) framework manages power cost
> > tables of CPUs. These tables are currently only visible from kernel
> > space. However, in
Hi,
(Not sure I am sending the right place)
Documentation/process/changes.rst says the minimal version for binutils
is 2.20. I am trying the binutils-2.20.51.0.2-5.48.el6.x86_64.rpm of
Centos6 on Fedora28, and it give me:
HOSTCC scripts/basic/fixdep
/usr/bin/ld: unrecognized option '-plugin'
We want to work for you to edit your photos.
We can do your photos with white background, sharpen, retouching is
included for all your photos.
Waiting for the test photos to start with.
Thanks,
Judy
On Tue, Jan 22, 2019 at 10:14:00PM +0100, Thomas Gleixner wrote:
> On Mon, 21 Jan 2019, Thomas Gleixner wrote:
> > On Mon, 21 Jan 2019, Heiko Carstens wrote:
> >
> > > Hi Thomas,
> > >
> > > [full quote below]
> > >
> > > Did you have any time to look into this yet? :)
> > >
> > > The warning
On Tue, Jan 22, 2019 at 10:49:09PM -0500, Waiman Long wrote:
> Track the number of slowpath locking operations that are being done
> without any MCS node available as well renaming lock_index[123] to make
> them more descriptive.
>
> Using these stat counters is one way to find out if a code path
On 22/01/2019 15:08, Greg Kroah-Hartman wrote:
When calling debugfs code, there is no need to ever check the return
value of the call, as no logic should ever change if a call works
properly or not. Fix up a bunch of x86-specific code to not care about
the results of debugfs.
Greg
On Wed, Jan 23, 2019 at 09:10:18AM +, Will Deacon wrote:
> On Tue, Jan 22, 2019 at 04:21:43PM +0100, Greg Kroah-Hartman wrote:
> > When calling debugfs functions, there is no need to ever check the
> > return value. The function can work or not, but the code logic should
> > never do
On Tue, Jan 22, 2019 at 03:41:29PM +, Patrick Bellasi wrote:
> On 22-Jan 16:13, Peter Zijlstra wrote:
> > On Tue, Jan 22, 2019 at 02:43:29PM +, Patrick Bellasi wrote:
> > > Do you think that could be acceptable?
> >
> > Think so, it's a sysctl poke, 'nobody' ever does that.
>
> Cool,
On Tue, Jan 22, 2019 at 11:56:33AM -0800, Sowjanya Komatineni wrote:
> This patch adds HW Command Queue for supported Tegra SDMMC
> controllers.
>
> Signed-off-by: Sowjanya Komatineni
> ---
> [V10]: Changes are same as V9 except this series has SDHCI core changes
> into seperate patch
>
On Tue, Jan 22, 2019 at 03:33:15PM +, Patrick Bellasi wrote:
> On 22-Jan 15:57, Peter Zijlstra wrote:
> > On Tue, Jan 22, 2019 at 02:01:15PM +, Patrick Bellasi wrote:
> > > Yes, I would say we have two options:
> > >
> > > 1) SCHED_FLAG_KEEP_POLICY enforces all the scheduling class
On Tue, Jan 22, 2019 at 11:56:32AM -0800, Sowjanya Komatineni wrote:
> Below are the supported DMA types in Host Control1 Register
> with Version 4 enable
> b'00 - SDMA
> b'01 - Not Used
> b'10 - ADMA2
> b'11 - ADMA2 or ADMA3
>
> ADMA3 uses Command Descriptor to issue an SD command.
> A
On Tue, Jan 22, 2019 at 11:56:30AM -0800, Sowjanya Komatineni wrote:
> Add supports-cqe optional property for MMC hosts.
>
> This property is used to identify the specific host controller
> supporting command queue.
>
> Signed-off-by: Sowjanya Komatineni
> ---
> [V10]: This patch version moves
On 23-Jan-19 2:15 PM, Boris Brezillon wrote:
> On Tue, 22 Jan 2019 12:11:37 +0530
> Vignesh R wrote:
>
>> Cadence OSPI controller IP supports Octal IO (x8 IO lines),
>> It also has an integrated PHY. IP register layout is very
>> similar to existing QSPI IP except for additional bits to
On Wed, 23 Jan 2019 14:58:27 +0800
YueHaibing wrote:
> Fix a static code checker warning:
> drivers/mtd/devices/docg3.c:1875
> doc_probe_device() warn: passing zero to 'ERR_PTR'
>
> Fixes: ae9d4934b2d7 ("mtd: docg3: add multiple floor support")
> Signed-off-by: YueHaibing
> ---
>
On Tue, Jan 22, 2019 at 04:21:43PM +0100, Greg Kroah-Hartman wrote:
> When calling debugfs functions, there is no need to ever check the
> return value. The function can work or not, but the code logic should
> never do something different based on this.
>
> Cc: Peter Zijlstra
> Cc: Ingo Molnar
Pls ignore this err patch.
On 2019/1/23 17:07, YueHaibing wrote:
> In case DOC_CHIPID_G3, mtd->name is not freed in err handling path,
> which is alloced by kasprintf(). Fix this by using devm_kasprintf().
>
> Fixes: ae9d4934b2d7 ("mtd: docg3: add multiple floor support")
> Signed-off-by:
On Wed, 23 Jan 2019 at 08:15, Christoph Hellwig wrote:
>
> On Tue, Jan 22, 2019 at 10:07:07PM +0100, Ard Biesheuvel wrote:
> > Yes, so much was clear. And the reason this breaks on some arm64
> > systems is because
> > a) non-snooped PCIe TLP attributes may be ignored, and
> > b) non-x86 CPUs do
In case DOC_CHIPID_G3, mtd->name is not freed in err handling path,
which is alloced by kasprintf(). Fix this by using devm_kasprintf().
Fixes: ae9d4934b2d7 ("mtd: docg3: add multiple floor support")
Signed-off-by: YueHaibing
---
v2: use devm_kasprintf
---
drivers/mtd/devices/docg3.c | 4 ++--
On 21/01/2019 13:43, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.14.95 release.
> There are 59 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
On 21/01/2019 13:43, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 4.9.152 release.
> There are 51 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Responses
There is no need to have the 'post1' variable static since
new value always be assigned before use it.
Signed-off-by: YueHaibing
---
drivers/watchdog/pika_wdt.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/watchdog/pika_wdt.c b/drivers/watchdog/pika_wdt.c
index
On 21/01/2019 15:42, Ard Biesheuvel wrote:
> On Mon, 21 Jan 2019 at 16:34, Julien Thierry wrote:
>>
>> Currently, irqflags are saved before calling runtime services and
>> checked for mismatch on return.
>>
>> Provide a pair of overridable macros to save and restore (if needed) the
>> state
Ping?
On 2019/1/17 16:21, zhengbin wrote:
> If we change the file mtime to 1969, mksquashfs and mount,
> the atime/mtime of this file will be underflow. The reason is
> treating timestamps with the high bit set as positive
> times(before 1970), which should be set as negative times
> just like on
1. In current implementation, every VLPI will temporarily be mapped to
the first CPU in system (normally CPU0) and then moved to the real
scheduled CPU later.
2. So there is a time window and a VLPI may be sent to CPU0 instead of
the real scheduled vCPU, in a multi-CPU virtual machine.
3.
On 01/18/2019 01:58 PM, Jiri Olsa wrote:
> Lance reported an issue with bpftool not being able to
> dump program if there are more programs loaded and you
> want to dump any but the first program, like:
>
> # bpftool prog
> 28: kprobe name trace_req_start tag 1dfc28ba8b3dd597 gpl
>
On 22/01/2019 20:18, Ard Biesheuvel wrote:
> On Mon, 21 Jan 2019 at 16:36, Julien Thierry wrote:
>>
>> CPU does not received signals for interrupts with a priority masked by
>> ICC_PMR_EL1. This means the CPU might not come back from a WFI
>> instruction.
>>
>> Make sure ICC_PMR_EL1 does not
Christophe Leroy's on January 23, 2019 12:11 am:
> Looks like book3s/32 doesn't set RI on machine check, so
> checking RI before calling die() will always be fatal
> allthought this is not an issue in most cases.
Oh good catch, this is a fix for powerpc/64 as well. I think actually
the panic was
On 1/23/19 2:28 AM, Wolfram Sang wrote:
> On Tue, Jan 22, 2019 at 06:37:41PM -0600, Gustavo A. R. Silva wrote:
>> Fix inconsistent IS_ERR and PTR_ERR in i2c_imx_dma_request.
>>
>> The proper pointer to be passed as argument is dma->chan_tx.
>>
>> This bug was detected with the help of
Hello Stephen,
I am sorry for the trouble. My editor is configured to automatically wrap lines
when they are too long, I'll be more careful next time.
Do you need me to do anything about this patch?
Thanks,
Fab
> From: Stephen Rothwell
> Sent: 22 January 2019 20:56
> To: Simon Horman
>
On 2019/1/23 16:46, Boris Brezillon wrote:
> On Wed, 23 Jan 2019 14:59:43 +0800
> YueHaibing wrote:
>
>> In case DOC_CHIPID_G3, mtd->name should be freed in the
>> err handling path, which is alloced by kasprintf.
>>
>> Fixes: ae9d4934b2d7 ("mtd: docg3: add multiple floor support")
>>
On 22/01/2019 15:35, Greg Kroah-Hartman wrote:
> When calling debugfs functions, there is no need to ever check the
> return value. The function can work or not, but the code logic should
> never do something different based on this.
>
> Cc: Boris Ostrovsky
> Cc: Juergen Gross
> Cc: Stefano
On Tue, 22 Jan 2019 at 17:24, Kalle Valo wrote:
>
> Ulf Hansson wrote:
>
> > During "wlan-up", we are programming the FW into the WiFi-chip. However,
> > re-programming the FW doesn't work, unless a power cycle of the WiFi-chip
> > is made in-between the programmings.
> >
> > To conform to this
On Tue, Jan 22, 2019 at 04:21:34PM +0100, Greg Kroah-Hartman wrote:
> When calling debugfs functions, there is no need to ever check the
> return value. The function can work or not, but the code logic should
> never do something different based on this.
>
> Cc: Stanislaw Gruszka
> Cc: Helmut
On Tue, Jan 22, 2019 at 04:21:18PM +0100, Greg Kroah-Hartman wrote:
> When calling debugfs functions, there is no need to ever check the
> return value. The function can work or not, but the code logic should
> never do something different based on this.
>
> Cc: Stanislaw Gruszka
> Cc: Kalle
On Tue, 22 Jan 2019 at 17:08, Jan Kiszka wrote:
>
> On 21.01.19 15:40, Ulf Hansson wrote:
> > On Fri, 18 Jan 2019 at 16:09, Ulf Hansson wrote:
> >>
> >> On Fri, 18 Jan 2019 at 13:09, Jan Kiszka wrote:
> >>>
> >>> On 17.01.19 10:54, Ulf Hansson wrote:
> On Wed, 16 Jan 2019 at 21:26, Jan
There is no need to have the 'gpio_unbanked' variable static since
new value always be assigned before use it.
Signed-off-by: YueHaibing
---
drivers/gpio/gpio-davinci.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpio/gpio-davinci.c
On Wed, 23 Jan 2019 at 09:14, Ulf Hansson wrote:
>
> On Tue, 22 Jan 2019 at 15:24, Vincent Guittot
> wrote:
> >
> > Initializing accounting_timestamp to something different from 0 during
> > pm_runtime_init() doesn't make sense and put useless ordering constraint
> > between
> >
Ben Finney writes:
> Domenico Andreoli writes:
>
> > the situation of dwarves-dfsg improved a lot over the weekend
>
> That's good to hear. What is the event you're referring to? Can you give
> a URL to something that describes this change?
Upstream (in CC) reacted to my request of
There is no need to have the 'new_mems' variable static since new
value always be assigned before use it.
Signed-off-by: YueHaibing
---
kernel/cgroup/cpuset.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/kernel/cgroup/cpuset.c b/kernel/cgroup/cpuset.c
index
On Wed, 23 Jan 2019 14:59:43 +0800
YueHaibing wrote:
> In case DOC_CHIPID_G3, mtd->name should be freed in the
> err handling path, which is alloced by kasprintf.
>
> Fixes: ae9d4934b2d7 ("mtd: docg3: add multiple floor support")
> Signed-off-by: YueHaibing
> ---
> drivers/mtd/devices/docg3.c
On Tue, 22 Jan 2019 12:11:37 +0530
Vignesh R wrote:
> Cadence OSPI controller IP supports Octal IO (x8 IO lines),
> It also has an integrated PHY. IP register layout is very
> similar to existing QSPI IP except for additional bits to support Octal
> and Octal DDR mode. Therefore, extend current
On Tue, Jan 22, 2019 at 06:13:11AM -0800, Ronald Tschalär wrote:
> commit d6abe6df706c66d803e6dd4fe98c1b6b7f125a56 (drm/bridge:
> sil_sii8620: do not have a dependency of RC_CORE) added a dependency on
> INPUT. However, this causes problems with other drivers, in particular
> an input driver that
There is no need to have the 'sgpio' variable static since new
value always be assigned before use it.
Signed-off-by: YueHaibing
---
drivers/pinctrl/sirf/pinctrl-sirf.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/pinctrl/sirf/pinctrl-sirf.c
On Fri, 18 Jan 2019 13:44:25 +0900
Masami Hiramatsu wrote:
> Since commit 533059281ee5 ("tracing: probeevent: Introduce new
> argument fetching code") dropped the $comm support from uprobe
> events, this re-enables it.
>
> For $comm support, uses strlcpy() instead of strncpy_from_user()
> to
On 1/23/19 2:33 AM, Jiri Olsa wrote:
> On Tue, Jan 22, 2019 at 05:34:39PM -0600, Gustavo A. R. Silva wrote:
>> Notice that the use of the bitwise OR operator '|' always leads to
>> true in this particular case, which seems a bit suspicious due to
>> the context in which this expression is being
There is no need to have the 'dummy_mask' variable static since new
value always be assigned before use it.
Signed-off-by: YueHaibing
---
drivers/usb/host/ehci-ps3.c | 2 +-
drivers/usb/host/ohci-ps3.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
diff --git
Hi Jiaxun,
On Wed, 23 Jan 2019 06:23:36 +,
Jiaxun Yang wrote:
>
> This controller appeared on Loongson-1 family MCUs
> including Loongson-1B and Loongson-1C.
>
> Signed-off-by: Jiaxun Yang
> ---
> drivers/irqchip/Kconfig| 9 ++
> drivers/irqchip/Makefile | 1 +
>
On Tue, Jan 22, 2019 at 05:34:39PM -0600, Gustavo A. R. Silva wrote:
> Notice that the use of the bitwise OR operator '|' always leads to
> true in this particular case, which seems a bit suspicious due to
> the context in which this expression is being used.
>
> Fix this by using bitwise AND
On 23.01.2019 00:11, Paolo Bonzini wrote:
> On 22/01/19 21:48, Greg Kroah-Hartman wrote:
>>> This also brings the question: shall we move these counters out of debugfs
>>> into something else?
>> If you have code that relies on debugfs, yes, you need to move that out
>> of debugfs because more
On Tue, Jan 22, 2019 at 06:37:41PM -0600, Gustavo A. R. Silva wrote:
> Fix inconsistent IS_ERR and PTR_ERR in i2c_imx_dma_request.
>
> The proper pointer to be passed as argument is dma->chan_tx.
>
> This bug was detected with the help of Coccinelle.
>
> Fixes: 5b3a23a3cc94 ("i2c: imx: notify
Hi All
On 2019-01-22 10:36, Geert Uytterhoeven wrote:
> On Mon, Jan 14, 2019 at 4:36 PM Jon Hunter wrote:
>> I have noticed that system suspend has started failing consistently on a
>> couple Tegra boards over the last few days with the linux-next branch.
>> The following error is seen on on
Masahiro Yamada's on January 15, 2019 7:01 pm:
> Hi Nicholas,
>
>
> On Tue, Jan 15, 2019 at 5:07 PM Nicholas Piggin wrote:
>>
>> Masahiro Yamada's on January 14, 2019 1:27 pm:
>> > The symbol table in the final archive is unneeded because it is passed
>> > to the linker after the
On 1/16/19 10:43 AM, Vincent Guittot wrote:
[...]
+static inline u64 rq_clock_pelt(struct rq *rq)
+{
Doesn't this function need
lockdep_assert_held(>lock);
assert_clock_updated(rq);
like rq_clock() and rq_clock_task()? Later to support commit
cb42c9a3ebbb "sched/core: Add debugging
Frederic Weisbecker's on January 17, 2019 3:54 am:
> On Mon, Jan 14, 2019 at 04:47:45PM +1000, Nicholas Piggin wrote:
>> We have a supercomputer site testing nohz_full to reduce jitter with
>> good results, but they want CPU0 to be nohz_full. That happens to be
>> the boot CPU, which is disallowed
On Wed, 23 Jan 2019 at 08:59, Greg Kroah-Hartman
wrote:
>
> On Wed, Jan 23, 2019 at 08:44:36AM +0100, Ulf Hansson wrote:
> > On Tue, 22 Jan 2019 at 16:23, Greg Kroah-Hartman
> > wrote:
> > >
> > > When calling debugfs functions, there is no need to ever check the
> > > return value. The
Hi Alex,
On Wed, Jan 23, 2019 at 5:30 AM Alex Williamson
wrote:
> The below patch comes about from the build regressions and improvements
> list you've sent out, but something doesn't add up that we'd be testing
> with an old compiler where initialization with { 0 } generates a
> "missing braces
On Tue, Jan 22, 2019 at 04:21:43PM +0100, Greg Kroah-Hartman wrote:
> When calling debugfs functions, there is no need to ever check the
> return value. The function can work or not, but the code logic should
> never do something different based on this.
So I've seen you do a fair number of
On Tue, 22 Jan 2019 at 15:24, Vincent Guittot
wrote:
>
> Initializing accounting_timestamp to something different from 0 during
> pm_runtime_init() doesn't make sense and put useless ordering constraint
> between
> timekeeping_init() and pm_runtime_init().
> PM runtime should start accounting
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
This patch fixes the following warnings:
kernel/time/hrtimer.c: In function ‘hrtimer_fixup_activate’:
./include/linux/compiler.h:77:22: warning: this statement may fall through
On Tue, 22 Jan 2019 at 16:26, Kamil Konieczny
wrote:
>
> Add AES crypto HW acceleration for Exynos5433, with the help of SlimSSS IP.
>
> Signed-off-by: Kamil Konieczny
> ---
> drivers/crypto/s5p-sss.c | 50
> 1 file changed, 46 insertions(+), 4
On 01/23/2019 06:27 AM, Tomasz Figa wrote:
> On Tue, Jan 22, 2019 at 11:47 PM Hans Verkuil wrote:
>>
>> On 01/22/19 11:02, Tomasz Figa wrote:
>>> On Mon, Nov 12, 2018 at 8:37 PM Hans Verkuil wrote:
Hi Tomasz,
A general note for the stateful and stateless patches: they
On Wed, 23 Jan 2019 07:54:22 +0100
Greg Kroah-Hartman wrote:
> On Wed, Jan 23, 2019 at 11:15:16AM +0900, Masami Hiramatsu wrote:
> > On Tue, 22 Jan 2019 16:21:46 +0100
> > Greg Kroah-Hartman wrote:
> >
> > > When calling debugfs functions, there is no need to ever check the
> > > return value.
On 1/23/19 2:03 AM, Sudarsana Reddy Kalluru wrote:
> -Original Message-
> From: Gustavo A. R. Silva [mailto:gust...@embeddedor.com]
> Sent: 23 January 2019 13:23
> To: Rasesh Mody ; Sudarsana Kalluru
> ; dept-gelinuxnic...@cavium.com; David S.
> Miller
> Cc: net...@vger.kernel.org;
In preparation to enabling -Wimplicit-fallthrough, mark switch cases
where we are expecting to fall through.
This patch fixes the following warning:
drivers/net/ethernet/mellanox/mlx4/eq.c: In function ‘mlx4_eq_int’:
drivers/net/ethernet/mellanox/mlx4/mlx4.h:219:5: warning: this statement may
On Tue, Jan 22, 2019 at 11:04:29PM -0500, Michael S. Tsirkin wrote:
> On Wed, Jan 23, 2019 at 01:03:46AM +0800, Tiwei Bie wrote:
> > This patch introduces the support for VIRTIO_F_ORDER_PLATFORM.
> > When this feature is negotiated, driver will use the barriers
> > suitable for hardware devices.
>
-Original Message-
From: Gustavo A. R. Silva [mailto:gust...@embeddedor.com]
Sent: 23 January 2019 13:23
To: Rasesh Mody ; Sudarsana Kalluru
; dept-gelinuxnic...@cavium.com; David S. Miller
Cc: net...@vger.kernel.org; linux-kernel@vger.kernel.org; Gustavo A. R. Silva
Subject: [PATCH
The System Controller Firmware (SCFW) controls RTC, thermal
and WDOG etc., these resources' interrupt function are managed
by SCU. When any IRQ pending, SCU will notify Linux via MU general
interrupt channel #3, and Linux kernel needs to call SCU APIs
to get IRQ status and notify each module to
On i.MX8QXP, SCU uses MU1 general interrupt channel #3 to notify
user for IRQs of RTC alarm, thermal alarm and WDOG etc., mailbox
RX doorbell mode is used for this function, this patch adds
support for it.
Signed-off-by: Anson Huang
---
arch/arm64/boot/dts/freescale/imx8qxp.dtsi | 6 --
1
Add scu general interrupt function support.
Signed-off-by: Anson Huang
---
.../devicetree/bindings/arm/freescale/fsl,scu.txt | 18 --
1 file changed, 12 insertions(+), 6 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/freescale/fsl,scu.txt
On Tue, 22 Jan 2019 at 16:26, Kamil Konieczny
wrote:
>
> Document DT bindings for crypto Samsung Exynos5433 SlimSSS (Slim Security
> SubSystem) IP.
>
> Signed-off-by: Kamil Konieczny
> ---
> .../devicetree/bindings/crypto/samsung-sss.txt | 13 ++---
> 1 file changed, 10
On Wed, Jan 23, 2019 at 08:44:36AM +0100, Ulf Hansson wrote:
> On Tue, 22 Jan 2019 at 16:23, Greg Kroah-Hartman
> wrote:
> >
> > When calling debugfs functions, there is no need to ever check the
> > return value. The function can work or not, but the code logic should
> > never do something
901 - 980 of 980 matches
Mail list logo
