Hi Song,
On 08/11/2018 01:27 PM, Song Liu wrote:
>> +
>> +static void delayed_uprobe_delete(struct delayed_uprobe *du)
>> +{
>> + if (!du)
>> + return;
> Do we really need this check?
Not necessary though, but I would still like to keep it for a safety.
>
>> +
Hi Song,
On 08/11/2018 01:27 PM, Song Liu wrote:
>> +
>> +static void delayed_uprobe_delete(struct delayed_uprobe *du)
>> +{
>> + if (!du)
>> + return;
> Do we really need this check?
Not necessary though, but I would still like to keep it for a safety.
>
>> +
The compiler predefined macro 'NDS32_ABI_2' had been removed, it should
use the '__NDS32_ABI_2' here.
Signed-off-by: Zong Li
---
arch/nds32/kernel/traps.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/nds32/kernel/traps.c b/arch/nds32/kernel/traps.c
index
The compiler predefined macro 'NDS32_ABI_2' had been removed, it should
use the '__NDS32_ABI_2' here.
Signed-off-by: Zong Li
---
arch/nds32/kernel/traps.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/arch/nds32/kernel/traps.c b/arch/nds32/kernel/traps.c
index
Hi Parthiban,
On Sun, Aug 12, 2018 at 02:22:13PM +0200, Parthiban Nallathambi wrote:
> Actions Semi OWL family SoC's provides support for external interrupt
> controller to be connected and controlled using SIRQ pins. S500, S700
> and S900 provides 3 SIRQ lines and works independently for 3
Hi Parthiban,
On Sun, Aug 12, 2018 at 02:22:13PM +0200, Parthiban Nallathambi wrote:
> Actions Semi OWL family SoC's provides support for external interrupt
> controller to be connected and controlled using SIRQ pins. S500, S700
> and S900 provides 3 SIRQ lines and works independently for 3
Hi Mike,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.18 next-20180810]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Mike,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.18 next-20180810]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On Mon, Aug 13, 2018 at 11:04:10AM +0800, Jia-Ju Bai wrote:
> The kernel may sleep with holding a spinlock.
>
> The function call paths (from bottom to top) in Linux-4.16 are:
>
> [FUNC] schedule_timeout_interruptible
> kernel/rcu/rcutorture.c, 523: schedule_timeout_interruptible in
>
On Mon, Aug 13, 2018 at 11:04:10AM +0800, Jia-Ju Bai wrote:
> The kernel may sleep with holding a spinlock.
>
> The function call paths (from bottom to top) in Linux-4.16 are:
>
> [FUNC] schedule_timeout_interruptible
> kernel/rcu/rcutorture.c, 523: schedule_timeout_interruptible in
>
Hi Mike,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.18 next-20180810]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Mike,
I love your patch! Yet something to improve:
[auto build test ERROR on linus/master]
[also build test ERROR on v4.18 next-20180810]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
The kernel may sleep with holding a spinlock.
The function call paths (from bottom to top) in Linux-4.16 are:
[FUNC] mutex_lock_nested
fs/nfs/write.c, 1045: mutex_lock_nested in nfs_scan_commit_list
fs/nfs/pnfs_nfs.c, 145: nfs_scan_commit_list in
pnfs_generic_recover_commit_reqs
The kernel may sleep with holding a spinlock.
The function call paths (from bottom to top) in Linux-4.16 are:
[FUNC] mutex_lock_nested
fs/nfs/write.c, 1045: mutex_lock_nested in nfs_scan_commit_list
fs/nfs/pnfs_nfs.c, 145: nfs_scan_commit_list in
pnfs_generic_recover_commit_reqs
The kernel may sleep with holding a spinlock.
The function call paths (from bottom to top) in Linux-4.16 are:
[FUNC] schedule_timeout
fs/nfs/nfs4session.c, 223: schedule_timeout in nfs4_slot_wait_on_seqid
fs/nfs/callback_proc.c, 466: nfs4_slot_wait_on_seqid in
referring_call_exists
The kernel may sleep with holding a spinlock.
The function call paths (from bottom to top) in Linux-4.16 are:
[FUNC] schedule_timeout
fs/nfs/nfs4session.c, 223: schedule_timeout in nfs4_slot_wait_on_seqid
fs/nfs/callback_proc.c, 466: nfs4_slot_wait_on_seqid in
referring_call_exists
The page migration code employs try_to_unmap() to try and unmap the
source page. This is accomplished by using rmap_walk to find all
vmas where the page is mapped. This search stops when page mapcount
is zero. For shared PMD huge pages, the page map count is always 1
not matter the number of
The page migration code employs try_to_unmap() to try and unmap the
source page. This is accomplished by using rmap_walk to find all
vmas where the page is mapped. This search stops when page mapcount
is zero. For shared PMD huge pages, the page map count is always 1
not matter the number of
The kernel may sleep with holding a spinlock.
The function call paths (from bottom to top) in Linux-4.16 are:
[FUNC] schedule
fs/inode.c, 1916: schedule in __wait_on_freeing_inode
fs/inode.c, 826: __wait_on_freeing_inode in find_inode_fast
fs/inode.c, 1107: find_inode_fast in iget_locked
The kernel may sleep with holding a spinlock.
The function call paths (from bottom to top) in Linux-4.16 are:
[FUNC] schedule
fs/inode.c, 1916: schedule in __wait_on_freeing_inode
fs/inode.c, 826: __wait_on_freeing_inode in find_inode_fast
fs/inode.c, 1107: find_inode_fast in iget_locked
The kernel may sleep with holding a spin lock.
The function call paths (from bottom to top) in Linux-4.16 are:
[FUNC] kmem_cache_alloc(GFP_KERNEL)
fs/jffs2/malloc.c, 188:
kmem_cache_alloc in jffs2_alloc_refblock
fs/jffs2/malloc.c, 221:
jffs2_alloc_refblock in
The kernel may sleep with holding a spin lock.
The function call paths (from bottom to top) in Linux-4.16 are:
[FUNC] kmem_cache_alloc(GFP_KERNEL)
fs/jffs2/malloc.c, 188:
kmem_cache_alloc in jffs2_alloc_refblock
fs/jffs2/malloc.c, 221:
jffs2_alloc_refblock in
The kernel may sleep with holding a spinlock.
The function call paths (from bottom to top) in Linux-4.16 are:
[FUNC] schedule
fs/dax.c, 259: schedule in get_unlocked_mapping_entry
fs/dax.c, 450: get_unlocked_mapping_entry in __dax_invalidate_mapping_entry
fs/dax.c, 471:
The kernel may sleep with holding a spinlock.
The function call paths (from bottom to top) in Linux-4.16 are:
[FUNC] schedule
fs/dax.c, 259: schedule in get_unlocked_mapping_entry
fs/dax.c, 450: get_unlocked_mapping_entry in __dax_invalidate_mapping_entry
fs/dax.c, 471:
The kernel may sleep with holding a spinlock.
The function call paths (from bottom to top) in Linux-4.16 are:
[FUNC] schedule_timeout_interruptible
kernel/rcu/rcutorture.c, 523: schedule_timeout_interruptible in
srcu_read_delay
kernel/rcu/rcutorture.c, 1105: [FUNC_PTR]srcu_read_delay in
The kernel may sleep with holding a spinlock.
The function call paths (from bottom to top) in Linux-4.16 are:
[FUNC] schedule_timeout_interruptible
kernel/rcu/rcutorture.c, 523: schedule_timeout_interruptible in
srcu_read_delay
kernel/rcu/rcutorture.c, 1105: [FUNC_PTR]srcu_read_delay in
Hi Anson,
> > > -Original Message-
> > > From: Anson Huang
> > > Sent: 2018年8月8日 12:39
> > > To: shawn...@kernel.org; s.ha...@pengutronix.de;
> > > ker...@pengutronix.de; Fabio Estevam ;
> > > mturque...@baylibre.com; sb...@kernel.org;
> > > linux-arm-ker...@lists.infradead.org;
> > >
Hi Anson,
> > > -Original Message-
> > > From: Anson Huang
> > > Sent: 2018年8月8日 12:39
> > > To: shawn...@kernel.org; s.ha...@pengutronix.de;
> > > ker...@pengutronix.de; Fabio Estevam ;
> > > mturque...@baylibre.com; sb...@kernel.org;
> > > linux-arm-ker...@lists.infradead.org;
> > >
I am Vice Chairman of Hang Seng Bank, I have Important Matter to Discuss with
you concerning my late client. Died without a NEXT OF KIN. Send me your private
email for full details information. email me at E-Mail: dray...@gmail.com
Regards
Mr.Fung
I am Vice Chairman of Hang Seng Bank, I have Important Matter to Discuss with
you concerning my late client. Died without a NEXT OF KIN. Send me your private
email for full details information. email me at E-Mail: dray...@gmail.com
Regards
Mr.Fung
From: kbuild test robot
drivers/bluetooth/btmtk.c:86:2-3: Unneeded semicolon
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
Fixes: a52562c05bdf ("Bluetooth: mediatek: Add protocol support for MediaTek
MT7668U USB devices")
CC: Sean Wang
Signed-off-by:
From: kbuild test robot
drivers/bluetooth/btmtk.c:86:2-3: Unneeded semicolon
Remove unneeded semicolon.
Generated by: scripts/coccinelle/misc/semicolon.cocci
Fixes: a52562c05bdf ("Bluetooth: mediatek: Add protocol support for MediaTek
MT7668U USB devices")
CC: Sean Wang
Signed-off-by:
Hi Sean,
I love your patch! Perhaps something to improve:
[auto build test WARNING on bluetooth/master]
[also build test WARNING on v4.18 next-20180810]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
Hi Sean,
I love your patch! Perhaps something to improve:
[auto build test WARNING on bluetooth/master]
[also build test WARNING on v4.18 next-20180810]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
On 2018년 08월 10일 19:11, Greg Kroah-Hartman wrote:
> On Fri, Aug 10, 2018 at 03:43:02PM +0900, Seung-Woo Kim wrote:
>> On 2018년 08월 08일 19:06, Seung-Woo Kim wrote:
>>> On 2018년 07월 05일 09:52, Al Viro wrote:
On Mon, Jul 02, 2018 at 10:01:25PM -0700, Linus Torvalds wrote:
> On Mon, Jul 2,
On 2018년 08월 10일 19:11, Greg Kroah-Hartman wrote:
> On Fri, Aug 10, 2018 at 03:43:02PM +0900, Seung-Woo Kim wrote:
>> On 2018년 08월 08일 19:06, Seung-Woo Kim wrote:
>>> On 2018년 07월 05일 09:52, Al Viro wrote:
On Mon, Jul 02, 2018 at 10:01:25PM -0700, Linus Torvalds wrote:
> On Mon, Jul 2,
On Sun, Aug 12, 2018 at 02:29:28PM +0900, SeongJae Park wrote:
> This commit fixes a couple of typos in README and recipies.txt.
>
> Signed-off-by: SeongJae Park
Good catch on the first "The the"! (Why say it once when you can say
it twice?)
On the second, the quoted output doesn't have a
On Sun, Aug 12, 2018 at 02:29:28PM +0900, SeongJae Park wrote:
> This commit fixes a couple of typos in README and recipies.txt.
>
> Signed-off-by: SeongJae Park
Good catch on the first "The the"! (Why say it once when you can say
it twice?)
On the second, the quoted output doesn't have a
I expected more fs/dcache.c cleanups this cycle, so that went into
a separate branch; said cleanups have missed the window, so in the
hindsight it could've gone into work.misc instead. Decided not
to cherry-pick, thus the separate pull request.
PS: That's the last pull request for today; the
I expected more fs/dcache.c cleanups this cycle, so that went into
a separate branch; said cleanups have missed the window, so in the
hindsight it could've gone into work.misc instead. Decided not
to cherry-pick, thus the separate pull request.
PS: That's the last pull request for today; the
misc cleanups from various folks all over the place
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.misc
for you
misc cleanups from various folks all over the place
The following changes since commit ce397d215ccd07b8ae3f71db689aedb85d56ab40:
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.misc
for you
This time it's pretty much local to fs/aio.c. Hopefully race-free...
The following changes since commit 1ffaddd029c867d134a1dde39f540dcc8c52e274:
Linux 4.18-rc8 (2018-08-05 12:37:41 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git
This time it's pretty much local to fs/aio.c. Hopefully race-free...
The following changes since commit 1ffaddd029c867d134a1dde39f540dcc8c52e274:
Linux 4.18-rc8 (2018-08-05 12:37:41 -0700)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git
should be reasonably complete now - the only leftovers are in ceph.
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.lookup
for you to fetch changes up to
should be reasonably complete now - the only leftovers are in ceph.
Linux 4.18-rc1 (2018-06-17 08:04:49 +0900)
are available in the git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/viro/vfs.git work.lookup
for you to fetch changes up to
* NFS mkdir/open_by_handle race fix
* analogous solution for FUSE, replacing the one currently in mainline
* new primitive to be used when discarding halfway set up inodes on failed
object creation; gives sane warranties re icache lookups not returning
such doomed by still not freed inodes. A
* NFS mkdir/open_by_handle race fix
* analogous solution for FUSE, replacing the one currently in mainline
* new primitive to be used when discarding halfway set up inodes on failed
object creation; gives sane warranties re icache lookups not returning
such doomed by still not freed inodes. A
* "do we need fput() or put_filp()" rules are gone - it's always fput() now.
We keep track of that state where it belongs - in ->f_mode.
* int *opened mess killed - in finish_open(), in ->atomic_open() instances
and in fs/namei.c code around do_last()/lookup_open()/atomic_open().
*
* "do we need fput() or put_filp()" rules are gone - it's always fput() now.
We keep track of that state where it belongs - in ->f_mode.
* int *opened mess killed - in finish_open(), in ->atomic_open() instances
and in fs/namei.c code around do_last()/lookup_open()/atomic_open().
*
Hi Rafael,
I love your patch! Perhaps something to improve:
url:
https://github.com/0day-ci/linux/commits/Rafael-J-Wysocki/cpuidle-menu-Handle-stopped-tick-more-aggressively/20180811-191914
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
linux-next
smatch
Hi Rafael,
I love your patch! Perhaps something to improve:
url:
https://github.com/0day-ci/linux/commits/Rafael-J-Wysocki/cpuidle-menu-Handle-stopped-tick-more-aggressively/20180811-191914
base: https://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git
linux-next
smatch
One week late(r) and here we are - 4.18 is out there.
It was a very calm week, and arguably I could just have released on
schedule last week, but we did have some minor updates. Mostly
networking, but some vfs race fixes (mentioned in the rc8 announment
as "pending") and a couple of driver fixes
One week late(r) and here we are - 4.18 is out there.
It was a very calm week, and arguably I could just have released on
schedule last week, but we did have some minor updates. Mostly
networking, but some vfs race fixes (mentioned in the rc8 announment
as "pending") and a couple of driver fixes
syzbot has found a reproducer for the following crash on:
HEAD commit:4110b42356f3 Add linux-next specific files for 20180810
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=107162c440
kernel config:
syzbot has found a reproducer for the following crash on:
HEAD commit:4110b42356f3 Add linux-next specific files for 20180810
git tree: linux-next
console output: https://syzkaller.appspot.com/x/log.txt?x=107162c440
kernel config:
Hi Jerome,
On Wed, Aug 1, 2018 at 4:00 PM Jerome Brunet wrote:
>
> This patchset is yet another round of update to the amlogic pll driver.
>
> 1) Enable bit is added so we don't rely on the bootloader or the init
> value to enable to pll device.
> 2) Remove unnecessary CLK_GET_RATE_NOCACHE
Hi Jerome,
On Wed, Aug 1, 2018 at 4:00 PM Jerome Brunet wrote:
>
> This patchset is yet another round of update to the amlogic pll driver.
>
> 1) Enable bit is added so we don't rely on the bootloader or the init
> value to enable to pll device.
> 2) Remove unnecessary CLK_GET_RATE_NOCACHE
Hi Heiko:
On 2018年08月10日 04:09, Heiko Stuebner wrote:
> Am Mittwoch, 6. Juli 2016, 10:20:54 CEST schrieb Caesar Wang:
>
>> arch/arm64/boot/dts/rockchip/rk3399.dtsi | 18 ++
>> 1 file changed, 18 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
>>
Hi Heiko:
On 2018年08月10日 04:09, Heiko Stuebner wrote:
> Am Mittwoch, 6. Juli 2016, 10:20:54 CEST schrieb Caesar Wang:
>
>> arch/arm64/boot/dts/rockchip/rk3399.dtsi | 18 ++
>> 1 file changed, 18 insertions(+)
>>
>> diff --git a/arch/arm64/boot/dts/rockchip/rk3399.dtsi
>>
On 08/12/2018 06:23 AM, Willy Tarreau wrote:
> Hi Linus,
>
> please consider applying the attached patch to improve the doc on
> the security reporting process.
>
> Thanks,
> Willy
Hi,
I have a few corrections/comments below.
They can be addressed later if the patch is being merged
On 08/12/2018 06:23 AM, Willy Tarreau wrote:
> Hi Linus,
>
> please consider applying the attached patch to improve the doc on
> the security reporting process.
>
> Thanks,
> Willy
Hi,
I have a few corrections/comments below.
They can be addressed later if the patch is being merged
Since the tick delta is used in multiple places in menu_select(), it's
better to use single one variable to record this value; furthermore, for
more readable we can refactor the code to split a separate function to
making decision for stopping tick, which also needs to use tick delta
value as one
To avoid staying in a shallow state for a long time, the menu governor
relies on not stopping tick when detects the prediction is shorter than
the tick event. This is just luckily to cover most cases but cannot say
it is completely safe. For example, if the prediction is 2000us and the
This patch is only for code refactoring and without functional change.
It introduces a new function menu_decide_stopping_tick(); we can use
this function to focus on making stopping tick decision. With moving
out stopping tick decision code, it lets the below piece code is
simplized only for the
Since the tick delta is used in multiple places in menu_select(), it's
better to use single one variable to record this value; furthermore, for
more readable we can refactor the code to split a separate function to
making decision for stopping tick, which also needs to use tick delta
value as one
To avoid staying in a shallow state for a long time, the menu governor
relies on not stopping tick when detects the prediction is shorter than
the tick event. This is just luckily to cover most cases but cannot say
it is completely safe. For example, if the prediction is 2000us and the
This patch is only for code refactoring and without functional change.
It introduces a new function menu_decide_stopping_tick(); we can use
this function to focus on making stopping tick decision. With moving
out stopping tick decision code, it lets the below piece code is
simplized only for the
We found the CPU cannot stay in deepest idle state as expected with
running synthetic workloads with mainline kernel on Arm platform
(96boards Hikey620 with octa CA53 CPUs).
The main issue is the criteria for decision stopping tick; now
the criteria is checking expected interval is less than
The tick stopping decision is made by comparing the prediction with
TICK_USEC, if the prediction is shorter than TICK_USEC then this means
the CPU is likely waken up before the tick event so it's pointless to
stop tick. In reality when make the decision, though the tick period is
fixed to
The usage for two variables 'data->predicted_us' and 'expected_interval'
in menu_select() are confused, especially these two variables are
assigned with each other: firstly 'data->predicted_us' is assigned to
the minimum value between 'data->predicted_us' and 'expected_interval',
so it presents
The tick stopping decision is made by comparing the prediction with
TICK_USEC, if the prediction is shorter than TICK_USEC then this means
the CPU is likely waken up before the tick event so it's pointless to
stop tick. In reality when make the decision, though the tick period is
fixed to
The usage for two variables 'data->predicted_us' and 'expected_interval'
in menu_select() are confused, especially these two variables are
assigned with each other: firstly 'data->predicted_us' is assigned to
the minimum value between 'data->predicted_us' and 'expected_interval',
so it presents
We found the CPU cannot stay in deepest idle state as expected with
running synthetic workloads with mainline kernel on Arm platform
(96boards Hikey620 with octa CA53 CPUs).
The main issue is the criteria for decision stopping tick; now
the criteria is checking expected interval is less than
On Sun, Aug 12, 2018 at 01:12:41PM +0200, Rafael J. Wysocki wrote:
> On Fri, Aug 10, 2018 at 11:03 AM wrote:
> >
> > On Fri, Aug 10, 2018 at 04:49:06PM +0800, Leo Yan wrote:
> > > On Fri, Aug 10, 2018 at 09:22:10AM +0200, Rafael J. Wysocki wrote:
> > > > On Fri, Aug 10, 2018 at 9:13 AM, wrote:
On Sun, Aug 12, 2018 at 01:12:41PM +0200, Rafael J. Wysocki wrote:
> On Fri, Aug 10, 2018 at 11:03 AM wrote:
> >
> > On Fri, Aug 10, 2018 at 04:49:06PM +0800, Leo Yan wrote:
> > > On Fri, Aug 10, 2018 at 09:22:10AM +0200, Rafael J. Wysocki wrote:
> > > > On Fri, Aug 10, 2018 at 9:13 AM, wrote:
Es ist mir eine Freude, Sie kennenzulernen. Mein Name ist Wesley, ich komme aus
dem Vereinigten Staaten von Amerika. Ich bin ledig und nie verheiratet. Ich
werde mich gerne mit Ihnen bekannt machen, ich entschuldige mich für Ihre
Privatsphäre. Ich hoffe, Sie werden freundlich sein genug, um mir
Es ist mir eine Freude, Sie kennenzulernen. Mein Name ist Wesley, ich komme aus
dem Vereinigten Staaten von Amerika. Ich bin ledig und nie verheiratet. Ich
werde mich gerne mit Ihnen bekannt machen, ich entschuldige mich für Ihre
Privatsphäre. Ich hoffe, Sie werden freundlich sein genug, um mir
> sorry to disturb you all but after one month and a half I never received
> any comment about this patch set and I fear it ended up in a forgotten
> corner. I would like to know if someone is considering it or not.
Adding Peter to CC using his latest EMail address.
Peter, you said you
> sorry to disturb you all but after one month and a half I never received
> any comment about this patch set and I fear it ended up in a forgotten
> corner. I would like to know if someone is considering it or not.
Adding Peter to CC using his latest EMail address.
Peter, you said you
On Fri, Aug 10, 2018 at 01:15:58PM +0200, Rafael J . Wysocki wrote:
> From: Rafael J. Wysocki
>
> Commit 87c9fe6ee495 (cpuidle: menu: Avoid selecting shallow states
> with stopped tick) missed the case when the target residencies of
> deep idle states of CPUs are above the tick boundary which
On Fri, Aug 10, 2018 at 01:15:58PM +0200, Rafael J . Wysocki wrote:
> From: Rafael J. Wysocki
>
> Commit 87c9fe6ee495 (cpuidle: menu: Avoid selecting shallow states
> with stopped tick) missed the case when the target residencies of
> deep idle states of CPUs are above the tick boundary which
Add initial pinctrl driver to support pin configuration with
pinctrl framework for sdm660.
Based off CAF implementation.
Signed-off-by: Craig Tatlor
---
Changes from v1:
Adds gpio-ranges property to bindings
.../bindings/pinctrl/qcom,sdm660-pinctrl.txt | 202 +++
Add initial pinctrl driver to support pin configuration with
pinctrl framework for sdm660.
Based off CAF implementation.
Signed-off-by: Craig Tatlor
---
Changes from v1:
Adds gpio-ranges property to bindings
.../bindings/pinctrl/qcom,sdm660-pinctrl.txt | 202 +++
Initial device tree support for Qualcomm SDM630 SoC and
Sony Pioneer (Xperia XA2).
SDM630 is based off of the SDM660 soc and all SDM660 specific drivers are
compatible with it. SDM660 is also based off of MSM8998 so it uses some
of its drivers aswell.
The device tree is based on the CAF 4.4
Initial device tree support for Qualcomm SDM630 SoC and
Sony Pioneer (Xperia XA2).
SDM630 is based off of the SDM660 soc and all SDM660 specific drivers are
compatible with it. SDM660 is also based off of MSM8998 so it uses some
of its drivers aswell.
The device tree is based on the CAF 4.4
On Sun, Aug 12, 2018 at 12:07:45PM +0200, Rafael J. Wysocki wrote:
[...]
> > > > > --- linux-pm.orig/drivers/cpuidle/governors/menu.c
> > > > > +++ linux-pm/drivers/cpuidle/governors/menu.c
> > > > > @@ -285,9 +285,8 @@ static int menu_select(struct cpuidle_dr
> > > > > {
> > > > > struct
On Sun, Aug 12, 2018 at 12:07:45PM +0200, Rafael J. Wysocki wrote:
[...]
> > > > > --- linux-pm.orig/drivers/cpuidle/governors/menu.c
> > > > > +++ linux-pm/drivers/cpuidle/governors/menu.c
> > > > > @@ -285,9 +285,8 @@ static int menu_select(struct cpuidle_dr
> > > > > {
> > > > > struct
On 11 August 2018 at 08:39, Anand Moon wrote:
> Hi Krzysztof,
>
> These patches should also be ported to u-boot to enable PMIC.
>
> I was just looking into S2MPS11B data sheet
> According to the 1.2 Key Features of S2MPS11
>
> BUCK1, BUCK2, BUCK3, BUCK4, BUCK6 have (0.65 V to 1.6 V) min /max
On 11 August 2018 at 08:39, Anand Moon wrote:
> Hi Krzysztof,
>
> These patches should also be ported to u-boot to enable PMIC.
>
> I was just looking into S2MPS11B data sheet
> According to the 1.2 Key Features of S2MPS11
>
> BUCK1, BUCK2, BUCK3, BUCK4, BUCK6 have (0.65 V to 1.6 V) min /max
Hi Linus,
please consider applying the attached patch to improve the doc on
the security reporting process.
Thanks,
Willy
>From a587418b587915bcaa5657909f52dc3995f29dcd Mon Sep 17 00:00:00 2001
From: Willy Tarreau
Date: Fri, 10 Aug 2018 16:36:04 +0200
Subject: [PATCH] docs: provide more details
Hi Linus,
please consider applying the attached patch to improve the doc on
the security reporting process.
Thanks,
Willy
>From a587418b587915bcaa5657909f52dc3995f29dcd Mon Sep 17 00:00:00 2001
From: Willy Tarreau
Date: Fri, 10 Aug 2018 16:36:04 +0200
Subject: [PATCH] docs: provide more details
On 12 August 2018 13:42:27 BST, Christian Lamparter wrote:
>On Sunday, August 12, 2018 9:18:19 AM CEST you wrote:
>> On 11 August 2018 18:27:43 BST, Christian Lamparter
> wrote:
>> >On Saturday, August 11, 2018 6:25:19 PM CEST Craig Tatlor wrote:
>> >> Add initial pinctrl driver to support pin
On 12 August 2018 13:42:27 BST, Christian Lamparter wrote:
>On Sunday, August 12, 2018 9:18:19 AM CEST you wrote:
>> On 11 August 2018 18:27:43 BST, Christian Lamparter
> wrote:
>> >On Saturday, August 11, 2018 6:25:19 PM CEST Craig Tatlor wrote:
>> >> Add initial pinctrl driver to support pin
On Sunday, August 12, 2018 9:18:19 AM CEST you wrote:
> On 11 August 2018 18:27:43 BST, Christian Lamparter
> wrote:
> >On Saturday, August 11, 2018 6:25:19 PM CEST Craig Tatlor wrote:
> >> Add initial pinctrl driver to support pin configuration with
> >> pinctrl framework for sdm660.
> >> Based
On Sunday, August 12, 2018 9:18:19 AM CEST you wrote:
> On 11 August 2018 18:27:43 BST, Christian Lamparter
> wrote:
> >On Saturday, August 11, 2018 6:25:19 PM CEST Craig Tatlor wrote:
> >> Add initial pinctrl driver to support pin configuration with
> >> pinctrl framework for sdm660.
> >> Based
Add sirq node for Actions Semi S700 SoC with 3 SIRQ pins support,
in which external interrupt controllers can be connected.
Example:
atc260x: atc2603c@65 {
interrupt-parent = <>;
interrupts = <2 IRQ_TYPE_LEVEL_HIGH>;
};
Signed-off-by: Parthiban Nallathambi
Signed-off-by:
Actions Semi Owl family SoC's S500, S700 and S900 provides support
for 3 external interrupt controllers through SIRQ pins.
Each line can be independently configured as interrupt and triggers
on either of the edges (raising or falling) or either of the levels
(high or low) . Each line can also be
This patch series add support for external interrupt controller
in Actions Semi Owl famil of SoC's (S500, S700 and S900). Actions
provides support for external interrupt controller to be connected
with it's SoC's using 3 SIRQ pins.
Each line can be configures independently, i.e 3 independent
Actions Semi Owl family SoC's S500, S700 and S900 provides support
for 3 external interrupt controllers through SIRQ pins.
Each line can be independently configured as interrupt and triggers
on either of the edges (raising or falling) or either of the levels
(high or low) . Each line can also be
1 - 100 of 166 matches
Mail list logo
