On Fri, 9 Oct 2020 02:46:09 +0300
Vladimir Oltean wrote:
> On Thu, Oct 08, 2020 at 05:27:49PM +0100, John Keeping wrote:
> > With threadirqs, stmmac_interrupt() is called on a thread with hardirqs
> > enabled so we cannot call __napi_schedule_irqoff(). Under lockd
() instead which will save & restore the interrupt
state.
Fixes: 4ccb45857c2c ("net: stmmac: Fix NAPI poll in TX path when in
multi-queue")
Signed-off-by: John Keeping
---
drivers/net/ethernet/stmicro/stmmac/stmmac_main.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff -
Hi,
On Fri, 17 Jul 2020 18:00:02 +0200
Thomas Gleixner wrote:
> Setting interrupt affinity on inactive interrupts is inconsistent when
> hierarchical irq domains are enabled. The core code should just store the
> affinity and not call into the irq chip driver for inactive interrupts
> because
Enable i2c transactions in irq disabled contexts like poweroff where the
PMIC is connected via i2c.
Signed-off-by: John Keeping
---
drivers/i2c/busses/i2c-rk3x.c | 39 +++
1 file changed, 35 insertions(+), 4 deletions(-)
diff --git a/drivers/i2c/busses/i2c
-by: John Keeping
---
drivers/input/touchscreen/st1232.c | 55 +-
1 file changed, 46 insertions(+), 9 deletions(-)
diff --git a/drivers/input/touchscreen/st1232.c
b/drivers/input/touchscreen/st1232.c
index 63b29c7279e2..4e032d3a3737 100644
--- a/drivers/input/touchscreen
Commit-ID: e2736219e6ca3117e10651e215b96d66775220da
Gitweb: https://git.kernel.org/tip/e2736219e6ca3117e10651e215b96d66775220da
Author: John Keeping
AuthorDate: Thu, 15 Aug 2019 11:01:46 +0100
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 16 Aug 2019 12:30:14 -0300
perf unwind
Commit-ID: e8ba2906f6b9054102ad035ac9cafad9d4168589
Gitweb: https://git.kernel.org/tip/e8ba2906f6b9054102ad035ac9cafad9d4168589
Author: John Keeping
AuthorDate: Thu, 15 Aug 2019 11:01:45 +0100
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 16 Aug 2019 12:25:57 -0300
perf unwind
Commit-ID: ab6cd0e5276e24403751e0b3b8ed807738a8571f
Gitweb: https://git.kernel.org/tip/ab6cd0e5276e24403751e0b3b8ed807738a8571f
Author: John Keeping
AuthorDate: Thu, 15 Aug 2019 11:01:44 +0100
Committer: Arnaldo Carvalho de Melo
CommitDate: Fri, 16 Aug 2019 12:25:23 -0300
perf map
only for thread group leader")
Cc: Konstantin Khlebnikov
Signed-off-by: John Keeping
---
v2:
- Remove unrelated change that has moved to the next patch
- Improve commit message to describe a scenario that shows the bug
---
tools/perf/util/map.c| 3 ++-
tools/pe
If dwarf_callchain_users is false, then unwind__prepare_access() will
not set unwind_libunwind_ops so the remaining test here is sufficient.
Signed-off-by: John Keeping
---
v2: new patch split out from patch 2
---
tools/perf/util/unwind-libunwind.c | 6 --
1 file changed, 6 deletions
In the next commit we will add new fields to map_groups and we need
these to be null if no value is assigned. The simplest way to achieve
this is to request zeroed memory from the allocator.
Signed-off-by: John Keeping
---
Unchanged in v2
---
tools/perf/util/map.c | 2 +-
1 file changed, 1
On Fri, 2 Aug 2019 15:30:39 +0200
Jiri Olsa wrote:
> On Mon, Jul 29, 2019 at 06:24:30PM +0100, John Keeping wrote:
> > Commit e5adfc3e7e77 ("perf map: Synthesize maps only for thread group
> > leader") changed the recording side so that we no longer get mmap events
&
In the next commit we will add new fields to map_groups and we need
these to be null if no value is assigned. The simplest way to achieve
this is to request zeroed memory from the allocator.
Signed-off-by: John Keeping
---
tools/perf/util/map.c | 2 +-
1 file changed, 1 insertion(+), 1
lebnikov
Signed-off-by: John Keeping
---
tools/perf/util/map.c| 3 +-
tools/perf/util/map_groups.h | 4 +++
tools/perf/util/thread.c | 7 ++---
tools/perf/util/thread.h | 4 ---
tools/perf/util/unwind-libunwind-local.c | 18 +---
Hi Minas,
On Wed, 19 Dec 2018 14:09:01 +
Minas Harutyunyan wrote:
> On 12/18/2018 6:35 PM, John Keeping wrote:
> > Hi Minas,
> >
> > On Fri, 14 Dec 2018 09:00:08 +
> > Minas Harutyunyan wrote:
> >> First of all, sorry for delayed answer.
> >
Hi Minas,
On Fri, 14 Dec 2018 09:00:08 +
Minas Harutyunyan wrote:
> First of all, sorry for delayed answer.
> Looks like similar issue seen by Andrzej Pietrasiewicz
> : "dwc2 isochronous transfers issues". Same
> feedback provided to Andrzej.
>
> I run tests on 4.20.0-rc4 in DDMA. By
Hi Minas,
On Fri, 9 Nov 2018 14:36:36 +
Minas Harutyunyan wrote:
> On 11/9/2018 12:43 PM, Minas Harutyunyan wrote:
> > Hi John,
> >
> > On 11/8/2018 9:37 PM, John Keeping wrote:
> >> Hi Minas,
> >>
> >> On Mon, 5 Nov 2018 08:28:07 +
&g
Hi Minas,
On Fri, 9 Nov 2018 14:36:36 +
Minas Harutyunyan wrote:
> On 11/9/2018 12:43 PM, Minas Harutyunyan wrote:
> > Hi John,
> >
> > On 11/8/2018 9:37 PM, John Keeping wrote:
> >> Hi Minas,
> >>
> >> On Mon, 5 Nov 2018 08:28:07 +
&g
req_running != -1
req_running = -1
_start channel
Signed-off-by: John Keeping
---
drivers/dma/pl330.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/dma/pl330.c b/drivers/dma/pl330.c
index 370df2e74ddd..88750a34e859 100644
req_running != -1
req_running = -1
_start channel
Signed-off-by: John Keeping
---
drivers/dma/pl330.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/drivers/dma/pl330.c b/drivers/dma/pl330.c
index 370df2e74ddd..88750a34e859 100644
by
schedule_timeout() is the same as the original timeout (HCI_INIT_TIMEOUT
on a system with HZ=1000).
Use wait_event_interruptible_timeout() instead of open-coding similar
behaviour which is subject to the spurious failure described above.
Signed-off-by: John Keeping <j...@metanate.com>
---
I saw pr
by
schedule_timeout() is the same as the original timeout (HCI_INIT_TIMEOUT
on a system with HZ=1000).
Use wait_event_interruptible_timeout() instead of open-coding similar
behaviour which is subject to the spurious failure described above.
Signed-off-by: John Keeping
---
I saw problems with the -rt patchset
If there are multiple functions associated with a configuration, then
the UAC2 interfaces may not start at zero. Set the correct first
interface number in the association descriptor so that the audio
interfaces are enumerated correctly in this case.
Signed-off-by: John Keeping <j...@metanate.
If there are multiple functions associated with a configuration, then
the UAC2 interfaces may not start at zero. Set the correct first
interface number in the association descriptor so that the audio
interfaces are enumerated correctly in this case.
Signed-off-by: John Keeping
Reviewed
pace
programs continue to work correctly and, as a bonus, old programs are
now compliant with the specification without having to fix anything
themselves.
Fixes: 53642399aa71 ("usb: gadget: f_fs: Fix wrong check on reserved1 of
OS_DESC_EXT_COMPAT")
Cc: sta...@vger.kernel.org
Signed
pace
programs continue to work correctly and, as a bonus, old programs are
now compliant with the specification without having to fix anything
themselves.
Fixes: 53642399aa71 ("usb: gadget: f_fs: Fix wrong check on reserved1 of
OS_DESC_EXT_COMPAT")
Cc: sta...@vger.kernel.org
Signed-off-b
tinue to work correctly and, as a bonus, old programs are
now compliant with the specification without having to fix anything
themselves.
Fixes: 53642399aa71 ("usb: gadget: f_fs: Fix wrong check on reserved1 of
OS_DESC_EXT_COMPAT")
Cc: sta...@vger.kernel.org
Signed-off-by: John Keeping <
tinue to work correctly and, as a bonus, old programs are
now compliant with the specification without having to fix anything
themselves.
Fixes: 53642399aa71 ("usb: gadget: f_fs: Fix wrong check on reserved1 of
OS_DESC_EXT_COMPAT")
Cc: sta...@vger.kernel.org
Signed-off-by: John Keep
On Fri, 10 Nov 2017 12:40:39 +0200, Felipe Balbi wrote:
> John Keeping <j...@metanate.com> writes:
> > This check has gone through several incompatible variations in commits
> > 53642399aa71 ("usb: gadget: f_fs: Fix wrong check on reserved1 of
> > OS_DESC_EXT_COMP
On Fri, 10 Nov 2017 12:40:39 +0200, Felipe Balbi wrote:
> John Keeping writes:
> > This check has gone through several incompatible variations in commits
> > 53642399aa71 ("usb: gadget: f_fs: Fix wrong check on reserved1 of
> > OS_DESC_EXT_COMPAT"), 354bc4
ust
drop the condition to avoid breaking userspace.
Fixes: 53642399aa71 ("usb: gadget: f_fs: Fix wrong check on reserved1 of
OS_DESC_EXT_COMPAT")
Cc: sta...@vger.kernel.org # v4.7+
Signed-off-by: John Keeping <j...@metanate.com>
---
drivers/usb/gadget/function/f_fs.c | 3 +--
1
ust
drop the condition to avoid breaking userspace.
Fixes: 53642399aa71 ("usb: gadget: f_fs: Fix wrong check on reserved1 of
OS_DESC_EXT_COMPAT")
Cc: sta...@vger.kernel.org # v4.7+
Signed-off-by: John Keeping
---
drivers/usb/gadget/function/f_fs.c | 3 +--
1 file changed, 1 insertion(
On Wed, Sep 20, 2017 at 07:08:11PM +0800, hl wrote:
>
>
> On Wednesday, September 20, 2017 06:08 PM, John Keeping wrote:
> > On Tue, Sep 19, 2017 at 01:27:40PM -0700, Sean Paul wrote:
> >> On Tue, Sep 19, 2017 at 11:19:01AM -0700, Brian Norris wrote:
> >>>
On Wed, Sep 20, 2017 at 07:08:11PM +0800, hl wrote:
>
>
> On Wednesday, September 20, 2017 06:08 PM, John Keeping wrote:
> > On Tue, Sep 19, 2017 at 01:27:40PM -0700, Sean Paul wrote:
> >> On Tue, Sep 19, 2017 at 11:19:01AM -0700, Brian Norris wrote:
> >>>
On Tue, Sep 19, 2017 at 01:27:40PM -0700, Sean Paul wrote:
> On Tue, Sep 19, 2017 at 11:19:01AM -0700, Brian Norris wrote:
> > Hi Sean,
> >
> > On Tue, Sep 19, 2017 at 11:00:25AM -0700, Sean Paul wrote:
> > > On Mon, Sep 18, 2017 at 05:05:33PM +0800, Nickey Yang wrote:
> > > > This patch correct
On Tue, Sep 19, 2017 at 01:27:40PM -0700, Sean Paul wrote:
> On Tue, Sep 19, 2017 at 11:19:01AM -0700, Brian Norris wrote:
> > Hi Sean,
> >
> > On Tue, Sep 19, 2017 at 11:00:25AM -0700, Sean Paul wrote:
> > > On Mon, Sep 18, 2017 at 05:05:33PM +0800, Nickey Yang wrote:
> > > > This patch correct
mclk is enabled and disabled only in i2s_runtime_{resume,suspend}() and
we ensure that the device is runtime suspended before reaching this
clk_disable_unprepare() call, so it is wrong to call it again here.
Signed-off-by: John Keeping <j...@metanate.com>
---
sound/soc/rockchip/rockchip
mclk is enabled and disabled only in i2s_runtime_{resume,suspend}() and
we ensure that the device is runtime suspended before reaching this
clk_disable_unprepare() call, so it is wrong to call it again here.
Signed-off-by: John Keeping
---
sound/soc/rockchip/rockchip_i2s.c | 1 -
1 file changed
they complete.
Signed-off-by: John Keeping <j...@metanate.com>
---
I originally sent a version of this patch back in July [1] without any
response. Since then, I've improved the commit message and switched
from create_singlethread_workqueue() to alloc_ordered_workqueue(), so
I've marked this
they complete.
Signed-off-by: John Keeping
---
I originally sent a version of this patch back in July [1] without any
response. Since then, I've improved the commit message and switched
from create_singlethread_workqueue() to alloc_ordered_workqueue(), so
I've marked this as v2.
[1] https
Commit-ID: 596a7a1d0989c621c3ae49be73a1d1f9de22eb5a
Gitweb: http://git.kernel.org/tip/596a7a1d0989c621c3ae49be73a1d1f9de22eb5a
Author: John Keeping <j...@metanate.com>
AuthorDate: Wed, 6 Sep 2017 10:35:40 +0100
Committer: Thomas Gleixner <t...@linutronix.de>
CommitDate: Wed
Commit-ID: 596a7a1d0989c621c3ae49be73a1d1f9de22eb5a
Gitweb: http://git.kernel.org/tip/596a7a1d0989c621c3ae49be73a1d1f9de22eb5a
Author: John Keeping
AuthorDate: Wed, 6 Sep 2017 10:35:40 +0100
Committer: Thomas Gleixner
CommitDate: Wed, 6 Sep 2017 11:41:20 +0200
genirq/msi: Fix
b60 ("genirq/msi: Add msi_domain_populate_irqs")
Cc: sta...@vger.kernel.org #v4.5+
Signed-off-by: John Keeping <j...@metanate.com>
Reviewed-by: Marc Zyngier <marc.zyng...@arm.com>
---
On Wed, 6 Sep 2017 09:52:43 +0100, Marc Zyngier wrote:
> On 05/09/17 18:12, John Keepin
b60 ("genirq/msi: Add msi_domain_populate_irqs")
Cc: sta...@vger.kernel.org #v4.5+
Signed-off-by: John Keeping
Reviewed-by: Marc Zyngier
---
On Wed, 6 Sep 2017 09:52:43 +0100, Marc Zyngier wrote:
> On 05/09/17 18:12, John Keeping wrote:
> > Use the correct variable to set up
Use the correct variable to set up each interrupt in turn rather than
configuring the first interrupt "nvec" times.
Signed-off-by: John Keeping <j...@metanate.com>
---
kernel/irq/msi.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/kernel/irq/msi.c b/
Use the correct variable to set up each interrupt in turn rather than
configuring the first interrupt "nvec" times.
Signed-off-by: John Keeping
---
kernel/irq/msi.c | 5 +++--
1 file changed, 3 insertions(+), 2 deletions(-)
diff --git a/kernel/irq/msi.c b/kernel/irq/msi.c
index 48
On Fri, 25 Aug 2017 19:42:51 +0300, Andy Shevchenko wrote:
> On Fri, 2017-08-25 at 17:05 +0100, John Keeping wrote:
> > On Fri, 25 Aug 2017 10:24:26 -0400, Tom Rini wrote:
> > > On Fri, Aug 25, 2017 at 04:56:47PM +0300, Andy Shevchenko wrote:
>
> > > > Appa
On Fri, 25 Aug 2017 19:42:51 +0300, Andy Shevchenko wrote:
> On Fri, 2017-08-25 at 17:05 +0100, John Keeping wrote:
> > On Fri, 25 Aug 2017 10:24:26 -0400, Tom Rini wrote:
> > > On Fri, Aug 25, 2017 at 04:56:47PM +0300, Andy Shevchenko wrote:
>
> > > > Appa
On Fri, 25 Aug 2017 10:24:26 -0400, Tom Rini wrote:
> On Fri, Aug 25, 2017 at 04:56:47PM +0300, Andy Shevchenko wrote:
> > +John
> >
> > On Tue, 2017-08-22 at 21:51 -0400, Tom Rini wrote:
> > > Not all devices with ACPI and this combination of sound devices will
> > > have the required
On Fri, 25 Aug 2017 10:24:26 -0400, Tom Rini wrote:
> On Fri, Aug 25, 2017 at 04:56:47PM +0300, Andy Shevchenko wrote:
> > +John
> >
> > On Tue, 2017-08-22 at 21:51 -0400, Tom Rini wrote:
> > > Not all devices with ACPI and this combination of sound devices will
> > > have the required
that completed
requests are passed to userspace in the order in which they complete.
Signed-off-by: John Keeping <j...@metanate.com>
---
drivers/usb/gadget/function/f_fs.c | 10 +-
drivers/usb/gadget/function/u_fs.h | 1 +
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/drive
that completed
requests are passed to userspace in the order in which they complete.
Signed-off-by: John Keeping
---
drivers/usb/gadget/function/f_fs.c | 10 +-
drivers/usb/gadget/function/u_fs.h | 1 +
2 files changed, 10 insertions(+), 1 deletion(-)
diff --git a/drivers/usb/gadget/function
Hi Sean,
On Sun, 12 Mar 2017 07:06:59 -0500, Rob Herring wrote:
> On Fri, Mar 03, 2017 at 11:39:45AM +0000, John Keeping wrote:
> > This reset is required in order to fully reset the internal state of the
> > MIPI controller.
> >
> > Signed-off-by: John
Hi Sean,
On Sun, 12 Mar 2017 07:06:59 -0500, Rob Herring wrote:
> On Fri, Mar 03, 2017 at 11:39:45AM +0000, John Keeping wrote:
> > This reset is required in order to fully reset the internal state of the
> > MIPI controller.
> >
> > Signed-off-by: John Keeping
>
On Thu, 23 Mar 2017 11:10:20 -0500, Julia Cartwright wrote:
> One quick question below. Apologies if this has been covered, but just
> want to be sure.
>
> On Thu, Mar 23, 2017 at 10:59:28AM +, John Keeping wrote:
> > regmap_update_bits does its own locking and everyt
On Thu, 23 Mar 2017 11:10:20 -0500, Julia Cartwright wrote:
> One quick question below. Apologies if this has been covered, but just
> want to be sure.
>
> On Thu, Mar 23, 2017 at 10:59:28AM +, John Keeping wrote:
> > regmap_update_bits does its own locking and everyt
With real-time preemption, regmap functions cannot be used in the
implementation of irq_chip since they use spinlocks which may sleep.
Move the setting of the mux for IRQs to an irq_bus_sync_unlock handler
where we are allowed to sleep.
Signed-off-by: John Keeping <j...@metanate.com>
Re
With real-time preemption, regmap functions cannot be used in the
implementation of irq_chip since they use spinlocks which may sleep.
Move the setting of the mux for IRQs to an irq_bus_sync_unlock handler
where we are allowed to sleep.
Signed-off-by: John Keeping
Reviewed-by: Heiko Stuebner
regmap_update_bits does its own locking and everything else accessed
here is a local variable so there is no need to lock around it.
Signed-off-by: John Keeping <j...@metanate.com>
Reviewed-by: Heiko Stuebner <he...@sntech.de>
Tested-by: Heiko Stuebner <he...@sntech.de>
---
regmap_update_bits does its own locking and everything else accessed
here is a local variable so there is no need to lock around it.
Signed-off-by: John Keeping
Reviewed-by: Heiko Stuebner
Tested-by: Heiko Stuebner
---
v3: unchanged
v2.1:
- Remove RK2928 locking in rockchip_set_pull()
v2
This lock is used from rockchip_irq_set_type() which is part of the
irq_chip implementation and thus must use raw_spinlock_t as documented
in Documentation/gpio/driver.txt.
Signed-off-by: John Keeping <j...@metanate.com>
Reviewed-by: Heiko Stuebner <he...@sntech.de>
Tested-by: Heiko
The aim of the series is to make the Rockchip pinctrl irq_chip
implementation safe for use with RT_FULL which requires that raw
spinlocks are used to avoid sleeping in hardirq context.
v4 is v3 rebased onto pinctrl/devel as of b9c6dcab265e ("pinctrl: rockchip:
rename RK1108 to RV1108&quo
The aim of the series is to make the Rockchip pinctrl irq_chip
implementation safe for use with RT_FULL which requires that raw
spinlocks are used to avoid sleeping in hardirq context.
v4 is v3 rebased onto pinctrl/devel as of b9c6dcab265e ("pinctrl: rockchip:
rename RK1108 to RV1108&quo
This lock is used from rockchip_irq_set_type() which is part of the
irq_chip implementation and thus must use raw_spinlock_t as documented
in Documentation/gpio/driver.txt.
Signed-off-by: John Keeping
Reviewed-by: Heiko Stuebner
Tested-by: Heiko Stuebner
---
v3: unchanged
v2: unchanged
rockchip_verify_mux() function from there.
Signed-off-by: John Keeping <j...@metanate.com>
Reviewed-by: Heiko Stuebner <he...@sntech.de>
Tested-by: Heiko Stuebner <he...@sntech.de>
---
v3: unchanged
v2: unchanged
---
drivers/pinctrl/pinct
rockchip_verify_mux() function from there.
Signed-off-by: John Keeping
Reviewed-by: Heiko Stuebner
Tested-by: Heiko Stuebner
---
v3: unchanged
v2: unchanged
---
drivers/pinctrl/pinctrl-rockchip.c | 46 +-
1 file changed, 30 insertions(+), 16 deletions
This lock is used from rockchip_irq_set_type() which is part of the
irq_chip implementation and thus must use raw_spinlock_t as documented
in Documentation/gpio/driver.txt.
Signed-off-by: John Keeping <j...@metanate.com>
Reviewed-by: Heiko Stuebner <he...@sntech.de>
Tested-by: Heiko
This lock is used from rockchip_irq_set_type() which is part of the
irq_chip implementation and thus must use raw_spinlock_t as documented
in Documentation/gpio/driver.txt.
Signed-off-by: John Keeping
Reviewed-by: Heiko Stuebner
Tested-by: Heiko Stuebner
---
v3: unchanged
v2: unchanged
regmap_update_bits does its own locking and everything else accessed
here is a local variable so there is no need to lock around it.
Signed-off-by: John Keeping <j...@metanate.com>
Reviewed-by: Heiko Stuebner <he...@sntech.de>
Tested-by: Heiko Stuebner <he...@sntech.de>
---
regmap_update_bits does its own locking and everything else accessed
here is a local variable so there is no need to lock around it.
Signed-off-by: John Keeping
Reviewed-by: Heiko Stuebner
Tested-by: Heiko Stuebner
---
v3: unchanged
v2.1:
- Remove RK2928 locking in rockchip_set_pull()
v2
rockchip_verify_mux() function from there.
Signed-off-by: John Keeping <j...@metanate.com>
Reviewed-by: Heiko Stuebner <he...@sntech.de>
Tested-by: Heiko Stuebner <he...@sntech.de>
---
v3: unchanged
v2: unchanged
---
drivers/pinctrl/pinct
rockchip_verify_mux() function from there.
Signed-off-by: John Keeping
Reviewed-by: Heiko Stuebner
Tested-by: Heiko Stuebner
---
v3: unchanged
v2: unchanged
---
drivers/pinctrl/pinctrl-rockchip.c | 46 +-
1 file changed, 30 insertions(+), 16 deletions
version so it's simpler to
apply.
[1] https://www.spinics.net/lists/arm-kernel/msg568974.html
John Keeping (4):
pinctrl: rockchip: remove unnecessary locking
pinctrl: rockchip: convert to raw spinlock
pinctrl: rockchip: split out verification of mux settings
pinctrl: rockchip: avoid hardirq
version so it's simpler to
apply.
[1] https://www.spinics.net/lists/arm-kernel/msg568974.html
John Keeping (4):
pinctrl: rockchip: remove unnecessary locking
pinctrl: rockchip: convert to raw spinlock
pinctrl: rockchip: split out verification of mux settings
pinctrl: rockchip: avoid hardirq
With real-time preemption, regmap functions cannot be used in the
implementation of irq_chip since they use spinlocks which may sleep.
Move the setting of the mux for IRQs to an irq_bus_sync_unlock handler
where we are allowed to sleep.
Signed-off-by: John Keeping <j...@metanate.com>
Re
With real-time preemption, regmap functions cannot be used in the
implementation of irq_chip since they use spinlocks which may sleep.
Move the setting of the mux for IRQs to an irq_bus_sync_unlock handler
where we are allowed to sleep.
Signed-off-by: John Keeping
Reviewed-by: Heiko Stuebner
On Thu, 16 Mar 2017 11:31:44 +0800, Chris Zhong wrote:
> For RK3399, the phy_cfg_clk is a required clock, if phy_cfg_clk is
> disabled, MIPI phy can not work. Let's return a error if there is no
> phy_cfg_clk in dts property, when the pdata match RK3399.
>
> Signed-off-by: Chris Zhong
On Thu, 16 Mar 2017 11:31:44 +0800, Chris Zhong wrote:
> For RK3399, the phy_cfg_clk is a required clock, if phy_cfg_clk is
> disabled, MIPI phy can not work. Let's return a error if there is no
> phy_cfg_clk in dts property, when the pdata match RK3399.
>
> Signed-off-by: Chris Zhong
> ---
>
regmap_update_bits does its own locking and everything else accessed
here is a local variable so there is no need to lock around it.
Signed-off-by: John Keeping <j...@metanate.com>
Reviewed-by: Heiko Stuebner <he...@sntech.de>
Tested-by: Heiko Stuebner <he...@sntech.de>
---
v2.
regmap_update_bits does its own locking and everything else accessed
here is a local variable so there is no need to lock around it.
Signed-off-by: John Keeping
Reviewed-by: Heiko Stuebner
Tested-by: Heiko Stuebner
---
v2.1:
- Remove RK2928 locking in rockchip_set_pull()
v2:
- Also remove
On Wed, 15 Mar 2017 13:23:09 -0500, Julia Cartwright wrote:
> On Wed, Mar 15, 2017 at 07:16:53PM +0100, Heiko Stuebner wrote:
> > Am Mittwoch, 15. März 2017, 18:08:06 CET schrieb John Keeping:
> > > On Wed, 15 Mar 2017 13:01:37 -0500, Julia Cartwright wrote:
> > > &
On Wed, 15 Mar 2017 13:23:09 -0500, Julia Cartwright wrote:
> On Wed, Mar 15, 2017 at 07:16:53PM +0100, Heiko Stuebner wrote:
> > Am Mittwoch, 15. März 2017, 18:08:06 CET schrieb John Keeping:
> > > On Wed, 15 Mar 2017 13:01:37 -0500, Julia Cartwright wrote:
> > > &
spinlocks are used to avoid sleeping in hardirq context.
[1] https://www.spinics.net/lists/arm-kernel/msg568279.html
John Keeping (4):
pinctrl: rockchip: remove unnecessary locking
pinctrl: rockchip: convert to raw spinlock
pinctrl: rockchip: split out verification of mux settings
pinctrl
spinlocks are used to avoid sleeping in hardirq context.
[1] https://www.spinics.net/lists/arm-kernel/msg568279.html
John Keeping (4):
pinctrl: rockchip: remove unnecessary locking
pinctrl: rockchip: convert to raw spinlock
pinctrl: rockchip: split out verification of mux settings
pinctrl
With real-time preemption, regmap functions cannot be used in the
implementation of irq_chip since they use spinlocks which may sleep.
Move the setting of the mux for IRQs to an irq_bus_sync_unlock handler
where we are allowed to sleep.
Signed-off-by: John Keeping <j...@metanate.com>
Re
regmap_update_bits does its own locking and everything else accessed
here is a local variable so there is no need to lock around it.
Signed-off-by: John Keeping <j...@metanate.com>
Reviewed-by: Heiko Stuebner <he...@sntech.de>
Tested-by: Heiko Stuebner <he...@sntech.de>
---
With real-time preemption, regmap functions cannot be used in the
implementation of irq_chip since they use spinlocks which may sleep.
Move the setting of the mux for IRQs to an irq_bus_sync_unlock handler
where we are allowed to sleep.
Signed-off-by: John Keeping
Reviewed-by: Heiko Stuebner
regmap_update_bits does its own locking and everything else accessed
here is a local variable so there is no need to lock around it.
Signed-off-by: John Keeping
Reviewed-by: Heiko Stuebner
Tested-by: Heiko Stuebner
---
v2:
- Also remove locking in rockchip_set_schmitt()
---
drivers/pinctrl
This lock is used from rockchip_irq_set_type() which is part of the
irq_chip implementation and thus must use raw_spinlock_t as documented
in Documentation/gpio/driver.txt.
Signed-off-by: John Keeping <j...@metanate.com>
Reviewed-by: Heiko Stuebner <he...@sntech.de>
Tested-by: Heiko
This lock is used from rockchip_irq_set_type() which is part of the
irq_chip implementation and thus must use raw_spinlock_t as documented
in Documentation/gpio/driver.txt.
Signed-off-by: John Keeping
Reviewed-by: Heiko Stuebner
Tested-by: Heiko Stuebner
---
v2: unchanged
---
drivers/pinctrl
rockchip_verify_mux() function from there.
Signed-off-by: John Keeping <j...@metanate.com>
Reviewed-by: Heiko Stuebner <he...@sntech.de>
Tested-by: Heiko Stuebner <he...@sntech.de>
---
v2: unchanged
---
drivers/pinctrl/pinctrl-rockchip.c | 46 +---
rockchip_verify_mux() function from there.
Signed-off-by: John Keeping
Reviewed-by: Heiko Stuebner
Tested-by: Heiko Stuebner
---
v2: unchanged
---
drivers/pinctrl/pinctrl-rockchip.c | 46 +-
1 file changed, 30 insertions(+), 16 deletions(-)
diff --git
On Wed, 15 Mar 2017 13:01:37 -0500, Julia Cartwright wrote:
> On Wed, Mar 15, 2017 at 05:46:52PM +0000, John Keeping wrote:
> > This lock is used from rockchip_irq_set_type() which is part of the
> > irq_chip implementation and thus must use raw_spinlock_t as documented
> >
On Wed, 15 Mar 2017 13:01:37 -0500, Julia Cartwright wrote:
> On Wed, Mar 15, 2017 at 05:46:52PM +0000, John Keeping wrote:
> > This lock is used from rockchip_irq_set_type() which is part of the
> > irq_chip implementation and thus must use raw_spinlock_t as documented
> >
On Wed, 15 Mar 2017 17:41:21 +0100, Heiko Stuebner wrote:
> Am Mittwoch, 15. März 2017, 17:28:56 CET schrieb Heiko Stuebner:
> > Am Montag, 13. März 2017, 18:38:11 CET schrieb John Keeping:
> > > This lock is used from rockchip_irq_set_type() which is part of the
> > &
On Wed, 15 Mar 2017 17:41:21 +0100, Heiko Stuebner wrote:
> Am Mittwoch, 15. März 2017, 17:28:56 CET schrieb Heiko Stuebner:
> > Am Montag, 13. März 2017, 18:38:11 CET schrieb John Keeping:
> > > This lock is used from rockchip_irq_set_type() which is part of the
> > &
On Wed, 15 Mar 2017 09:47:29 -0700, Brian Norris wrote:
> On Wed, Mar 15, 2017 at 04:42:31PM +0800, Chris Zhong wrote:
> > For RK3399, the grf clk should be enabled before writing grf registers,
> > otherwise the register value can not be changed.
> >
> > Signed-off-by: Chris Zhong
On Wed, 15 Mar 2017 09:47:29 -0700, Brian Norris wrote:
> On Wed, Mar 15, 2017 at 04:42:31PM +0800, Chris Zhong wrote:
> > For RK3399, the grf clk should be enabled before writing grf registers,
> > otherwise the register value can not be changed.
> >
> > Signed-off-by: Chris Zhong
> > ---
> >
The hci_bcm driver currently does not prepare/unprepare the clock and
goes directly to enable, but as the documentation for clk_enable says,
clk_prepare must be called before clk_enable.
Signed-off-by: John Keeping <j...@metanate.com>
---
drivers/bluetooth/hci_bcm.c | 4 ++--
1 file chan
The hci_bcm driver currently does not prepare/unprepare the clock and
goes directly to enable, but as the documentation for clk_enable says,
clk_prepare must be called before clk_enable.
Signed-off-by: John Keeping
---
drivers/bluetooth/hci_bcm.c | 4 ++--
1 file changed, 2 insertions(+), 2
1 - 100 of 556 matches
Mail list logo
