> From: Raj, Ashok
> Sent: Monday, November 9, 2020 7:59 AM
>
> Hi Thomas,
>
> [-] Jing, She isn't working at Intel anymore.
>
> Now this is getting compiled as a book :-).. Thanks a ton!
>
> One question on the hypercall case that isn't immediately
> clear to me.
>
> On Sun, Nov 08, 2020 at
This patch adds code to handle the active scan during interleave
scan. The interleave scan will be canceled when users start active scan,
and it will be restarted after active scan stopped.
Signed-off-by: Howard Chung
Reviewed-by: Alain Michaud
Reviewed-by: Manish Mandlik
---
(no changes
This adds support of variable length parameter in mgmt_config.
Signed-off-by: Howard Chung
---
(no changes since v1)
net/bluetooth/mgmt_config.c | 140 +---
1 file changed, 84 insertions(+), 56 deletions(-)
diff --git a/net/bluetooth/mgmt_config.c
This patch add a configurable parameter to switch off the interleave
scan feature.
Reviewed-by: Alain Michaud
Signed-off-by: Howard Chung
---
Changes in v7:
- Fix bt_dev_warn arguemnt type warning
Changes in v6:
- Set EnableAdvMonInterleaveScan to 1 byte long
Changes in v4:
- Set
This patch implements the interleaving between allowlist scan and
no-filter scan. It'll be used to save power when at least one monitor is
registered and at least one pending connection or one device to be
scanned for.
The durations of the allowlist scan and the no-filter scan are
controlled by
This patch adds code to handle the system suspension during interleave
scan. The interleave scan will be canceled when the system is going to
sleep, and will be restarted after waking up.
Commit-changes 5:
- Remove the change in hci_req_config_le_suspend_scan
Signed-off-by: Howard Chung
We can get hwirq number of the gpio by its irq_data->hwirq so that we don't
need to add more macros for different platforms. This patch is tested in
SiFive Unleashed board and SiFive Unmatched board.
Signed-off-by: Greentime Hu
---
drivers/gpio/gpio-sifive.c | 12
1 file changed, 8
On Mon, Nov 09, 2020 at 08:54:13AM +0200, Amit Klein wrote:
> Unfortunately, I'm just a security researcher, not a kernel developer...
>
> Does that mean you don't plan to back-port the patch?
I could possibly have a look, but quite frankly I'm not convinced that we
need to backport this at all.
Hi Masahiro,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f8394f232b1eab649ce2df5c5f15b0e528c92091
commit: def2fbffe62c00c330c7f41584a356001179c59c kconfig: allow symbols implied
by y to become m
date: 8
On 11/8/20 11:45 PM, John Hubbard wrote:
> On 11/8/20 12:37 AM, Barry Song wrote:
>> Without DEBUG_FS, all the code in gup_test becomes meaningless. For sure
>> kernel provides debugfs stub while DEBUG_FS is disabled, but the point
>> here is that GUP_TEST can do nothing without DEBUG_FS.
>>
>>
On Mon 09-11-20 13:54:59, Neil Brown wrote:
>
> If a worker task for a normal (bound, non-CPU-intensive) calls
> cond_resched(), this allows other non-workqueue processes to run, but
> does *not* allow other workqueue workers to run. This is because
> workqueue will only attempt to run one task
On 06/11/2020 23.46, Nishanth Menon wrote:
> On 13:32-20201106, Peter Ujfalusi wrote:
> [...]
>>>
> default power management functionality etc
Right, so how does that helps with devices present in the SoC, but no
node at all? First thing which comes to mind is AASRC, we
Hi Rijo,
On Wed, Nov 4, 2020 at 7:26 AM Rijo Thomas wrote:
>
> AMD-TEE driver keeps track of shared memory buffers and their
> corresponding buffer id's in a global linked list. These buffers are
> used to share data between x86 and AMD Secure Processor. This patchset
> fixes issues related to
On 11/8/20 12:37 AM, Barry Song wrote:
Without DEBUG_FS, all the code in gup_test becomes meaningless. For sure
kernel provides debugfs stub while DEBUG_FS is disabled, but the point
here is that GUP_TEST can do nothing without DEBUG_FS.
Cc: John Hubbard
Cc: Ralph Campbell
Cc: Randy Dunlap
Atish Patra 於 2020年9月18日 週五 上午6:37寫道：
>
> From: Anup Patel
>
> Currently, RISC-V reserves 1MB of fixmap memory for device tree. However,
> it maps only single PMD (2MB) space for fixmap which leaves only < 1MB space
> left for other kernel features such as early ioremap which requires fixmap
>
On Sun, Nov 08, 2020 at 09:35:38AM -0800, Linus Torvalds wrote:
> So while we try to mark scripts executable, we then actually generally
> execute them using an explicit interpreter invocation anyway (ie using
>
> $(CONFIG_SHELL) "some-script-path"
>
> or similar).
Thanks for explaining!
--
On Mon, 9 Nov 2020 at 01:19, Nathan Chancellor wrote:
>
> Patch "treewide: Remove stringification from __alias macro definition"
> causes arguments to __alias to no longer be quoted automatically, which
> breaks CONFIG_KASAN on ARM after commit d6d51a96c7d6 ("ARM: 9014/2:
> Replace string mem*
On Fri 06-11-20 12:32:38, Minchan Kim wrote:
> It's hard to have some tests to be supposed to work under heavy
> memory pressure(e.g., injecting some memory hogger) because
> out-of-memory killer easily kicks out one of processes so system
> is broken or system loses the memory pressure state
> From: Jason Gunthorpe
> Sent: Monday, November 9, 2020 7:24 AM
>
> On Sun, Nov 08, 2020 at 07:47:24PM +0100, Thomas Gleixner wrote:
> >
> > That means the guest needs a way to ask the hypervisor for a proper
> > translation, i.e. a hypercall. Now where to do that? Looking at the
> > above
On Sun, Nov 08, 2020 at 11:37:38PM +0100, Rikard Falkeborn wrote:
> The only usage of dsi_host_ops is to assign its address to the ops field
> in the mipi_dsi_host struct, which is a const pointer. Make it const to
> allow the compiler to put it in read-only memory.
>
> Signed-off-by: Rikard
Hi Alex,
On Sun, Nov 08, 2020 at 04:01:59PM +0800, Alex Shi wrote:
> Couple of variables are actually useless, remove them to save some gcc
> warning:
> drivers/video/fbdev/riva/riva_hw.c:250:21: warning: variable ‘mlwm’ set
> but not used [-Wunused-but-set-variable]
>
From: "xiao.ma"
The driver supports Q54SJ108A2 series modules of Delta.
Standard attributes are in the sysfs, and other attributes are in the debugfs.
Signed-off-by: xiao.ma
---
Notes:
Patch v2 changelog:
Add delta.rst in Documentation/hwmon.
Tristate "DELTA" in Kconfig is
On Tue, 3 Nov 2020 at 09:43, Dmitry Osipenko wrote:
>
> 03.11.2020 10:24, Ard Biesheuvel пишет:
> > Still broken today
> >
> > https://kernelci.org/build/id/5fa0c1a74bdb1ea4063fe7e4/
> >
Still broken today
https://kernelci.org/build/id/5fa898baa00b5f3167db8857/
> > So the options are
> >
> >
On 9/11/20 1:27 am, Joe Perches wrote:
> On Sun, 2020-11-08 at 19:13 +0530, Aditya Srivastava wrote:
>> Currently, checkpatch warns us if the author of the commit signs-off
>> as co-developed-by.
> []
>> A quick manual check found out that all fixes were correct in those
>> cases.
> []
>> diff
Hi Yang,
Thank you for the patch! Perhaps something to improve:
[auto build test WARNING on tip/master]
[also build test WARNING on linus/master v5.10-rc3 next-20201106]
[cannot apply to vhost/linux-next kvm/linux-next linux/master]
[If your patch is applied to the wrong git tree, kindly drop us
Hi Olaf.
On Fri, Nov 06, 2020 at 07:39:41PM +0100, Olaf Hering wrote:
> hvfb_getmem uses vzalloc, therefore vmalloc.h should be included.
>
> Fixes commit d21987d709e807ba7bbf47044deb56a3c02e8be4 ("video: hyperv:
> hyperv_fb: Support deferred IO for Hyper-V frame buffer driver")
>
>
Hi all,
Changes since 20201106:
The drivers-memory tree gained a build failure for which I applied
a patch.
The mfd tree lost its build failure.
The tip tree gained conflicts against the block tree.
The akpm-current tree gained a conflict against the tip tree.
Non-merge commits (relative to
Hi Stephen
On Fri, Nov 06, 2020 at 10:23:33AM -0800, Stephen Boyd wrote:
> Reading the EDID of this panel shows that these flags should be set. Set
> them so that we match what is in the EDID.
>
> Cc: Douglas Anderson
> Cc: Bjorn Andersson
> Fixes: b0c664cc80e8 ("panel: simple: Add BOE
make clang-analyzer caught my attention with:
kernel/sysctl.c:1511:4: warning: Value stored to 'first' is never read \
[clang-analyzer-deadcode.DeadStores]
first = 0;
^
Commit 9f977fb7ae9d ("sysctl: add proc_do_large_bitmap") introduced
On 05-11-20, 12:55, Ionela Voinescu wrote:
> For errors parsing the _PSD domains, a separate domain is returned for
> each CPU in the failed _PSD domain with no coordination (as per previous
> comment). But contrary to the intention, the code was setting
> CPUFREQ_SHARED_TYPE_ALL as coordination
On 05-11-20, 12:55, Ionela Voinescu wrote:
> Use the existing sysfs attribute "freqdomain_cpus" to expose
> information to userspace about CPUs in the same frequency domain.
>
> Signed-off-by: Ionela Voinescu
> Cc: Rafael J. Wysocki
> Cc: Viresh Kumar
> ---
>
On 2020/11/8 16:20, Tariq Toukan wrote:
>
>
> On 11/7/2020 8:53 AM, xiakaixu1...@gmail.com wrote:
>> From: Kaixu Xia
>>
>> Fix the following coccinelle warnings:
>>
>
> Hi Kaixu,
>
> Which coccinelle version gave this warning?
Hi Tariq,
The version is coccinelle-1.0.7.
Thanks,
Kaixu
>
On 05-11-20, 12:55, Ionela Voinescu wrote:
> The previous coordination type handling in the cppc_cpufreq init code
> created some confusion: the comment mentioned "Support only SW_ANY for
> now" while only the SW_ALL/ALL case resulted in a failure. The other
> coordination types (HW_ALL/HW, NONE)
On 05-11-20, 12:55, Ionela Voinescu wrote:
> Considering only the currently supported coordination types (ANY, HW,
> NONE), this change only makes a difference for the ANY type, when
> policy->cpu is hotplugged out. In that case the new policy->cpu will
> be different from ((struct cppc_cpudata
From: Menglong Dong
Some typos are found out by misspell-fixer tool:
$ misspell-fixer -rnv ./net/sched/
./net/sched/act_api.c:686
./net/sched/act_bpf.c:68
./net/sched/cls_rsvp.h:241
./net/sched/em_cmp.c:44
./net/sched/sch_pie.c:408
Fix typos found by misspell-fixer.
Signed-off-by: Menglong
On 05-11-20, 12:55, Ionela Voinescu wrote:
> The CPPC performance capabilities are used significantly throughout
> the driver. Simplify the use of them by introducing a local pointer
> "caps" to point to cpu_data->perf_caps, in functions that access
> performance capabilities often.
>
>
progfd is created by prog_parse_fd(), before 'bpftool net attach' exit,
it should be closed.
Fixes: 04949ccc273e ("tools: bpftool: add net attach command to attach XDP on
interface")
Signed-off-by: Wang Hai
---
tools/bpf/bpftool/net.c | 2 ++
1 file changed, 2 insertions(+)
diff --git
On 05-11-20, 12:55, Ionela Voinescu wrote:
> In order to maintain the typical naming convention in the cpufreq
> framework:
> - replace the use of "cpu" variable name for cppc_cpudata pointers
>with "cpu_data"
> - replace variable names "cpu_num" and "cpunum" with "cpu"
> - make cpu
On 05-11-20, 12:55, Ionela Voinescu wrote:
> Fix a few trivial issues in the cppc_cpufreq driver:
>
> - indentation of function arguments
> - consistent use of tabs (vs space) in defines
> - spelling: s/Offest/Offset, s/trasition/transition
> - order of local variables, from long pointers to
On 06-11-20, 11:14, Lukasz Luba wrote:
> I also had similar doubts, because if we make frequency requests
> independently for each CPU, why not having N cooling devs, which
> will set independently QoS max freq for them...
>
> What convinced me:
> EAS and FIE would know the 'real' frequency of
This fixes a regression for blocking connects introduced by commit
4becb7ee5b3d ("net/x25: Fix x25_neigh refcnt leak when x25 disconnect").
The x25->neighbour is already set to "NULL" by x25_disconnect() now,
while a blocking connect is waiting in
x25_wait_for_connection_establishment().
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f8394f232b1eab649ce2df5c5f15b0e528c92091
commit: e5fc436f06eef54ef512ea55a9db8eb9f2e76959 sparse: use static inline for
__chk_{user,io}_ptr()
date: 2 months ago
config: sh-randconfig-s032-20201103
menglong8.dong@ wrote:
> From: Menglong Dong
>
> Obviously, 'bpf/bpf.h' in 'samples/bpf/hbm.c' is duplicated.
>
> Signed-off-by: Menglong Dong
> ---
Acked-by: John Fastabend
On 07/11/20 3:36 pm, Marco Elver wrote:
> On Sat, 7 Nov 2020 at 05:58, David Gow wrote:
>> On Sat, Nov 7, 2020 at 3:22 AM Arpitha Raghunandan <98.a...@gmail.com> wrote:
>>>
>>> Implementation of support for parameterized testing in KUnit.
>>> This approach requires the creation of a test case
On Fri, Nov 6, 2020 at 3:17 PM Guenter Roeck wrote:
>
> On Fri, Nov 06, 2020 at 12:18:25PM +0200, Alexandru Ardelean wrote:
> > The sense resistor is a parameter of the board. It should be configured in
> > the driver via a device-tree / ACPI property, so that the proper current
> > measurements
Hi Alex,
On Fri, Nov 6, 2020 at 8:42 AM Alex Williamson
wrote:
>
> On Fri, 6 Nov 2020 08:24:26 +0530
> Vikas Gupta wrote:
>
> > Hi Alex,
> >
> > On Thu, Nov 5, 2020 at 12:38 PM Alex Williamson
> > wrote:
> > >
> > > On Thu, 5 Nov 2020 11:32:55 +0530
> > > Vikas Gupta wrote:
> > >
> > > >
On Fri, Nov 6, 2020 at 3:14 PM Guenter Roeck wrote:
>
> On Fri, Nov 06, 2020 at 12:18:24PM +0200, Alexandru Ardelean wrote:
> > In order to account for any potential overflows that could occur.
> >
> > Signed-off-by: Alexandru Ardelean
> > ---
> > drivers/hwmon/ltc2945.c | 14 +++---
> >
On Wed, Nov 04, 2020 at 04:24:22PM +, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> In file included from drivers/input/touchscreen/cyttsp_i2c_common.c:24:
> drivers/input/touchscreen/cyttsp4_core.h:236:27: warning:
> ‘cyttsp4_tch_abs_string’ defined but not used
On Mon, Nov 09, 2020 at 02:03:11AM +, Tim Li wrote:
> This email and any attachments thereto may contain private, confidential, and
> privileged material for the sole use of the intended recipient. Any review,
> copying, or distribution of this email (or any attachments thereto) by others
>
On Sat, Jun 13, 2020 at 04:09:46PM +0800, Like Xu wrote:
> From: Wei Wang
>
> The MSR variable type can be 'unsigned int', which uses less memory than
> the longer 'unsigned long'. Fix 'struct x86_pmu' for that. The lbr_nr won't
> be a negative number, so make it 'unsigned int' as well.
Hi,
On Wed, Nov 04, 2020 at 04:24:16PM +, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/input/touchscreen/resistive-adc-touch.c:34: warning: cannot
> understand function prototype: 'struct grts_state '
>
> Cc: Eugen Hristev
> Cc: Dmitry Torokhov
> Cc:
On Wed, Nov 04, 2020 at 04:24:10PM +, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/input/mouse/cyapa_gen5.c:392: warning: Function parameter or member
> 'cyapa' not described in 'cyapa_i2c_pip_write'
> drivers/input/mouse/cyapa_gen5.c:392: warning:
On Wed, Nov 04, 2020 at 04:24:11PM +, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/input/misc/ab8500-ponkey.c:32: warning: Function parameter or member
> 'idev' not described in 'ab8500_ponkey'
>
> Cc: Dmitry Torokhov
> Cc: Sundar Iyer
> Cc:
On Wed, Nov 04, 2020 at 04:24:09PM +, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/input/mouse/cyapa.c:130: warning: Function parameter or member 'reg'
> not described in 'cyapa_i2c_write'
> drivers/input/mouse/cyapa.c:130: warning: Excess function
From: Jeevan Shriram
Add initial Qualcomm SDX55 pinctrl driver to support pin configuration
with pinctrl framewor for SDX55 SoC.
Signed-off-by: Jeevan Shriram
Reviewed-by: Bjorn Andersson
[ported from downstream and tidy up]
Signed-off-by: Vinod Koul
---
drivers/pinctrl/qcom/Kconfig
Add device tree binding Documentation details for Qualcomm SDX55
pinctrl driver.
Reviewed-by: Bjorn Andersson
Signed-off-by: Vinod Koul
---
.../bindings/pinctrl/qcom,sdx55-pinctrl.yaml | 154 ++
1 file changed, 154 insertions(+)
create mode 100644
On Wed, Nov 04, 2020 at 04:24:19PM +, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/input/mouse/elantech.c:1837: warning: Function parameter or member
> 'psmouse' not described in 'elantech_setup_smbus'
> drivers/input/mouse/elantech.c:1837: warning:
This series add device tree binding documentation and driver for SDX55 SOC
pincontroller.
Changes in v3:
- Add ack by Bjorn
- Fix dt_binding_check errors
- Add gpio ranges in binding
Changes in v2:
- merge the functional groups together
- move pins to single line for readability
Jeevan
On Wed, Nov 04, 2020 at 04:24:18PM +, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/input/keyboard/gpio_keys.c:119: warning: Function parameter or
> member 'dev' not described in 'get_bm_events_by_type'
> drivers/input/keyboard/gpio_keys.c:119: warning:
On Mon, Nov 09, 2020 at 11:40:08AM +0800, Wang Qing wrote:
> Add PREEMPT_RT output to die().
That says what you did, but not why you are doing this.
Why are you doing this? That needs to go into the changelog text.
greg k-h
This option adds support for a testing cpuidle driver, which allows
user to define custom idle states with their respective latencies and
residencies. This is useful for testing the behaviour of governors on
customized set of idle states.
This can be used as of now by specifying a customized set
On Mon, Nov 09, 2020 at 07:16:25AM +0200, Amit Klein wrote:
> Dear all
>
> Quick question: what's the plan for back-porting this security patch to LTS
> branches?
If you have working and tested backports, to older kernels, I'll be glad
to accept them if you think they are needed.
thanks,
greg
On Wed, Nov 04, 2020 at 04:24:26PM +, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/input/keyboard/nomadik-ske-keypad.c:71: warning: Function parameter
> or member 'pclk' not described in 'ske_keypad'
> drivers/input/keyboard/nomadik-ske-keypad.c:71:
Hi, everybody:
How do we deal with this problem? I updated the kernel to the latest and the
problem still persists.
make ARCH=arm64 CROSS_COMPILE=aarch64-linux-gnu- -j24 dtbs 2>err.txt
vim err.txt
arch/arm64/boot/dts/qcom/ipq6018.dtsi:185.3-14: Warning (dma_ranges_format):
On Wed, Nov 04, 2020 at 04:24:25PM +, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/input/misc/drv2667.c:109: warning: Function parameter or member
> 'input_dev' not described in 'drv2667_data'
> drivers/input/misc/drv2667.c:109: warning: Function
On Wed, Nov 04, 2020 at 04:24:24PM +, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/input/misc/drv2665.c:59: warning: Function parameter or member
> 'input_dev' not described in 'drv2665_data'
> drivers/input/misc/drv2665.c:59: warning: Function parameter
On Wed, Nov 04, 2020 at 04:24:23PM +, Lee Jones wrote:
> Fixes the following W=1 kernel build warning(s):
>
> drivers/input/misc/drv260x.c:194: warning: Function parameter or member
> 'input_dev' not described in 'drv260x_data'
> drivers/input/misc/drv260x.c:194: warning: Function
Hi Masahiro,
FYI, the error/warning still remains.
tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
master
head: f8394f232b1eab649ce2df5c5f15b0e528c92091
commit: def2fbffe62c00c330c7f41584a356001179c59c kconfig: allow symbols implied
by y to become m
date: 8
On 2020/11/6 15:58, Vincent Guittot wrote:
> On Wed, 21 Oct 2020 at 17:05, Aubrey Li wrote:
>>
>> From: Aubrey Li
>>
>> Added idle cpumask to track idle cpus in sched domain. When a CPU
>> enters idle, its corresponding bit in the idle cpumask will be set,
>> and when the CPU exits idle, its bit
On 2020/11/5 下午8:22, Alexander Lobakin wrote:
From: Jason Wang
Date: Thu, 5 Nov 2020 11:10:24 +0800
Hi Jason,
On 2020/11/4 下午11:31, Alexander Lobakin wrote:
Since commit 086d08725d34 ("remoteproc: create vdev subdevice with
specific dma memory pool"), every remoteproc has a DMA subdevice
On 2020/11/7 1:54, Joel Fernandes wrote:
> On Fri, Nov 06, 2020 at 10:58:58AM +0800, Li, Aubrey wrote:
>
>>>
>>> -- workload D, new added syscall workload, performance drop in cs_on:
>>> +--+--+---+
>>> | | **
Hi all,
Today's linux-next merge of the akpm-current tree got a conflict in:
arch/arc/Kconfig
between commit:
39cac191ff37 ("arc/mm/highmem: Use generic kmap atomic implementation")
from the tip tree and commit:
b41c56d2a9e6 ("arc: use FLATMEM with freeing of unused memory map instead
On 09-11-20, 08:44, Dmitry Osipenko wrote:
> 09.11.2020 08:35, Viresh Kumar пишет:
> > On 09-11-20, 08:19, Dmitry Osipenko wrote:
> >> Thanks, I made it in a different way by simply adding helpers to the
> >> pm_opp.h which use devm_add_action_or_reset(). This doesn't require to
> >> add new
On Mon, Nov 09, 2020 at 11:43:54AM +0800, Wang Qing wrote:
> Use kobj_to_dev() instead of container_of().
>
> Signed-off-by: Wang Qing
Applied, thank you.
--
Dmitry
> -Original Message-
> From: Abel Vesa [mailto:abel.v...@nxp.com]
> Sent: Tuesday, November 3, 2020 7:18 PM
> To: Mike Turquette ; Stephen Boyd
> ; Adam Ford ; Marek Vasut
> ; Lucas Stach ; Rob
> Herring ; Shawn Guo ; Sascha
> Hauer ; Fabio Estevam ;
> Anson Huang ; Jacky Bai ; Peng
> Fan
09.11.2020 08:35, Viresh Kumar пишет:
> On 09-11-20, 08:19, Dmitry Osipenko wrote:
>> Thanks, I made it in a different way by simply adding helpers to the
>> pm_opp.h which use devm_add_action_or_reset(). This doesn't require to
>> add new kernel symbols.
>
> I will prefer to add it in core.c
Hi all,
After merging the mac80211-next tree, today's linux-next build (htmldocs)
produced this warning:
Documentation/driver-api/80211/cfg80211:48: include/net/cfg80211.h:1014:
WARNING: Unexpected indentation.
Documentation/driver-api/80211/cfg80211:48: include/net/cfg80211.h:1016:
WARNING:
After the dividers of PLL-CPUX disabled, there's no need for PLL-CPUX to
be gated when tweaking the clock of CPUX, thus reparenting CPUX to
osc24M is also now not needed.
Remove these notifiers.
Preventing reparenting CPUX is said to be able to help solving the issue
that the timer jumps
On 09-11-20, 08:19, Dmitry Osipenko wrote:
> Thanks, I made it in a different way by simply adding helpers to the
> pm_opp.h which use devm_add_action_or_reset(). This doesn't require to
> add new kernel symbols.
I will prefer to add it in core.c itself, and yes
devm_add_action_or_reset() looks
According to the user manual, PLL-CPUX have two dividers, in which P is
only allowed when the desired rate is less than 240MHz. As the CCU
framework have no such feature yet and the clock rate that allows P is
much lower than where we normally operate, disallow the usage of P
factor now.
M is not
On 07.11.20 02:11, Brian Masney wrote:
When booting a hyperthreaded system with the kernel parameter
'mitigations=auto,nosmt', the following warning occurs:
WARNING: CPU: 0 PID: 1 at drivers/xen/events/events_base.c:1112
unbind_from_irqhandler+0x4e/0x60
...
Hardware name: Xen
According to Ondrej Jirman, switching of the mux of CPUX clock is one of
the sources of timer jumps on A64 (and maybe this will also lead to
timer jump on H3).
This patchset tries to remove this mux by disabling the dividers in
PLL-CPUX. Both the lack of reparent when relocking and the prevention
09.11.2020 07:57, Viresh Kumar пишет:
> On 09-11-20, 07:41, Dmitry Osipenko wrote:
>> 09.11.2020 07:34, Viresh Kumar пишет:
>>> On 06-11-20, 16:18, Dmitry Osipenko wrote:
06.11.2020 09:24, Viresh Kumar пишет:
> It has been found that some users (like cpufreq-dt and others on LKML)
>
> -Original Message-
> From: Thomas Gleixner
> Sent: Saturday, November 7, 2020 8:32 AM
> To: Tian, Kevin ; Jason Gunthorpe
> Cc: Jiang, Dave ; Bjorn Helgaas ;
> vk...@kernel.org; Dey, Megha ; m...@kernel.org;
> bhelg...@google.com; alex.william...@redhat.com; Pan, Jacob jun
> ; Raj,
09.11.2020 08:10, Viresh Kumar пишет:
> On 09-11-20, 08:08, Dmitry Osipenko wrote:
>> 09.11.2020 08:00, Viresh Kumar пишет:
>>> On 06-11-20, 21:41, Frank Lee wrote:
On Fri, Nov 6, 2020 at 9:18 PM Dmitry Osipenko wrote:
>
> 06.11.2020 09:15, Viresh Kumar пишет:
>> Setting
On 2020-10-30 14:53, Sai Prakash Ranjan wrote:
Some hardware variants contain a system cache or the last level
cache(llc). This cache is typically a large block which is shared
by multiple clients on the SOC. GPU uses the system cache to cache
both the GPU data buffers(like textures) as well the
On 09-11-20, 08:10, Dmitry Osipenko wrote:
> 09.11.2020 07:47, Dmitry Osipenko пишет:
> > 09.11.2020 07:43, Viresh Kumar пишет:
> >> On 08-11-20, 15:19, Dmitry Osipenko wrote:
> >>> I took a detailed look at the GENPD and tried to implement it. Here is
> >>> what was found:
> >>>
> >>> 1. GENPD
09.11.2020 07:47, Dmitry Osipenko пишет:
> 09.11.2020 07:43, Viresh Kumar пишет:
>> On 08-11-20, 15:19, Dmitry Osipenko wrote:
>>> I took a detailed look at the GENPD and tried to implement it. Here is
>>> what was found:
>>>
>>> 1. GENPD framework doesn't aggregate performance requests from the
On 09-11-20, 08:08, Dmitry Osipenko wrote:
> 09.11.2020 08:00, Viresh Kumar пишет:
> > On 06-11-20, 21:41, Frank Lee wrote:
> >> On Fri, Nov 6, 2020 at 9:18 PM Dmitry Osipenko wrote:
> >>>
> >>> 06.11.2020 09:15, Viresh Kumar пишет:
> Setting regulators for count as 0 doesn't sound good to
09.11.2020 08:00, Viresh Kumar пишет:
> On 06-11-20, 21:41, Frank Lee wrote:
>> On Fri, Nov 6, 2020 at 9:18 PM Dmitry Osipenko wrote:
>>>
>>> 06.11.2020 09:15, Viresh Kumar пишет:
Setting regulators for count as 0 doesn't sound good to me.
But, I understand that you don't want to
On 06-11-20, 21:41, Frank Lee wrote:
> On Fri, Nov 6, 2020 at 9:18 PM Dmitry Osipenko wrote:
> >
> > 06.11.2020 09:15, Viresh Kumar пишет:
> > > Setting regulators for count as 0 doesn't sound good to me.
> > >
> > > But, I understand that you don't want to have that if (have_regulator)
> > >
On Mon, Nov 9, 2020 at 6:00 AM Waiman Long wrote:
>
> The default value of inotify.max_user_watches sysctl parameter was set
> to 8192 since the introduction of the inotify feature in 2005 by
> commit 0eeca28300df ("[PATCH] inotify"). Today this value is just too
> small for many modern usage. As
On 09-11-20, 07:41, Dmitry Osipenko wrote:
> 09.11.2020 07:34, Viresh Kumar пишет:
> > On 06-11-20, 16:18, Dmitry Osipenko wrote:
> >> 06.11.2020 09:24, Viresh Kumar пишет:
> >>> It has been found that some users (like cpufreq-dt and others on LKML)
> >>> have abused the helper
Hi,
> -Original Message-
> From: xiakaixu1...@gmail.com
> Sent: Saturday, November 7, 2020 10:22 PM
> To: j...@linux.ibm.com; martin.peter...@oracle.com
> Cc: linux-s...@vger.kernel.org; linux-kernel@vger.kernel.org; Kaixu Xia
>
> Subject: [PATCH] scsi: bnx2fc: fix comparison to bool
09.11.2020 07:43, Viresh Kumar пишет:
> On 08-11-20, 15:19, Dmitry Osipenko wrote:
>> I took a detailed look at the GENPD and tried to implement it. Here is
>> what was found:
>>
>> 1. GENPD framework doesn't aggregate performance requests from the
>> attached devices. This means that if deviceA
On 08-11-20, 15:19, Dmitry Osipenko wrote:
> I took a detailed look at the GENPD and tried to implement it. Here is
> what was found:
>
> 1. GENPD framework doesn't aggregate performance requests from the
> attached devices. This means that if deviceA requests performance state
> 10 and then
This patch series enables support for the ARM SCMI and the various
drivers provided (cpufreq, clock, sensors, reset) since these are
utilized by Broadcom STB platforms.
Please let me know if you would like me to carry those patches through
the ARM SoC pull requests for v5.11 or if you would like
Enable the ARM SCMI protocol and the common clock, cpufreq, reset and
sensors drivers. Broadcom STB platforms (ARCH_BRCMSTB) implement SCMI to
provide support for CPU frequency scaling, clock configuration and
temperature and current sensors.
Signed-off-by: Florian Fainelli
---
Enable the ARM SCMI protocol and the common clock, cpufreq and sensors
drivers. Broadcom STB platforms (ARCH_BRCMSTB) implement SCMI to provide
support for CPU frequency scaling, clock configuration and temperature
and current sensors.
Signed-off-by: Florian Fainelli
---
09.11.2020 07:34, Viresh Kumar пишет:
> On 06-11-20, 16:18, Dmitry Osipenko wrote:
>> 06.11.2020 09:24, Viresh Kumar пишет:
>>> It has been found that some users (like cpufreq-dt and others on LKML)
>>> have abused the helper dev_pm_opp_get_opp_table() to create the OPP
>>> table instead of just
1 - 100 of 502 matches
Mail list logo
