On 20.06.2018 21:34, Krzysztof Kozlowski wrote:
> On Tue, Jun 19, 2018 at 09:59:04AM +0200, Krzysztof Kozlowski wrote:
>> On 19 June 2018 at 09:26, Marek Szyprowski wrote:
>>> Hi Krzysztof,
>>>
>>> On 2018-06-18 19:42, Krzysztof Kozlowski wrote:
The decon, decon_tv and dsi nodes have only
On 20.06.2018 21:34, Krzysztof Kozlowski wrote:
> On Tue, Jun 19, 2018 at 09:59:04AM +0200, Krzysztof Kozlowski wrote:
>> On 19 June 2018 at 09:26, Marek Szyprowski wrote:
>>> Hi Krzysztof,
>>>
>>> On 2018-06-18 19:42, Krzysztof Kozlowski wrote:
The decon, decon_tv and dsi nodes have only
On Thu, Jun 21, 2018 at 5:46 AM, Jia-Ju Bai wrote:
> On 2018/6/21 11:38, Matthew Wilcox wrote:
>>
>> On Thu, Jun 21, 2018 at 11:07:14AM +0800, Jia-Ju Bai wrote:
>>>
>>> The kernel may sleep with holding a spinlock.
>>> The function call path (from bottom to top) in Linux-4.16.7 is:
>>>
>>> [FUNC]
On Thu, Jun 21, 2018 at 5:46 AM, Jia-Ju Bai wrote:
> On 2018/6/21 11:38, Matthew Wilcox wrote:
>>
>> On Thu, Jun 21, 2018 at 11:07:14AM +0800, Jia-Ju Bai wrote:
>>>
>>> The kernel may sleep with holding a spinlock.
>>> The function call path (from bottom to top) in Linux-4.16.7 is:
>>>
>>> [FUNC]
On 06/20/18 11:23, Rob Herring wrote:
> On Sun, Jun 17, 2018 at 10:03 AM, wrote:
>> From: Frank Rowand
>>
>> A comment in the review of the patch adding the phandle cache said that
>> the cache would have to be updated when modules are applied and removed.
>> This patch implements the cache
On 06/20/18 11:23, Rob Herring wrote:
> On Sun, Jun 17, 2018 at 10:03 AM, wrote:
>> From: Frank Rowand
>>
>> A comment in the review of the patch adding the phandle cache said that
>> the cache would have to be updated when modules are applied and removed.
>> This patch implements the cache
Hi Pavel,
On Wed, Jun 20, 2018 at 05:27:00PM -0400, Pavel Tatashin wrote:
> We want to get timestamps and high resultion clock available to us as early
> as possible in boot. But, native_sched_clock() outputs time based either on
> tsc after tsc_init() is called later in boot, or using jiffies
Hi Pavel,
On Wed, Jun 20, 2018 at 05:27:00PM -0400, Pavel Tatashin wrote:
> We want to get timestamps and high resultion clock available to us as early
> as possible in boot. But, native_sched_clock() outputs time based either on
> tsc after tsc_init() is called later in boot, or using jiffies
On Wed, Jun 20, 2018 at 09:09:49PM -0700, Randy Dunlap wrote:
> On 06/20/2018 08:15 PM, Tobin C. Harding wrote:
> > On Wed, Jun 20, 2018 at 04:38:05PM -0700, Randy Dunlap wrote:
> >> On 06/20/2018 04:22 PM, Tobin C. Harding wrote:
> >>> On Wed, Jun 20, 2018 at 03:36:44PM -0700, Randy Dunlap wrote:
On Wed, Jun 20, 2018 at 09:09:49PM -0700, Randy Dunlap wrote:
> On 06/20/2018 08:15 PM, Tobin C. Harding wrote:
> > On Wed, Jun 20, 2018 at 04:38:05PM -0700, Randy Dunlap wrote:
> >> On 06/20/2018 04:22 PM, Tobin C. Harding wrote:
> >>> On Wed, Jun 20, 2018 at 03:36:44PM -0700, Randy Dunlap wrote:
* Nishanth Menon [180619 19:46]:
> Hi,
> This is an update from RFC posted earlier:
> https://marc.info/?l=linux-arm-kernel=152817866312732=2
>
> The following series enables support for newest addition in TI's SoC
> portfolio - AM654 SoC.
>
> The series is based off v4.18-rc1, also
* Nishanth Menon [180619 19:46]:
> Hi,
> This is an update from RFC posted earlier:
> https://marc.info/?l=linux-arm-kernel=152817866312732=2
>
> The following series enables support for newest addition in TI's SoC
> portfolio - AM654 SoC.
>
> The series is based off v4.18-rc1, also
* Nishanth Menon [180619 19:46]:
> + cbass_main: cbass@10 {
> + compatible = "simple-bus";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges = <0x0010 0x00 0x0010 0x0002>, /* ctrl mmr */
> +
* Nishanth Menon [180619 19:46]:
> + cbass_main: cbass@10 {
> + compatible = "simple-bus";
> + #address-cells = <1>;
> + #size-cells = <1>;
> + ranges = <0x0010 0x00 0x0010 0x0002>, /* ctrl mmr */
> +
Good day.
Kindly find attached PO 28057 for your reference and action.
Your quick response is highly appreciated.
We wish to get your quotations on confirmation of as attached.
Awaits your urgent responds on confirmation of the above
THANKS & REGARDS ?
Alma Patubo
PROCUREMENT DEPARTMENT
Good day.
Kindly find attached PO 28057 for your reference and action.
Your quick response is highly appreciated.
We wish to get your quotations on confirmation of as attached.
Awaits your urgent responds on confirmation of the above
THANKS & REGARDS ?
Alma Patubo
PROCUREMENT DEPARTMENT
On Wed, 2018-06-20 at 18:24 -0700, Tadeusz Struk wrote:
> On 06/20/2018 04:59 PM, James Bottomley wrote:
> > I'm slightly surprised by this statement. I thought IoT Node.js
> > runtimes (of which there are far too many, so I haven't looked at
> > all of them) use libuv or one of the forks:
> >
>
On Wed, 2018-06-20 at 18:24 -0700, Tadeusz Struk wrote:
> On 06/20/2018 04:59 PM, James Bottomley wrote:
> > I'm slightly surprised by this statement. I thought IoT Node.js
> > runtimes (of which there are far too many, so I haven't looked at
> > all of them) use libuv or one of the forks:
> >
>
On 06/20/2018 07:27 AM, Richard Weinberger wrote:
> Marek,
>
> Am Mittwoch, 20. Juni 2018, 06:52:09 CEST schrieb Marek Vasut:
>> On 06/19/2018 02:07 PM, Richard Weinberger wrote:
>>> The denali NAND flash controller needs at least two clocks to operate,
>>> nand_clk and nand_x_clk.
>>> Since
On 06/20/2018 07:27 AM, Richard Weinberger wrote:
> Marek,
>
> Am Mittwoch, 20. Juni 2018, 06:52:09 CEST schrieb Marek Vasut:
>> On 06/19/2018 02:07 PM, Richard Weinberger wrote:
>>> The denali NAND flash controller needs at least two clocks to operate,
>>> nand_clk and nand_x_clk.
>>> Since
ST/CZ SoC have 2 channels for capture in the I2SSP path.
The DMA though these channels is done using the same dma
descriptors.
We configure the channel and enable it on the basis of
channel selected by machine driver. Machine driver knows
which codec sits on which channel and thus sends the
Hi Sinan,
I love your patch! Perhaps something to improve:
[auto build test WARNING on pci/next]
[also build test WARNING on v4.18-rc1 next-20180620]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
ST/CZ SoC have 2 channels for capture in the I2SSP path.
The DMA though these channels is done using the same dma
descriptors.
We configure the channel and enable it on the basis of
channel selected by machine driver. Machine driver knows
which codec sits on which channel and thus sends the
Hi Sinan,
I love your patch! Perhaps something to improve:
[auto build test WARNING on pci/next]
[also build test WARNING on v4.18-rc1 next-20180620]
[if your patch is applied to the wrong git tree, please drop us a note to help
improve the system]
url:
https://github.com/0day-ci/linux
From: "Agrawal, Akshu"
This is a correction to match acutal hardware configuration.
The hardware configuration looks like:
I2S_BT -> SPK(Max) + DMIC(Adau)
I2S_SP -> DA7219 Headset
No actual products have been shipped with previous configuration.
Signed-off-by: Akshu Agrawal
---
From: "Agrawal, Akshu"
This is a correction to match acutal hardware configuration.
The hardware configuration looks like:
I2S_BT -> SPK(Max) + DMIC(Adau)
I2S_SP -> DA7219 Headset
No actual products have been shipped with previous configuration.
Signed-off-by: Akshu Agrawal
---
On 6/20/2018 7:32 PM, Mark Brown wrote:
> On Thu, Jun 07, 2018 at 02:48:44PM +0800, Akshu Agrawal wrote:
>
>> This patch is dependent on ASoC: AMD: Change codec to channel link as per
>> hardware redesign
>> https://patchwork.kernel.org/patch/10388099/
>
> Can you please send a patch series
On 6/20/2018 7:32 PM, Mark Brown wrote:
> On Thu, Jun 07, 2018 at 02:48:44PM +0800, Akshu Agrawal wrote:
>
>> This patch is dependent on ASoC: AMD: Change codec to channel link as per
>> hardware redesign
>> https://patchwork.kernel.org/patch/10388099/
>
> Can you please send a patch series
Hi Dan,
I agree completely. I was concerned whether the preprocessor definitions in
p80211metadef.h were named according to some convention as there are
many definitions named similarly there.
I am considering renaming this specific definition to "p80211_dot11_keyid",
would that be more
Hi Dan,
I agree completely. I was concerned whether the preprocessor definitions in
p80211metadef.h were named according to some convention as there are
many definitions named similarly there.
I am considering renaming this specific definition to "p80211_dot11_keyid",
would that be more
From: Souptick Joarder
Use new return type vm_fault_t for page_mkwrite
handler.
Signed-off-by: Souptick Joarder
Reviewed-by: Matthew Wilcox
Signed-off-by: Ryusuke Konishi
---
fs/nilfs2/file.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/nilfs2/file.c
From: Souptick Joarder
Use new return type vm_fault_t for page_mkwrite
handler.
Signed-off-by: Souptick Joarder
Reviewed-by: Matthew Wilcox
Signed-off-by: Ryusuke Konishi
---
fs/nilfs2/file.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/fs/nilfs2/file.c
Adding clocks for pcie driver, due to the ASIC design,
the pcie controller re-use part of the mipi clock logic,
so the mipi clock is also required.
Tested-by: Jianxin Qin
Signed-off-by: Yixun Lan
---
drivers/clk/meson/axg.c | 145 +++
Adding clocks for pcie driver, due to the ASIC design,
the pcie controller re-use part of the mipi clock logic,
so the mipi clock is also required.
Tested-by: Jianxin Qin
Signed-off-by: Yixun Lan
---
drivers/clk/meson/axg.c | 145 +++
On Wed, Jun 20, 2018 at 1:35 PM, Nick Dyer wrote:
> The pinctrl settings were incorrect for the touchscreen interrupt line,
> causing
> an interrupt storm. This change has been tested with both the atmel_mxt_ts and
> RMI4 drivers on the RDU1 units.
>
> The value 0x4 comes from the value of
On Wed, Jun 20, 2018 at 1:35 PM, Nick Dyer wrote:
> The pinctrl settings were incorrect for the touchscreen interrupt line,
> causing
> an interrupt storm. This change has been tested with both the atmel_mxt_ts and
> RMI4 drivers on the RDU1 units.
>
> The value 0x4 comes from the value of
Hi all,
Changes since 20180620:
Non-merge commits (relative to Linus' tree): 1541
1590 files changed, 50624 insertions(+), 26914 deletions(-)
I have created today's linux-next tree at
git://git.kernel.org/pub/scm
Hi all,
Changes since 20180620:
Non-merge commits (relative to Linus' tree): 1541
1590 files changed, 50624 insertions(+), 26914 deletions(-)
I have created today's linux-next tree at
git://git.kernel.org/pub/scm
On 06/20/2018 08:15 PM, Tobin C. Harding wrote:
> On Wed, Jun 20, 2018 at 04:38:05PM -0700, Randy Dunlap wrote:
>> On 06/20/2018 04:22 PM, Tobin C. Harding wrote:
>>> On Wed, Jun 20, 2018 at 03:36:44PM -0700, Randy Dunlap wrote:
On 06/20/2018 03:30 PM, Tobin C. Harding wrote:
> On Wed,
On 06/20/2018 08:15 PM, Tobin C. Harding wrote:
> On Wed, Jun 20, 2018 at 04:38:05PM -0700, Randy Dunlap wrote:
>> On 06/20/2018 04:22 PM, Tobin C. Harding wrote:
>>> On Wed, Jun 20, 2018 at 03:36:44PM -0700, Randy Dunlap wrote:
On 06/20/2018 03:30 PM, Tobin C. Harding wrote:
> On Wed,
On 6/21/18 1:01 AM, bseg...@google.com wrote:
> Xunlei Pang writes:
>
>> I noticed the group constantly got throttled even it consumed
>> low cpu usage, this caused some jitters on the response time
>> to some of our business containers enabling cpu quota.
>>
>> It's very simple to reproduce:
>>
On 6/21/18 1:01 AM, bseg...@google.com wrote:
> Xunlei Pang writes:
>
>> I noticed the group constantly got throttled even it consumed
>> low cpu usage, this caused some jitters on the response time
>> to some of our business containers enabling cpu quota.
>>
>> It's very simple to reproduce:
>>
On 2018/6/21 11:43, Al Viro wrote:
On Thu, Jun 21, 2018 at 11:20:59AM +0800, Jia-Ju Bai wrote:
The kernel may sleep with holding a spinlock.
The function call path (from bottom to top) in Linux-4.16.7 is:
[FUNC] vfree --> can sleep
kernel/kcov.c, 237: vfree in kcov_put
kernel/kcov.c, 396:
On 2018/6/21 11:43, Al Viro wrote:
On Thu, Jun 21, 2018 at 11:20:59AM +0800, Jia-Ju Bai wrote:
The kernel may sleep with holding a spinlock.
The function call path (from bottom to top) in Linux-4.16.7 is:
[FUNC] vfree --> can sleep
kernel/kcov.c, 237: vfree in kcov_put
kernel/kcov.c, 396:
On 2018/6/21 11:38, Matthew Wilcox wrote:
On Thu, Jun 21, 2018 at 11:07:14AM +0800, Jia-Ju Bai wrote:
The kernel may sleep with holding a spinlock.
The function call path (from bottom to top) in Linux-4.16.7 is:
[FUNC] remove_element(GFP_KERNEL)
mm/mempool.c, 250: remove_element in
On 2018/6/21 11:38, Matthew Wilcox wrote:
On Thu, Jun 21, 2018 at 11:07:14AM +0800, Jia-Ju Bai wrote:
The kernel may sleep with holding a spinlock.
The function call path (from bottom to top) in Linux-4.16.7 is:
[FUNC] remove_element(GFP_KERNEL)
mm/mempool.c, 250: remove_element in
On Thu, Jun 21, 2018 at 11:20:59AM +0800, Jia-Ju Bai wrote:
> The kernel may sleep with holding a spinlock.
> The function call path (from bottom to top) in Linux-4.16.7 is:
>
> [FUNC] vfree --> can sleep
> kernel/kcov.c, 237: vfree in kcov_put
> kernel/kcov.c, 396: kcov_put in kcov_ioctl_locked
On Thu, Jun 21, 2018 at 11:20:59AM +0800, Jia-Ju Bai wrote:
> The kernel may sleep with holding a spinlock.
> The function call path (from bottom to top) in Linux-4.16.7 is:
>
> [FUNC] vfree --> can sleep
> kernel/kcov.c, 237: vfree in kcov_put
> kernel/kcov.c, 396: kcov_put in kcov_ioctl_locked
On Thu, Jun 21, 2018 at 11:07:14AM +0800, Jia-Ju Bai wrote:
> The kernel may sleep with holding a spinlock.
> The function call path (from bottom to top) in Linux-4.16.7 is:
>
> [FUNC] remove_element(GFP_KERNEL)
> mm/mempool.c, 250: remove_element in mempool_resize
> mm/mempool.c, 247:
On Thu, Jun 21, 2018 at 11:07:14AM +0800, Jia-Ju Bai wrote:
> The kernel may sleep with holding a spinlock.
> The function call path (from bottom to top) in Linux-4.16.7 is:
>
> [FUNC] remove_element(GFP_KERNEL)
> mm/mempool.c, 250: remove_element in mempool_resize
> mm/mempool.c, 247:
On Thu, Jun 21, 2018 at 11:02:58AM +0800, Jia-Ju Bai wrote:
> The kernel may sleep with holding a spinlock.
> The function call path (from bottom to top) in Linux-4.16.7 is:
>
> [FUNC] schedule
> lib/percpu-refcount.c, 222:
> schedule in __percpu_ref_switch_mode
> lib/percpu-refcount.c,
On Thu, Jun 21, 2018 at 11:02:58AM +0800, Jia-Ju Bai wrote:
> The kernel may sleep with holding a spinlock.
> The function call path (from bottom to top) in Linux-4.16.7 is:
>
> [FUNC] schedule
> lib/percpu-refcount.c, 222:
> schedule in __percpu_ref_switch_mode
> lib/percpu-refcount.c,
The kernel may sleep with holding a spinlock.
The function call path (from bottom to top) in Linux-4.16.7 is:
[FUNC] vfree --> can sleep
kernel/kcov.c, 237: vfree in kcov_put
kernel/kcov.c, 396: kcov_put in kcov_ioctl_locked
kernel/kcov.c, 410: kcov_ioctl_locked in kcov_ioctl
kernel/kcov.c, 409:
The kernel may sleep with holding a spinlock.
The function call path (from bottom to top) in Linux-4.16.7 is:
[FUNC] vfree --> can sleep
kernel/kcov.c, 237: vfree in kcov_put
kernel/kcov.c, 396: kcov_put in kcov_ioctl_locked
kernel/kcov.c, 410: kcov_ioctl_locked in kcov_ioctl
kernel/kcov.c, 409:
The kernel may sleep with holding a spinlock.
The function call path (from bottom to top) in Linux-4.16.7 is:
[FUNC] schedule
kernel/locking/rtmutex.c, 1223: schedule in rt_mutex_handle_deadlock
kernel/locking/rtmutex.c, 1273: rt_mutex_handle_deadlock in
rt_mutex_slowlock
The kernel may sleep with holding a spinlock.
The function call path (from bottom to top) in Linux-4.16.7 is:
[FUNC] schedule
kernel/locking/rtmutex.c, 1223: schedule in rt_mutex_handle_deadlock
kernel/locking/rtmutex.c, 1273: rt_mutex_handle_deadlock in
rt_mutex_slowlock
From: Freeman Liu
The Spreadtrum SC27XX PMICs ADC controller contains 32 channels,
which is used to sample voltages with 12 bits conversion.
[Baolin Wang did lots of improvements]
Signed-off-by: Freeman Liu
Signed-off-by: Baolin Wang
---
Changes since v2:
- Remove lock when read/set the
From: Freeman Liu
The Spreadtrum SC27XX PMICs ADC controller contains 32 channels,
which is used to sample voltages with 12 bits conversion.
[Baolin Wang did lots of improvements]
Signed-off-by: Freeman Liu
Signed-off-by: Baolin Wang
---
Changes since v2:
- Remove lock when read/set the
On Wed, Jun 20, 2018 at 04:38:05PM -0700, Randy Dunlap wrote:
> On 06/20/2018 04:22 PM, Tobin C. Harding wrote:
> > On Wed, Jun 20, 2018 at 03:36:44PM -0700, Randy Dunlap wrote:
> >> On 06/20/2018 03:30 PM, Tobin C. Harding wrote:
> >>> On Wed, Jun 20, 2018 at 09:09:49AM -0700, Randy Dunlap wrote:
On Wed, Jun 20, 2018 at 04:38:05PM -0700, Randy Dunlap wrote:
> On 06/20/2018 04:22 PM, Tobin C. Harding wrote:
> > On Wed, Jun 20, 2018 at 03:36:44PM -0700, Randy Dunlap wrote:
> >> On 06/20/2018 03:30 PM, Tobin C. Harding wrote:
> >>> On Wed, Jun 20, 2018 at 09:09:49AM -0700, Randy Dunlap wrote:
This patch adds the binding documentation for Spreadtrum SC27XX series
PMICs ADC controller device.
Signed-off-by: Baolin Wang
Reviewed-by: Rob Herring
---
Changes since v2:
- Add reviewed tag from Rob.
Changes since v1:
- No updates.
---
.../bindings/iio/adc/sprd,sc27xx-adc.txt |
This patch adds the binding documentation for Spreadtrum SC27XX series
PMICs ADC controller device.
Signed-off-by: Baolin Wang
Reviewed-by: Rob Herring
---
Changes since v2:
- Add reviewed tag from Rob.
Changes since v1:
- No updates.
---
.../bindings/iio/adc/sprd,sc27xx-adc.txt |
The kernel may sleep with holding a spinlock.
The function call path (from bottom to top) in Linux-4.16.7 is:
[FUNC] remove_element(GFP_KERNEL)
mm/mempool.c, 250: remove_element in mempool_resize
mm/mempool.c, 247: _raw_spin_lock_irqsave in mempool_resize
To fix this bug, GFP_KERNEL is replaced
The kernel may sleep with holding a spinlock.
The function call path (from bottom to top) in Linux-4.16.7 is:
[FUNC] remove_element(GFP_KERNEL)
mm/mempool.c, 250: remove_element in mempool_resize
mm/mempool.c, 247: _raw_spin_lock_irqsave in mempool_resize
To fix this bug, GFP_KERNEL is replaced
The kernel may sleep with holding a spinlock.
The function call path (from bottom to top) in Linux-4.16.7 is:
[FUNC] schedule
lib/percpu-refcount.c, 222:
schedule in __percpu_ref_switch_mode
lib/percpu-refcount.c, 339:
__percpu_ref_switch_mode in percpu_ref_kill_and_confirm
On Wed, 20 Jun 2018, Dave Mielke wrote:
> [quoted lines by Adam Borowski on 2018/06/21 at 03:43 +0200]
>
> >It's meant for displaying braille to _sighted_ people. And in real world,
> >the main [ab]use is a way to show images that won't get corrupted by
> >proportional fonts. :-þ
>
> It's not
The kernel may sleep with holding a spinlock.
The function call path (from bottom to top) in Linux-4.16.7 is:
[FUNC] schedule
lib/percpu-refcount.c, 222:
schedule in __percpu_ref_switch_mode
lib/percpu-refcount.c, 339:
__percpu_ref_switch_mode in percpu_ref_kill_and_confirm
On Wed, 20 Jun 2018, Dave Mielke wrote:
> [quoted lines by Adam Borowski on 2018/06/21 at 03:43 +0200]
>
> >It's meant for displaying braille to _sighted_ people. And in real world,
> >the main [ab]use is a way to show images that won't get corrupted by
> >proportional fonts. :-þ
>
> It's not
On Thu, 21 Jun 2018, Adam Borowski wrote:
> On Tue, Jun 19, 2018 at 11:34:34AM -0400, Nicolas Pitre wrote:
> > On Tue, 19 Jun 2018, Adam Borowski wrote:
> > > Thus, it'd be nice to use the structure you add to implement full Unicode
> > > range for the vast majority of people. This includes even
On Thu, 21 Jun 2018, Adam Borowski wrote:
> On Tue, Jun 19, 2018 at 11:34:34AM -0400, Nicolas Pitre wrote:
> > On Tue, 19 Jun 2018, Adam Borowski wrote:
> > > Thus, it'd be nice to use the structure you add to implement full Unicode
> > > range for the vast majority of people. This includes even
This patch removes redudant check of PLL ID. struct uniphier_aio_pll
enable member has already been checked at is_valid_pll().
Signed-off-by: Katsuhiro Suzuki
---
Changes from v1:
- Remove unused variable 'dev'
---
sound/soc/uniphier/aio-cpu.c | 5 -
1 file changed, 5 deletions(-)
This patch removes redudant check of PLL ID. struct uniphier_aio_pll
enable member has already been checked at is_valid_pll().
Signed-off-by: Katsuhiro Suzuki
---
Changes from v1:
- Remove unused variable 'dev'
---
sound/soc/uniphier/aio-cpu.c | 5 -
1 file changed, 5 deletions(-)
From: Honghui Zhang
The MTCMOS of PCIe Host for MT2712 will be off when system suspend, and all
the internal control register will be reset after system resume. The PCIe
link should be re-established and the related control register values
should be re-set after system resume.
Signed-off-by:
From: Honghui Zhang
The MTCMOS of PCIe Host for MT2712 will be off when system suspend, and all
the internal control register will be reset after system resume. The PCIe
link should be re-established and the related control register values
should be re-set after system resume.
Signed-off-by:
Hello,
I got mistake (forget to remove unused variable).
I'll send v2. Sorry for confusing.
Regards,
--
Katsuhiro Suzuki
> -Original Message-
> From: Katsuhiro Suzuki
> Sent: Thursday, June 21, 2018 11:44 AM
> To: Mark Brown ; alsa-de...@alsa-project.org
> Cc: Masami Hiramatsu ; Jassi
Hello,
I got mistake (forget to remove unused variable).
I'll send v2. Sorry for confusing.
Regards,
--
Katsuhiro Suzuki
> -Original Message-
> From: Katsuhiro Suzuki
> Sent: Thursday, June 21, 2018 11:44 AM
> To: Mark Brown ; alsa-de...@alsa-project.org
> Cc: Masami Hiramatsu ; Jassi
Hi Ard,
On Wed, Jun 20, 2018 at 12:09:49PM +0200, Ard Biesheuvel wrote:
> On 20 June 2018 at 10:57, Jun Yao wrote:
> > Move {idmap_pg_dir,tramp_pg_dir,swapper_pg_dir} to .rodata
> > section. And update the swapper_pg_dir by fixmap.
> >
>
> I think we may be able to get away with not mapping
Hi Ard,
On Wed, Jun 20, 2018 at 12:09:49PM +0200, Ard Biesheuvel wrote:
> On 20 June 2018 at 10:57, Jun Yao wrote:
> > Move {idmap_pg_dir,tramp_pg_dir,swapper_pg_dir} to .rodata
> > section. And update the swapper_pg_dir by fixmap.
> >
>
> I think we may be able to get away with not mapping
This patch removes redudant check of PLL ID. struct uniphier_aio_pll
enable member has already been checked at is_valid_pll().
Signed-off-by: Katsuhiro Suzuki
---
sound/soc/uniphier/aio-cpu.c | 4
1 file changed, 4 deletions(-)
diff --git a/sound/soc/uniphier/aio-cpu.c
On 06/20/2018 01:03 AM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Earlier I sent the first patch as a solution to a regression introduced
> during the v4.16 merge window, but after testing David's common clock
> series on top of 4.18-rc1 + this patch it turned out that the
This patch removes redudant check of PLL ID. struct uniphier_aio_pll
enable member has already been checked at is_valid_pll().
Signed-off-by: Katsuhiro Suzuki
---
sound/soc/uniphier/aio-cpu.c | 4
1 file changed, 4 deletions(-)
diff --git a/sound/soc/uniphier/aio-cpu.c
On 06/20/2018 01:03 AM, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Earlier I sent the first patch as a solution to a regression introduced
> during the v4.16 merge window, but after testing David's common clock
> series on top of 4.18-rc1 + this patch it turned out that the
On Fri, Jun 1, 2018 at 8:54 AM wrote:
>
> From: Oscar Salvador
>
> Callers of register_mem_sect_under_node() are always passing a valid
> memory_block (not NULL), so we can safely drop the check for NULL.
>
> In the same way, register_mem_sect_under_node() is only called in case
> the node is
On Fri, Jun 1, 2018 at 8:54 AM wrote:
>
> From: Oscar Salvador
>
> Callers of register_mem_sect_under_node() are always passing a valid
> memory_block (not NULL), so we can safely drop the check for NULL.
>
> In the same way, register_mem_sect_under_node() is only called in case
> the node is
On Fri, Jun 1, 2018 at 8:54 AM wrote:
>
> From: Oscar Salvador
>
> link_mem_sections() and walk_memory_range() share most of the code,
> so we can use walk_memory_range() with a callback to
> register_mem_sect_under_node()
> instead of using link_mem_sections().
Yes, their logic is indeed
On Fri, Jun 1, 2018 at 8:54 AM wrote:
>
> From: Oscar Salvador
>
> link_mem_sections() and walk_memory_range() share most of the code,
> so we can use walk_memory_range() with a callback to
> register_mem_sect_under_node()
> instead of using link_mem_sections().
Yes, their logic is indeed
On Thu, Jun 21, 2018 at 4:39 AM, Yisheng Xie wrote:
> match_string() returns the index of an array for a matching string,
> which can be used instead of open coded variant.
>
> As Andy's suggestion, this patch add string literal instead of NULL
> for crypto in array of hwcaps and make an
On Thu, Jun 21, 2018 at 4:39 AM, Yisheng Xie wrote:
> match_string() returns the index of an array for a matching string,
> which can be used instead of open coded variant.
>
> As Andy's suggestion, this patch add string literal instead of NULL
> for crypto in array of hwcaps and make an
[quoted lines by Adam Borowski on 2018/06/21 at 03:43 +0200]
>It's meant for displaying braille to _sighted_ people. And in real world,
>the main [ab]use is a way to show images that won't get corrupted by
>proportional fonts. :-þ
It's not abuse at all. I often use U+28xx to show sighted people
[quoted lines by Adam Borowski on 2018/06/21 at 03:43 +0200]
>It's meant for displaying braille to _sighted_ people. And in real world,
>the main [ab]use is a way to show images that won't get corrupted by
>proportional fonts. :-þ
It's not abuse at all. I often use U+28xx to show sighted people
Hi Boaz,
Could you have a look at this trivial patch?
Thanks,
Chengguang.
On 06/13/2018 12:05 PM, Chengguang Xu wrote:
There are some cases can cause memory leak when parsing
option 'osdname'.
Signed-off-by: Chengguang Xu
---
fs/exofs/super.c | 5 -
1 file changed, 4 insertions(+), 1
Hi Boaz,
Could you have a look at this trivial patch?
Thanks,
Chengguang.
On 06/13/2018 12:05 PM, Chengguang Xu wrote:
There are some cases can cause memory leak when parsing
option 'osdname'.
Signed-off-by: Chengguang Xu
---
fs/exofs/super.c | 5 -
1 file changed, 4 insertions(+), 1
On Fri, Jun 1, 2018 at 8:54 AM wrote:
>
> From: Oscar Salvador
>
> When hotpluging memory, it is possible that two calls are being made
> to register_mem_sect_under_node().
> One comes from __add_section()->hotplug_memory_register()
> and the other from add_memory_resource()->link_mem_sections()
On Fri, Jun 1, 2018 at 8:54 AM wrote:
>
> From: Oscar Salvador
>
> When hotpluging memory, it is possible that two calls are being made
> to register_mem_sect_under_node().
> One comes from __add_section()->hotplug_memory_register()
> and the other from add_memory_resource()->link_mem_sections()
Fix a typo, use 'm' instead of 'ns->mq_mnt'.
Fixes: 5cd6a50ace05 ("ipc: Convert mqueue fs to fs_context")
Signed-off-by: Wei Yongjun
---
ipc/mqueue.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ipc/mqueue.c b/ipc/mqueue.c
index 833b8d7..0f10221 100644
--- a/ipc/mqueue.c
Fix a typo, use 'm' instead of 'ns->mq_mnt'.
Fixes: 5cd6a50ace05 ("ipc: Convert mqueue fs to fs_context")
Signed-off-by: Wei Yongjun
---
ipc/mqueue.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/ipc/mqueue.c b/ipc/mqueue.c
index 833b8d7..0f10221 100644
--- a/ipc/mqueue.c
Commit ab8f58ad72c4 ("PM / devfreq: Set min/max_freq when adding
the devfreq device") introduced the initialization of the user
limits min/max_freq from the lowest/highest available OPPs. Later
commit f1d981eaecf8 ("PM / devfreq: Use the available min/max
frequency") added scaling_min/max_freq,
Commit ab8f58ad72c4 ("PM / devfreq: Set min/max_freq when adding
the devfreq device") introduced the initialization of the user
limits min/max_freq from the lowest/highest available OPPs. Later
commit f1d981eaecf8 ("PM / devfreq: Use the available min/max
frequency") added scaling_min/max_freq,
cpufreq stubs out some functions when CONFIG_CPU_FREQ=n , but
cpufreq_update_policy() is not among them. The throttler driver
(https://patchwork.kernel.org/patch/10453351/) uses cpufreq as one
possible throttling mechanism, but it can still be useful without
cpufreq. Stubbing out
This series adds the throttler driver, for non-thermal throttling of
CPUs and devfreq devices. A use case for non-thermal throttling could
be the detection of a high battery discharge voltage, close to the
over-current protection (OCP) limit of the battery.
To support throttling of devfreq
1 - 100 of 1490 matches
Mail list logo
