Geert Uytterhoeven wrote:
> On 32-bit:
>
> drivers/net/wireless/zydas/zd1211rw/zd_usb.c: In function
> ‘check_read_regs’:
> drivers/net/wireless/zydas/zd1211rw/zd_def.h:18:25: warning: format ‘%ld’
> expects argument of type ‘long int’, but argument 6 has type ‘size_t’ {aka
>
On Fri, Sep 20, 2019 at 08:11:35PM +0530, Naresh Kamboju wrote:
> On Fri, 20 Sep 2019 at 03:36, Greg Kroah-Hartman
> wrote:
> >
> > This is the start of the stable review cycle for the 5.3.1 release.
> > There are 21 patches in this series, all will be posted as a response
> > to this one. If
On Fri, Sep 20, 2019 at 03:17:48PM -0600, shuah wrote:
> On 9/19/19 4:03 PM, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.3.1 release.
> > There are 21 patches in this series, all will be posted as a response
> > to this one. If anyone has any issues with
On Fri, Sep 20, 2019 at 11:37:38AM -0700, Guenter Roeck wrote:
> On Fri, Sep 20, 2019 at 12:01:28AM +0200, Greg Kroah-Hartman wrote:
> > This is the start of the stable review cycle for the 5.2.17 release.
> > There are 124 patches in this series, all will be posted as a response
> > to this one.
On Sat, Sep 21, 2019 at 6:30 AM Albert Ou wrote:
>
> This fixes an error with how the FDT blob is reserved in memblock.
> An incorrect physical address calculation exposed the FDT header to
> unintended corruption, which typically manifested with of_fdt_raw_init()
> faulting during late boot
With this change if a perf_date parameter is provided to asciidoc
then it will override the default date written to the man page metadata.
Without this change, or if the perf_date isn't specified, then the
current date is written to the metadata. Having this parameter allows
the metadata to be
On 9/20/19 7:04 PM, Hillf Danton wrote:
>>
>
>>> It will be resent if no one saw the message.
>
>>
>
>> I didn't see it and I can't find it on lore.kernel.org/linux-pci/.
>
>>
>
> Respin, git send-email works/jj/pci-epf-uaf.txt
>
> ...
>
> From: Hillf Danton
>
> To: Bjorn Helgaas
>
>
On Sat, Sep 21, 2019 at 12:12:33AM +0100, Al Viro wrote:
> Neither hlist_add_before() nor hlist_add_behind() should ever
> be called with both arguments pointing to the same hlist_node.
> However, gcc doesn't know that, so it ends up with pointless reloads.
> AFAICS, the following generates
On Fri, Sep 20, 2019 at 04:30:20PM -0700, Andy Lutomirski wrote:
> So I think that just improving the
> getrandom()-is-blocking-on-x86-and-arm behavior, adding GRND_INSECURE
> and GRND_SECURE_BLOCKING, and adding the warning if 0 is passed is
> good enough.
I think so as well. Anyway, keep in
On 9/20/2019 6:11 PM, Jakub Kicinski wrote:
> On Tue, 17 Sep 2019 13:30:52 +0300, Alexandru Ardelean wrote:
>> The 'mac-mode' property is similar to 'phy-mode' and 'phy-connection-type',
>> which are enums of mode strings.
>>
>> The 'dwmac' driver supports almost all modes declared in the
On Fri, Sep 20, 2019 at 10:53:56PM +0200, Jiri Olsa wrote:
> On Sun, Sep 15, 2019 at 06:27:40PM +0800, Changbin Du wrote:
> > When in TUI mode, it is impossible to show all the debug messages to
> > console. This make it hard to debug perf issues using debug messages.
> > This patch adds support
Gentle ping for status of this series. thx!
On Mon, Sep 09, 2019 at 10:44:44PM +0800, Changbin Du wrote:
> This series is a trivial improvment for the layout of 'kernel hacking'
> configuration menu. Now we have many items in it which makes takes
> a little time to look up them since they are not
On Wed, 18 Sep 2019 14:14:47 +0300, Alexandru Ardelean wrote:
> The `adi,disable-energy-detect` property was implemented in an initial
> version of the `adin` driver series, but after a review it was discarded in
> favor of implementing the ETHTOOL_PHY_EDPD phy-tunable option.
>
> With the
Code cleanup for hash bits calculation by
calling rounddown_pow_of_two() and ilog2()
Signed-off-by: Chengguang Xu
---
fs/quota/dquot.c | 8 ++--
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/fs/quota/dquot.c b/fs/quota/dquot.c
index 6e826b454082..679dd3b5db70 100644
---
Load size was limited to 64MB, this was legacy limitation due to vmalloc()
which was removed a while ago.
Limiting load size to 64MB is both pointless and affects real world use
cases.
Signed-off-by: zhanglin
---
security/selinux/selinuxfs.c | 4
1 file changed, 4 deletions(-)
diff --git
On 9/20/19, Trond Myklebust wrote:
> On Fri, 2019-09-20 at 14:23 -0400, Nick Bowler wrote:
>> Not sure how reproducible this is. Since I've never seen a crash
>> like this before it may be a regression compared to, say, Linux 4.19
>> but I am not certain because this particular machine is brand
On Tue, 17 Sep 2019 23:45:21 -0500, Navid Emamdoost wrote:
> In ql_run_loopback_test, ql_lb_send does not release skb when fails. So
> it must be released before returning.
>
> Signed-off-by: Navid Emamdoost
> ---
> drivers/net/ethernet/qlogic/qlge/qlge_ethtool.c | 4 +++-
Thanks for the patch,
On Sat, Sep 21, 2019 at 9:19 AM John Hubbard wrote:
>
> On 9/20/19 5:33 PM, Qiujun Huang wrote:
> >> On 9/20/19 8:51 AM, Qiujun Huang wrote:
> ...
> >> It would be nice if this spelled out a little more clearly what's
> >> wrong. I think you and Aneesh are saying that the entry is really
> >> a
On 9/20/19 2:16 PM, Ben Hutchings wrote:
On Fri, 2019-09-20 at 13:04 -0700, Guenter Roeck wrote:
On Fri, Sep 20, 2019 at 03:23:34PM +0100, Ben Hutchings wrote:
This is the start of the stable review cycle for the 3.16.74 release.
There are 132 patches in this series, which will be posted as
Hi Richard,
On 2019/9/20 22:38, Richard Weinberger wrote:
> On Fri, Sep 20, 2019 at 4:14 PM Xiaoming Ni wrote:
>> I still think this is easier to understand:
>> Free the memory allocated by the current function in the failed branch
>
> Please note that jffs2 is in "odd fixes only" maintenance
On Tue, 17 Sep 2019 13:30:52 +0300, Alexandru Ardelean wrote:
> The 'mac-mode' property is similar to 'phy-mode' and 'phy-connection-type',
> which are enums of mode strings.
>
> The 'dwmac' driver supports almost all modes declared in the 'phy-mode'
> enum (except for 1 or 2). But in general,
On Fri, Sep 20, 2019 at 05:13:40PM -0700, Andrew Morton wrote:
> On Thu, 13 Jun 2019 10:23:18 +0200 Michal Hocko wrote:
>
> > On Wed 12-06-19 13:57:53, Joel Savitz wrote:
> > > In the event of an oom kill, useful information about the killed
> > > process is printed to dmesg. Users, especially
This fixes an error with how the FDT blob is reserved in memblock.
An incorrect physical address calculation exposed the FDT header to
unintended corruption, which typically manifested with of_fdt_raw_init()
faulting during late boot after fdt_totalsize() returned a wrong value.
Systems with
On 9/20/19 5:38 PM, Hillf Danton wrote:
>>Kishon, Hillf, can you turn it into a patch and send it asap please ?
>
>
>
> What was sent a couple of days before,
>
>
>
> To: Bjorn Helgaas
>
> Cc: linux-pci , LKML
>
> Subject: [PATCH] PCI: endpoint: Fix uaf on unregistering driver
>
> ...
On Thu, Sep 05, 2019 at 02:03:42PM +0200, Thomas Gleixner wrote:
> Right now there is no restriction at all to attach a Posix CPU timer to any
> process in the system. Per thread CPU timers are limited to be created by
> threads in the same thread group.
>
> Timers can be used to observe activity
>On 9/20/19 8:51 AM, Qiujun Huang wrote:
>> __get_user_pages_fast try to walk the page table but the
>> hugepage pte is replace by hwpoison swap entry by mca path.
>
>I expect you mean MCE (machine check exception), rather than mca?
Yeah
>
>> ...
>> [15798.177437] mce: Uncorrected hardware memory
On 9/19/19 11:35 PM, Hui Zhu wrote:
> This is the second version of this patch. The previous version is in
> https://lkml.org/lkml/2019/9/11/935
> I updated the commit introduction and Kconfig because it is not clear.
>
Hi,
Just a few minor fixes (below):
>
> Signed-off-by: Hui Zhu
> ---
>
On Fri, Sep 20, 2019 at 06:49:07AM +0800, Sam Shih wrote:
> From: Ryder Lee
>
> This adds a property "num-pwms" in example so that we could
> specify the number of PWM channels via device tree.
>
> Signed-off-by: Ryder Lee
> Signed-off-by: Sam Shih
> Reviewed-by: Matthias Brugger
> Acked-by:
On Thu, 13 Jun 2019 10:23:18 +0200 Michal Hocko wrote:
> On Wed 12-06-19 13:57:53, Joel Savitz wrote:
> > In the event of an oom kill, useful information about the killed
> > process is printed to dmesg. Users, especially system administrators,
> > will find it useful to immediately see the UID
[PATCH] tracing: Sample module to demonstrate kernel access to Ftrace
Hi,
This patch is for a sample module to demonstrate the use of APIs that
were introduced/exported in order to access Ftrace instances from within the
kernel.
Please Note: This module is dependent on -
- commit: f45d122
This is a sample module to demostrate the use of the newly introduced and
exported APIs to access Ftrace instances from within the kernel.
Newly introduced APIs used here -
1. Create a new trace array if it does not exist.
struct trace_array *trace_array_create(const char *name)
2.
Hi Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/nvdimm/nvdimm
tags/libnvdimm-for-5.4
...to receive some reworks to better support nvdimms on powerpc and an
nvdimm security interface update.
There was some last minute build breakage detected in -next so I've
left a
On Thu, Sep 19, 2019 at 8:09 AM Thomas Gleixner wrote:
>
> Replace the syscall entry work handling with the generic version, Provide
> the necessary helper inlines to handle the real architecture specific
> parts, e.g. audit and seccomp invocations.
> - if (work & (_TIF_SYSCALL_TRACE |
On Thu, Sep 19, 2019 at 8:09 AM Thomas Gleixner wrote:
>
> Evaluating _TIF_NOHZ to decide whether to use the slow syscall entry path
> is not only pointless, it's actually counterproductive:
>
> 1) Context tracking code is invoked unconditionally before that flag is
> evaluated.
>
> 2) If
On Thu, Sep 19, 2019 at 8:09 AM Thomas Gleixner wrote:
>
> On syscall entry certain work needs to be done conditionally like tracing,
> seccomp etc. This code is duplicated in all architectures.
>
> Provide a generic version.
>
> Signed-off-by: Thomas Gleixner
> ---
> arch/Kconfig
On Thu, 22 Aug 2019 16:03:44 -0700 Andrew Morton
wrote:
> On Tue, 20 Aug 2019 15:18:24 +0200 Vlastimil Babka wrote:
>
> > v2: also fix THP split handling (added Patch 1) per Kirill
> >
> > The debug_pagealloc functionality serves a similar purpose on the page
> > allocator level that
On Fri, Sep 20, 2019 at 3:44 PM Linus Torvalds
wrote:
>
> On Fri, Sep 20, 2019 at 1:51 PM Andy Lutomirski wrote:
> >
> > To be clear, when I say "blocking", I mean "blocks until we're ready,
> > but we make sure we're ready in a moderately timely manner".
>
> .. an I want a pony.
>
> The problem
Hello Shengjiu,
One issue for error-out and some nit-pickings inline. Thanks.
On Thu, Sep 19, 2019 at 08:11:42PM +0800, Shengjiu Wang wrote:
> There is error "aplay: pcm_write:2023: write error: Input/output error"
> on i.MX8QM/i.MX8QXP platform for S24_3LE format.
>
> In i.MX8QM/i.MX8QXP, the
On Thu, 15 Aug 2019 11:02:16 +0100 Catalin Marinas
wrote:
> On Wed, Aug 14, 2019 at 03:07:11PM -0400, Qian Cai wrote:
> > The only way to obtain the current memory pool size for a running kernel
> > is to check back the kernel config file which is inconvenient. Record it
> > in the kernel
Add support for expectations, which allow properties to be specified and
then verified in tests.
Signed-off-by: Brendan Higgins
Reviewed-by: Greg Kroah-Hartman
Reviewed-by: Logan Gunthorpe
Reviewed-by: Stephen Boyd
---
include/kunit/test.h | 836 +++
Add core facilities for defining unit tests; this provides a common way
to define test cases, functions that execute code which is under test
and determine whether the code under test behaves as expected; this also
provides a way to group together related test cases in test suites (here
we call
Create a common API for test managed resources like memory and test
objects. A lot of times a test will want to set up infrastructure to be
used in test cases; this could be anything from just wanting to allocate
some memory to setting up a driver stack; this defines facilities for
creating "test
Quoting Amit Kucheria (2019-09-20 15:14:58)
> On Fri, Sep 20, 2019 at 3:09 PM Stephen Boyd wrote:
> >
> > Ok so the plan is to change DT and then change it back? That sounds
> > quite bad so please fix the thermal core to not care about this before
> > applying these changes so that we don't
Neither hlist_add_before() nor hlist_add_behind() should ever
be called with both arguments pointing to the same hlist_node.
However, gcc doesn't know that, so it ends up with pointless reloads.
AFAICS, the following generates better code, is obviously equivalent
in case when arguments are
On Fri, Sep 20, 2019 at 4:05 PM Linus Torvalds
wrote:
>
>
> Now, I hear you say "those are so small these days that it doesn't
> matter". And maybe you're right. But particularly for slow media,
> triggering good streaming write behavior has been a problem in the
> past.
Which reminds me: the
On Fri, Sep 20, 2019 at 12:35 AM Konstantin Khlebnikov
wrote:
>
> This patch implements write-behind policy which tracks sequential writes
> and starts background writeback when file have enough dirty pages.
Apart from a spelling error ("contigious"), my only reaction is that
I've wanted this
On Fri, Sep 20, 2019 at 12:12 PM Jiri Olsa wrote:
>
> On Tue, Sep 03, 2019 at 11:26:03PM -0700, Stephane Eranian wrote:
> > Now that the default perf_events paranoid level is set to 2, a regular user
> > cannot monitor kernel level activity anymore. As such, with the following
> > cmdline:
> >
>
Now that the default perf_events paranoid level is set to 2, a regular user
cannot monitor kernel level activity anymore. As such, with the following
cmdline:
$ perf record -e cycles date
The perf tool first tries cycles:uk but then falls back to cycles:u
as can be seen in the perf report
On Sat, Sep 14, 2019 at 07:35:02AM -0500, Eric W. Biederman wrote:
>
> The current task on the runqueue is currently read with rcu_dereference().
>
> To obtain ordinary rcu semantics for an rcu_dereference of rq->curr it needs
> to be paird with rcu_assign_pointer of rq->curr. Which provides
First time emailing to this mailing list so please let me know if I made
a mistake in how I sent it. I'm trying to receive a notification from
the kernel once it verifies an ACK packet in a handshake. Problem is,
there is no API or kernel resource I've seen that supports this feature
for both
The pull request you sent on Fri, 20 Sep 2019 15:12:26 -0600:
> git://github.com/awilliam/linux-vfio.git tags/vfio-v5.4-rc1
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/1ddd00276fd5fbd14dd5e366d8777dcd5f2d1b65
Thank you!
--
Deet-doot-dot, I am a bot.
The pull request you sent on Fri, 20 Sep 2019 14:40:42 -0700:
> https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git
> tags/clk-for-linus
has been merged into torvalds/linux.git:
https://git.kernel.org/torvalds/c/a703d279c57e1bfe2b6536c3a17c1c498b416d24
Thank you!
--
Deet-doot-dot,
On Fri, Sep 20, 2019 at 10:16:49PM +0100, Ben Hutchings wrote:
> On Fri, 2019-09-20 at 13:04 -0700, Guenter Roeck wrote:
> > On Fri, Sep 20, 2019 at 03:23:34PM +0100, Ben Hutchings wrote:
> > > This is the start of the stable review cycle for the 3.16.74 release.
> > > There are 132 patches in
In predicate_parse, there is an error path that is not going to
out_free instead it returns directly which leads to memory leak.
Signed-off-by: Navid Emamdoost
---
kernel/trace/trace_events_filter.c | 6 --
1 file changed, 4 insertions(+), 2 deletions(-)
diff --git
On Mon, Aug 12, 2019 at 11:58:53PM +0200, Uwe Kleine-König wrote:
> On Mon, Aug 12, 2019 at 10:50:01PM +0200, Paul Cercueil wrote:
> >
> >
> > Le lun. 12 août 2019 à 7:55, Uwe =?iso-8859-1?q?Kleine-K=F6nig?=
> > a écrit :
> > > On Fri, Aug 09, 2019 at 07:33:24PM +0200, Paul Cercueil wrote:
> >
On Thu, Sep 19, 2019 at 08:11:41PM +0800, Shengjiu Wang wrote:
> When set the runtime hardware parameters, we may need to query
> the capability of DMA to complete the parameters.
>
> This patch is to Extract this operation from
> dmaengine_pcm_set_runtime_hwparams function to a separate function
On Fri, Sep 20, 2019 at 1:51 PM Andy Lutomirski wrote:
>
> To be clear, when I say "blocking", I mean "blocks until we're ready,
> but we make sure we're ready in a moderately timely manner".
.. an I want a pony.
The problem is that you start from an assumption that we simply can't
seem to do.
On Tue, 17 Sep 2019 02:35:10 PDT (-0700), m...@aurabindo.in wrote:
‐‐‐ Original Message ‐‐‐
On Sunday, September 15, 2019 12:57 AM, Palmer Dabbelt
wrote:
On Sat, 14 Sep 2019 06:05:59 PDT (-0700), Anup Patel wrote:
> > -Original Message-
> > From:
Patch to support INT33FE ACPI pseudo-device on hardware with USB Micro-B
connector.
v5:
- Spelling corrections in Kconfig, commit description and comments;
- Micro-B code: Remove warning at fuel gauge registration failure and
use PTR_ERR_OR_ZERO() for simplicity.
v4:
- Micro-B variant: Don't
Existing intel_cht_int33fe ACPI pseudo-device driver assumes that
hardware has Type-C connector and register related devices described as
I2C connections in the _CRS resource.
There is at least one hardware (Lenovo Yoga Book YB1-91L/F) with Micro-B
USB connector exists. It has INT33FE device in
On Fri, Sep 20 2019 at 16:22 -0600, Stephen Boyd wrote:
Quoting Lina Iyer (2019-09-11 09:15:57)
On Thu, Sep 05 2019 at 18:39 -0600, Stephen Boyd wrote:
>Quoting Lina Iyer (2019-08-29 11:11:51)
>> When an interrupt is to be serviced, the convention is to mask the
>> interrupt at the chip and
Quoting Lina Iyer (2019-09-11 09:15:57)
> On Thu, Sep 05 2019 at 18:39 -0600, Stephen Boyd wrote:
> >Quoting Lina Iyer (2019-08-29 11:11:51)
> >> When an interrupt is to be serviced, the convention is to mask the
> >> interrupt at the chip and unmask after servicing the interrupt. Enabling
> >>
Quoting Lina Iyer (2019-09-17 14:50:20)
> On Fri, Sep 13 2019 at 13:53 -0600, Lina Iyer wrote:
> >On Thu, Sep 05 2019 at 18:03 -0600, Stephen Boyd wrote:
> >>Quoting Lina Iyer (2019-09-03 10:07:22)
> >>>On Mon, Sep 02 2019 at 07:58 -0600, Marc Zyngier wrote:
> On 02/09/2019 14:38, Rob Herring
On Fri, Sep 20, 2019 at 3:09 PM Stephen Boyd wrote:
>
> Quoting Amit Kucheria (2019-09-20 15:07:25)
> > On Fri, Sep 20, 2019 at 3:02 PM Stephen Boyd wrote:
> > >
> > > Quoting Amit Kucheria (2019-09-20 14:52:24)
> > > > Register upper-lower interrupts for each of the two tsens controllers.
> > >
On Fri, Sep 20, 2019 at 02:51:14PM -0700, Andrii Nakryiko wrote:
On Fri, Sep 20, 2019 at 12:19 PM Ivan Khoronzhuk
wrote:
On Fri, Sep 20, 2019 at 09:34:51PM +0300, Ivan Khoronzhuk wrote:
>On Fri, Sep 20, 2019 at 09:41:54AM -0700, Andrii Nakryiko wrote:
>>On Fri, Sep 20, 2019 at 1:22 AM Ivan
On Fri, 20 Sep 2019 09:36:57 -0700, Florian Fainelli wrote:
> On 9/20/19 8:30 AM, Markus Elfring wrote:
> >> netdev is closed at the moment for patch.
> >
> > I wonder about this information.
>
> This is covered here:
>
>
On Fri, Sep 20, 2019 at 3:07 PM Amit Kucheria wrote:
>
> On Fri, Sep 20, 2019 at 3:02 PM Stephen Boyd wrote:
> >
> > Quoting Amit Kucheria (2019-09-20 14:52:24)
> > > Register upper-lower interrupts for each of the two tsens controllers.
> > >
> > > Signed-off-by: Amit Kucheria
> > > ---
> > >
Quoting Amit Kucheria (2019-09-20 15:07:25)
> On Fri, Sep 20, 2019 at 3:02 PM Stephen Boyd wrote:
> >
> > Quoting Amit Kucheria (2019-09-20 14:52:24)
> > > Register upper-lower interrupts for each of the two tsens controllers.
> > >
> > > Signed-off-by: Amit Kucheria
> > > ---
> > >
On Fri, Sep 20, 2019 at 3:02 PM Stephen Boyd wrote:
>
> Quoting Amit Kucheria (2019-09-20 14:52:24)
> > Register upper-lower interrupts for each of the two tsens controllers.
> >
> > Signed-off-by: Amit Kucheria
> > ---
> > arch/arm64/boot/dts/qcom/msm8996.dtsi | 60 ++-
Quoting Amit Kucheria (2019-09-20 14:52:30)
> Depending on the IP version, TSENS supports upper, lower and critical
> threshold interrupts. We only add support for upper and lower threshold
> interrupts for now.
>
> TSENSv2 has an irq [status|clear|mask] bit tuple for each sensor while
> earlier
Quoting Amit Kucheria (2019-09-20 14:52:29)
> Hide the details of how to convert values read from TSENS HW to mCelsius
> behind a function. All versions of the IP can be supported as a result.
>
> Signed-off-by: Amit Kucheria
> ---
Reviewed-by: Stephen Boyd
Just one nit below.
>
Quoting Amit Kucheria (2019-09-20 14:52:24)
> Register upper-lower interrupts for each of the two tsens controllers.
>
> Signed-off-by: Amit Kucheria
> ---
> arch/arm64/boot/dts/qcom/msm8996.dtsi | 60 ++-
> 1 file changed, 32 insertions(+), 28 deletions(-)
>
> diff
From: "Steven Rostedt (VMware)"
Revert swork version of: block: blk-mq: move blk_queue_usage_counter_release()
into process context
In order to switch to upstream, we need to revert the swork code.
Signed-off-by: Steven Rostedt (VMware)
---
block/blk-core.c | 14 +-
From: "Steven Rostedt (VMware)"
Revert: thermal: Defer thermal wakups to threads
Signed-off-by: Steven Rostedt (VMware)
---
drivers/thermal/x86_pkg_temp_thermal.c | 52 ++
1 file changed, 3 insertions(+), 49 deletions(-)
diff --git
To be able to backport some of the fixes done in upstream RT, I need
to revert the simple work code and incorporate the work queue rework
that was done in rt-devel. I originally thought this crashed under
stress test (as I reported in the stable meeting), but found that
the system booted a
From: Sebastian Andrzej Siewior
[ Upstream commit d15a862f24df983458533aebd6fa207ecdd1095a ]
This is an all-in change of the workqueue rework.
The worker_pool.lock is made to raw_spinlock_t. With this change we can
schedule workitems from preempt-disable sections and sections with disabled
From: "Steven Rostedt (VMware)"
revert: fs/aio: simple simple work
Signed-off-by: Steven Rostedt (VMware)
---
fs/aio.c | 15 ++-
1 file changed, 2 insertions(+), 13 deletions(-)
diff --git a/fs/aio.c b/fs/aio.c
index 16dcf8521c2c..911e23087dfb 100644
--- a/fs/aio.c
+++ b/fs/aio.c
From: Sebastian Andrzej Siewior
[ Upstream commit 61c928ecf4fe200bda9b49a0813b5ba0f43995b5 ]
| BUG: sleeping function called from invalid context at
kernel/locking/rtmutex.c:914
| in_atomic(): 1, irqs_disabled(): 0, pid: 255, name: kworker/u257:6
| 5 locks held by kworker/u257:6/255:
| #0:
From: Sebastian Andrzej Siewior
[ Upstream commit 1a142116f6435ef070ecebb66d2d599507c10601 ]
|BUG: sleeping function called from invalid context at
kernel/locking/rtmutex.c:768
|in_atomic(): 1, irqs_disabled(): 0, pid: 26, name: rcuos/2
|2 locks held by rcuos/2/26:
| #0:
From: Daniel Wagner
[ Upstream commit ad2408dc248fe58536eef5b2b5734d8f9d3a280b ]
On RT the spin lock in pkg_temp_thermal_platfrom_thermal_notify will
call schedule while we run in irq context.
[] dump_stack+0x4e/0x8f
[] __schedule_bug+0xa6/0xb4
[] __schedule+0x5b4/0x700
[] schedule+0x2a/0x90
msm8916 uses sensors 0, 1, 2, 4 and 5. Sensor 3 is NOT used. Fixup the
device tree so that the correct sensor ID is used and as a result we can
actually check the temperature for the cpu2_3 sensor.
Signed-off-by: Amit Kucheria
Reviewed-by: Daniel Lezcano
Reviewed-by: Stephen Boyd
---
Older IP only supports the 'uplow' interrupt, but newer IP supports
'uplow' and 'critical' interrupts. Document interrupt support in the
tsens driver by converting over to a YAML schema.
Suggested-by: Stephen Boyd
Signed-off-by: Amit Kucheria
---
.../bindings/thermal/qcom-tsens.txt |
Dump some basic version info and sensor details into debugfs. Example
from qcs404 below:
--(/sys/kernel/debug) $ ls tsens/
4a9000.thermal-sensor version
--(/sys/kernel/debug) $ cat tsens/version
1.4.0
--(/sys/kernel/debug) $ cat tsens/4a9000.thermal-sensor/sensors
max: 11
num: 10
id
Printing the function name when enabling debugging makes logs easier to
read.
Signed-off-by: Amit Kucheria
Reviewed-by: Stephen Boyd
Reviewed-by: Daniel Lezcano
---
drivers/thermal/qcom/tsens-common.c | 8
drivers/thermal/qcom/tsens.c| 6 +++---
2 files changed, 7
There are two fields - id and hw_id - to track what sensor an action was
to performed on. This was because the sensors connected to a TSENS IP
might not be contiguous i.e. 1, 2, 4, 5 with 3 being skipped.
This causes confusion in the code which uses hw_id sometimes and id
other times
Move platform_set_drvdata up to avoid an extra 'if (ret)' check after
the call to tsens_register.
Signed-off-by: Amit Kucheria
Reviewed-by: Stephen Boyd
Reviewed-by: Daniel Lezcano
---
drivers/thermal/qcom/tsens.c | 8 +++-
1 file changed, 3 insertions(+), 5 deletions(-)
diff --git
Changes since v3:
- Fix up the YAML definitions based on Rob's review
Changes since v2:
- Addressed Stephen's review comment
- Moved the dt-bindings to yaml (This throws up some new warnings in various
QCOM
devicetrees. I'll send out a separate series to fix them up)
- Collected reviews and acks
Hide the details of how to convert values read from TSENS HW to mCelsius
behind a function. All versions of the IP can be supported as a result.
Signed-off-by: Amit Kucheria
---
drivers/thermal/qcom/tsens-common.c | 50 +
1 file changed, 36 insertions(+), 14
Register upper-lower interrupt for the tsens controller.
Signed-off-by: Amit Kucheria
---
arch/arm64/boot/dts/qcom/msm8916.dtsi | 22 --
1 file changed, 12 insertions(+), 10 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/msm8916.dtsi
Register upper-lower interrupt for the tsens controller.
Signed-off-by: Amit Kucheria
---
arch/arm64/boot/dts/qcom/qcs404.dtsi | 42 +++-
1 file changed, 22 insertions(+), 20 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/qcs404.dtsi
Register upper-lower interrupts for each of the two tsens controllers.
Signed-off-by: Amit Kucheria
Reviewed-by: Stephen Boyd
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 88 +++-
1 file changed, 46 insertions(+), 42 deletions(-)
diff --git
msm8974 has 11 sensors connected to a single TSENS IP. Define a thermal
zone for each of those sensors to expose the temperature of each zone.
Signed-off-by: Amit Kucheria
Tested-by: Brian Masney
Reviewed-by: Stephen Boyd
---
arch/arm/boot/dts/qcom-msm8974.dtsi | 90
Register upper-lower interrupts for each of the two tsens controllers.
Signed-off-by: Amit Kucheria
---
arch/arm64/boot/dts/qcom/msm8996.dtsi | 60 ++-
1 file changed, 32 insertions(+), 28 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/msm8996.dtsi
Register upper-lower interrupts for each of the two tsens controllers.
Signed-off-by: Amit Kucheria
---
arch/arm64/boot/dts/qcom/msm8998.dtsi | 82 ++-
1 file changed, 42 insertions(+), 40 deletions(-)
diff --git a/arch/arm64/boot/dts/qcom/msm8998.dtsi
Depending on the IP version, TSENS supports upper, lower and critical
threshold interrupts. We only add support for upper and lower threshold
interrupts for now.
TSENSv2 has an irq [status|clear|mask] bit tuple for each sensor while
earlier versions only have a single bit per sensor to denote
Register upper-lower interrupt for the tsens controller.
Signed-off-by: Amit Kucheria
Tested-by: Brian Masney
---
arch/arm/boot/dts/qcom-msm8974.dtsi | 36 +++--
1 file changed, 19 insertions(+), 17 deletions(-)
diff --git a/arch/arm/boot/dts/qcom-msm8974.dtsi
On Fri, Sep 20, 2019 at 12:19 PM Ivan Khoronzhuk
wrote:
>
> On Fri, Sep 20, 2019 at 09:34:51PM +0300, Ivan Khoronzhuk wrote:
> >On Fri, Sep 20, 2019 at 09:41:54AM -0700, Andrii Nakryiko wrote:
> >>On Fri, Sep 20, 2019 at 1:22 AM Ivan Khoronzhuk
> >> wrote:
> >>>
> >>>On Thu, Sep 19, 2019 at
On Fri, Sep 20, 2019 at 04:53:16PM +0200, Thierry Reding wrote:
> From: Adrian Hunter
>
> Add host operation ->set_dma_mask() so that drivers can define their own
> DMA masks.
>
> Signed-off-by: Adrian Hunter
> Signed-off-by: Thierry Reding
Tested-by: Nicolin Chen
Ran a boot test with both
>> after->start = map->end;
>> +after->pgoff = pos->map_ip(pos, map->end);
>
> So is this equivalent to what __split_vma() does in the kernel, i.e.:
>
>if (new_below)
>new->vm_end = addr;
>else {
>
On Tue, Sep 17, 2019 at 12:06 PM Rob Herring wrote:
>
> On Wed, Sep 11, 2019 at 12:46:24PM +0530, Amit Kucheria wrote:
> > Document interrupt support in the tsens driver by converting over to a
> > YAML schema.
> >
> > Suggested-by: Stephen Boyd
> > Signed-off-by: Amit Kucheria
> > ---
> >
1 - 100 of 924 matches
Mail list logo
