When the mmc_rescan work is enabled for execution (host->rescan_disable),
it's the only instance per mmc host that is allowed to set/clear the
host->bus_ops pointer.
Besides the mmc_rescan work, there are a couple of scenarios when the
host->bus_ops pointer may be accessed. Typically, those can be
On Fri 12-02-21 11:42:15, David Hildenbrand wrote:
> On 12.02.21 11:33, Michal Hocko wrote:
[...]
> > I have to digest this but my first impression is that this is more heavy
> > weight than it needs to. Pfn walkers should normally obey node range at
> > least. The first pfn is usually excluded but
This macro iterates for each group of bits (clump) with set bits,
within a bitmap memory region. For each iteration, "start" is set to
the bit offset of the found clump, while the respective clump value is
stored to the location pointed by "clump". Additionally, the
bitmap_get_value() and bitmap_se
On Fri, Feb 12, 2021 at 12:00:15PM +, Lorenzo Pieralisi wrote:
> On Thu, Feb 11, 2021 at 03:33:52PM +, Vincenzo Frascino wrote:
> > +void mte_suspend_enter(void)
> > +{
> > + if (!system_supports_mte())
> > + return;
> > +
> > + /*
> > +* The barriers are required to guara
Hello Bartosz,
Since this patchset primarily affects GPIO drivers, would you like
to pick it up through your GPIO tree?
This patchset introduces a new generic version of for_each_set_clump.
The previous version of for_each_set_clump8 used a fixed size 8-bit
clump, but the new generic version can
Add bindings for the Toshiba Visconti PWM Controller.
Signed-off-by: Nobuhiro Iwamatsu
---
.../bindings/pwm/toshiba,pwm-visconti.yaml| 43 +++
1 file changed, 43 insertions(+)
create mode 100644
Documentation/devicetree/bindings/pwm/toshiba,pwm-visconti.yaml
diff --git a/D
This series is the PWM driver for Toshiba's ARM SoC, Visconti[0].
This provides DT binding documentation and device driver.
[0]:
https://toshiba.semicon-storage.com/ap-en/semiconductor/product/image-recognition-processors-visconti.html
Updates:
dt-bindings: pwm: Add bindings for Toshiba Visco
This patch reimplements the thunderx_gpio_set_multiple function in
drivers/gpio/gpio-thunderx.c to use the new for_each_set_clump macro.
Instead of looping for each bank in thunderx_gpio_set_multiple
function, now we can skip bank which is not set and save cycles.
Cc: William Breathitt Gray
Cc: R
Add driver for the PWM controller on Toshiba Visconti ARM SoC.
Signed-off-by: Nobuhiro Iwamatsu
---
drivers/pwm/Kconfig| 9 ++
drivers/pwm/Makefile | 1 +
drivers/pwm/pwm-visconti.c | 173 +
3 files changed, 183 insertions(+)
create mode 100
This patch reimplements the xgpio_set_multiple() function in
drivers/gpio/gpio-xilinx.c to use the new generic functions:
bitmap_get_value() and bitmap_set_value(). The code is now simpler
to read and understand. Moreover, instead of looping for each bit
in xgpio_set_multiple() function, now we can
On Thu, 11 Feb 2021 10:27:41 -0800
Ben Widawsky wrote:
> On 21-02-11 09:55:48, Jonathan Cameron wrote:
> > On Wed, 10 Feb 2021 10:16:05 -0800
> > Ben Widawsky wrote:
> >
> > > On 21-02-10 08:55:57, Ben Widawsky wrote:
> > > > On 21-02-10 15:07:59, Jonathan Cameron wrote:
> > > > > On We
On Thu, 11 Feb 2021 07:55:29 -0800
Ben Widawsky wrote:
> On 21-02-11 09:55:48, Jonathan Cameron wrote:
> > On Wed, 10 Feb 2021 10:16:05 -0800
> > Ben Widawsky wrote:
> >
> > > On 21-02-10 08:55:57, Ben Widawsky wrote:
> > > > On 21-02-10 15:07:59, Jonathan Cameron wrote:
> > > > > On We
On Fri, Feb 12, 2021 at 12:35:15PM +, Mark Brown wrote:
> On Fri, Feb 12, 2021 at 11:30:41AM +, Steven Price wrote:
> > On 11/02/2021 20:21, sonicadvan...@gmail.com wrote:
> > > Why do we need compatibility layers?
> > > There are ARMv8 CPUs that only support AArch64 but still need to run
>
On Tue, 26 Jan 2021 at 13:28, Hillf Danton wrote:
>
>
> BTW better run the reproducer again with KASAN enabled.
>
It happened today again with kernel 5.11 rc7 (e0756cfc7d7c)
Why not try your patch?
list_del corruption, def70143e848->next is LIST_POISON1 (dead0100)
[ cut h
Joel reported long preempt and irq off sequence in newidle_balance because
of a large number of CPU cgroups in use and having to be updated. This
patchset moves the update outside newidle_imblance. This enables to early
abort during the updates in case of pending irq as an example.
Instead of kick
On Fri, 12 Feb 2021 at 13:25, Greg Kroah-Hartman
wrote:
>
> This is the start of the stable review cycle for the 4.19.176 release.
> There are 27 patches in this series, all will be posted as a response
> to this one. If anyone has any issues with these being applied, please
> let me know.
>
> Re
newidle_balance runs with both preempt and irq disabled which prevent
local irq to run during this period. The duration for updating the
blocked load of CPUs varies according to the number of CPU cgroups
with non-decayed load and extends this critical period to an uncontrolled
level.
Remove the up
idle load balance is the only user of update_nohz_stats and doesn't use
force parameter. Remove it
Signed-off-by: Vincent Guittot
---
kernel/sched/fair.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index f3f0f8cca061..4573a0
The return of _nohz_idle_balance() is not used anymore so we can remove
it
Signed-off-by: Vincent Guittot
---
kernel/sched/fair.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index bfe1e235fe01..f3f0f8cca061 100644
--- a/
Start to update last_blocked_load_update_tick to reduce the possibility
of another cpu starting the update one more time
Signed-off-by: Vincent Guittot
---
kernel/sched/fair.c | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.
Remove the specific case for handling this_cpu outside for_each_cpu() loop
when running ILB. Instead we use for_each_cpu_wrap() and start with the
next cpu after this_cpu so we will continue to finish with this_cpu.
update_nohz_stats() is now used for this_cpu too and will prevents
unnecessary upd
Reorder the tests and skip useless ones when no load balance has been
performed and rq lock has not been released.
Signed-off-by: Vincent Guittot
---
kernel/sched/fair.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index
Instead of waking up a random and already idle CPU, we can take advantage
of this_cpu being about to enter idle to run the ILB and update the
blocked load.
Signed-off-by: Vincent Guittot
---
kernel/sched/fair.c | 20 +---
kernel/sched/idle.c | 6 ++
kernel/sched/sched.h |
On 2/10/2021 4:51 PM, George Kennedy wrote:
On 2/3/2021 2:35 PM, Dmitry Vyukov wrote:
On Wed, Feb 3, 2021 at 8:29 PM Konrad Rzeszutek Wilk
wrote:
Hey Dmitry, Rafael, George, please see below..
On Wed, Jan 27, 2021 at 10:10:07PM +0100, Dmitry Vyukov wrote:
On Wed, Jan 27, 2021 at 9:01 PM
On Fri 2021-02-12 13:38:58, Linus Walleij wrote:
> I need Arnds help with this...
>
> On Fri, Feb 12, 2021 at 12:05 AM kernel test robot wrote:
>
> >ld: drivers/leds/flash/leds-rt8515.o: in function
> > `rt8515_v4l2_flash_release':
> > >> drivers/leds/flash/leds-rt8515.c:216: undefined refe
On Thu, 11 Feb 2021 12:40:45 -0800
Dan Williams wrote:
> On Thu, Feb 11, 2021 at 2:19 AM Jonathan Cameron
> wrote:
> >
> > On Wed, 10 Feb 2021 18:17:25 +
> > Jonathan Cameron wrote:
> >
> > > On Tue, 9 Feb 2021 16:02:54 -0800
> > > Ben Widawsky wrote:
> > >
> > > > From: Dan Williams
On 2021/02/12 22:12, Michal Hocko wrote:
> On Fri 12-02-21 21:58:15, Tetsuo Handa wrote:
>> On 2021/02/12 21:30, Michal Hocko wrote:
>>> On Fri 12-02-21 12:22:07, Matthew Wilcox wrote:
On Fri, Feb 12, 2021 at 08:18:11PM +0900, Tetsuo Handa wrote:
> On 2021/02/12 1:41, Michal Hocko wrote:
>
Thanks for the update and sorry for the late reply. After long-term testing of
the patch, storm detection improved, it turns out that a similar problem can
occur if hrtimer_interrupt runs during clock_settime. In this case it seems the
offset can get updated and later read using hrtimer_update_b
On Thu, 11 Feb 2021 08:01:48 -0800
Ben Widawsky wrote:
> On 21-02-11 11:19:24, Jonathan Cameron wrote:
> > On Tue, 9 Feb 2021 16:02:56 -0800
> > Ben Widawsky wrote:
> >
> > > The CXL memory device send interface will have a number of supported
> > > commands. The raw command is not such a com
Hi,
Thanks for your patience, and thanks for sticking around!
I'm sorry I haven't reviewed this again in a long time, but I was able
to today.
> +PUREILIFI USB DRIVER
Did you mistype "PURELIFI" here, or was that intentional?
> +PUREILIFI USB DRIVER
> +M: Srinivasan Raju
Probably would be
This is a tool that is intended to work around the fact that the
preemptoff, irqsoff, and preemptirqsoff tracers only work in
overwrite mode. The idea is to act randomly in such a way that we
do not systematically lose any latencies, so that if enough testing
is done, all latencies will be captured
Hello Oleksij,
nice cleanup - and I like the removal of the notifier in af_can.c :-)
Two questions/hints from my side:
On 12.02.21 13:52, Oleksij Rempel wrote:
diff --git a/drivers/net/can/dev/dev.c b/drivers/net/can/dev/dev.c
index d9281ae853f8..912401788d93 100644
--- a/drivers/net/can/dev/
Changes since v11
* I added a .gitignore in the tools/tracing/latency directory.
Changes since v10
* Using libtracefs to control ftrace and find /sys/kernel/tracing
* New options to list available tracers, select the tracer and other
ftrace parameters
* A signal handler to restore the ftrac
On Fri, Feb 12, 2021 at 2:31 PM George Kennedy
wrote:
> On 2/10/2021 4:51 PM, George Kennedy wrote:
> > On 2/3/2021 2:35 PM, Dmitry Vyukov wrote:
> >> On Wed, Feb 3, 2021 at 8:29 PM Konrad Rzeszutek Wilk
> >> wrote:
> >>> Hey Dmitry, Rafael, George, please see below..
> >>>
> >>> On Wed, Jan 27,
> > Or we have also found out, that pushing back on parameters like this,
> > the developers goes back and looks at the code, and sometimes figures
> > out a way to automatically do the right thing, removing the
> > configuration knob, and just making it all simpler for the user to
> > use.
>
> I
On Fri, Feb 12, 2021 at 09:33:44AM +, Vaittinen, Matti wrote:
> There seems to be few drivers which need delayed wq and which implement
> .remove() just to call the cancel_delayed_work_sync().
> I think this might help cleaning up those(?) Or am I completely off
> here?
I can see it being us
On Fri, Feb 12, 2021 at 12:33 PM Steven Price wrote:
> On 11/02/2021 20:21, sonicadvan...@gmail.com wrote:
> > The problem:
> > We need to support 32-bit processes running under a userspace
> > compatibility layer. The compatibility layer is a AArch64 process.
> > This means exposing the 32bit co
On 2/11/21 8:04 PM, Jakub Kicinski wrote:
On Fri, 12 Feb 2021 03:05:23 +0530 Sharath Chandra Vurukala wrote:
+/* MAP CSUM headers */
+struct rmnet_map_v5_csum_header {
+ u8 next_hdr:1;
+ u8 header_type:7;
+ u8 hw_reserved:5;
+ u8 priority:1;
+ u8 hw_reserved_bi
On Fri, Feb 12, 2021 at 01:25:21PM +0100, Frederic Weisbecker wrote:
> On Thu, Jan 28, 2021 at 05:21:36PM -0300, Marcelo Tosatti wrote:
> > Rather than waking up all nohz_full CPUs on the system, only wakeup
> > the target CPUs of member threads of the signal.
> >
> > Reduces interruptions to noh
On 2021-02-12 1:57 p.m., Emil Velikov wrote:
On Fri, 5 Feb 2021 at 22:01, Chris Wilson wrote:
Userspace has discovered the functionality offered by SYS_kcmp and has
started to depend upon it. In particular, Mesa uses SYS_kcmp for
os_same_file_description() in order to identify when two fd (e.g
On Fri, 12 Feb 2021 10:00:23 +0200, Matti Vaittinen wrote:
> The ROHM BD718x7 and BD71828 drivers support setting HW state
> specific voltages from device-tree. This is used also by various
> in-tree DTS files.
>
> These drivers do incorrectly try to compose bit-map using enum
> values. By a chanc
On Thu, 11 Feb 2021 19:08:20 +0100, Nicolas Saenz Julienne wrote:
> With the introduction of 26751de25d25 ("spi: bcm2835: Micro-optimise
> FIFO loops") it has become apparent that some users might initiate
> zero-length SPI transfers. A fact the micro-optimization omitted, and
> which turned out to
On Thu, 11 Feb 2021 12:37:14 -0800, Kees Cook wrote:
> Since "data" is u32, &data is a "u32 *" type, which means pointer math
> will move in u32-sized steps. This was meant to be a byte offset, so
> cast &data to "char *" to aim the copy into the correct location.
>
> Seen with -Warray-bounds (and
> So the plan to fix this warning is, when device_bind_driver() is called:
> 1. Delete all device links from the device (in this case, the PHY) to
> suppliers that haven't probed yet because there's no probe function
> that can defer at this point.
Just because it currently does not happen, does n
At Power-On Reset, transients may cause the LCPLL to lock onto a
clock that is momentarily unstable. This is normally seen in QSGMII
setups where the higher speed 6G SerDes is being used.
This patch adds an initial LCPLL Reset to the PHY (first instance)
to avoid this issue.
Signed-off-by: Steen H
The current IB serdes calibration algorithm (performed by the onboard 8051)
has proven to be unstable for the VSC8514 QSGMII phy.
A new algorithm has been developed based on
'Frequency-offset Jittered-Injection' or 'FoJi' method which solves
all known issues. This patch disables the 8051 algorithm
The 'coma mode' (configurable through sw or hw) provides an
optional feature that may be used to control when the PHYs become active.
The typical usage is to synchronize the link-up time across
all PHY instances. This patch releases coma mode if not done by hardware,
otherwise the phys will not lin
On Fri, 12 Feb 2021 at 13:14, Simon Ser wrote:
>
> On Friday, February 12th, 2021 at 1:57 PM, Emil Velikov
> wrote:
>
> > On Fri, 5 Feb 2021 at 22:01, Chris Wilson wrote:
> > >
> > > Userspace has discovered the functionality offered by SYS_kcmp and has
> > > started to depend upon it. In parti
On Fri, 12 Feb 2021 at 14:01, Michel Dänzer wrote:
>
> On 2021-02-12 1:57 p.m., Emil Velikov wrote:
> > On Fri, 5 Feb 2021 at 22:01, Chris Wilson wrote:
> >>
> >> Userspace has discovered the functionality offered by SYS_kcmp and has
> >> started to depend upon it. In particular, Mesa uses SYS_kc
On 12/02/2021 15:12, Song Bao Hua (Barry Song) wrote:
-Original Message-
From: Grygorii Strashko [mailto:grygorii.stras...@ti.com]
Sent: Saturday, February 13, 2021 12:53 AM
To: Song Bao Hua (Barry Song) ; Andy Shevchenko
Cc: Arnd Bergmann ; luojiaxing ; Linus
Walleij ; Santosh Shi
On Fri, Feb 12, 2021 at 12:41:48PM +, Luis Henriques wrote:
> Greg KH writes:
>
> > On Fri, Feb 12, 2021 at 12:05:14PM +, Luis Henriques wrote:
> >> Greg KH writes:
> >>
> >> > On Fri, Feb 12, 2021 at 10:22:16AM +0200, Amir Goldstein wrote:
> >> >> On Fri, Feb 12, 2021 at 9:49 AM Greg K
On 2/8/21 7:31 AM, Rajan Vaja wrote:
> From: Tejas Patel
>
> Fix smatch warning:
> drivers/firmware/xilinx/zynqmp.c:1288 zynqmp_firmware_remove()
> error: dereferencing freed memory 'feature_data'
>
> Use hash_for_each_safe for safe removal of hash entry.
>
> Fixes: acfdd18591ea ("firmware:
Hi Gustavo,
"Gustavo A. R. Silva" wrote on Fri, 12 Feb 2021
04:40:22 -0600:
> Cast &data to (char *) in order to avoid unintentionally accessing
> the stack.
>
> Notice that data is of type u32, so any increment to &data
> will be in the order of 4-byte chunks, and this piece of code
> is actua
CHECK drivers/acpi/property.c
warning: Function parameter or member '__fwnode' not described in
'acpi_graph_get_remote_endpoint'
warning: Excess function parameter 'fwnode' description in
'acpi_graph_get_remote_endpoint'
warning: Excess function parameter 'endpoint' description in
'acpi_gra
From: Catalin Marinas
> Sent: 12 February 2021 13:28
>
> On Fri, Feb 12, 2021 at 12:35:15PM +, Mark Brown wrote:
> > On Fri, Feb 12, 2021 at 11:30:41AM +, Steven Price wrote:
> > > On 11/02/2021 20:21, sonicadvan...@gmail.com wrote:
> > > > Why do we need compatibility layers?
> > > > Ther
Refactor acpi_data_prop_read_single() for less LOCs and better maintenance.
Signed-off-by: Andy Shevchenko
---
drivers/acpi/property.c | 80 ++---
1 file changed, 34 insertions(+), 46 deletions(-)
diff --git a/drivers/acpi/property.c b/drivers/acpi/property.c
After the commit 3a7a2ab839ad couple of functions became a dead code.
Moreover, for all these years nobody used them. Remove.
Fixes: 3a7a2ab839ad ("ACPI / property: Extend fwnode_property_* to data-only
subnodes")
Signed-off-by: Andy Shevchenko
---
drivers/acpi/property.c | 20 -
There is no users outside of property.c. No need to export
acpi_node_prop_read(), hence make it static.
Fixes: 3708184afc77 ("device property: Move FW type specific functionality to
FW specific files")
Signed-off-by: Andy Shevchenko
---
drivers/acpi/property.c | 6 +++---
include/linux/acpi.h
On Thu, Feb 11, 2021 at 12:21:54PM -0800, sonicadvan...@gmail.com wrote:
> From: Ryan Houdek
>
> Sorry about the noise. I obviously don't work in this ecosystem.
> Didn't get any comments previously so I'm resending
>
> The problem:
> We need to support 32-bit processes running under a userspace
On 11.02.21 19:05, Mike Kravetz wrote:
On 2/8/21 12:50 AM, Muchun Song wrote:
When we free a HugeTLB page to the buddy allocator, we should allocate the
vmemmap pages associated with it. But we may cannot allocate vmemmap pages
when the system is under memory pressure, in this case, we just refu
On Thu, Feb 11, 2021 at 9:31 PM Guenter Roeck wrote:
>
> Hi Rob,
>
> On Wed, Feb 03, 2021 at 03:26:03PM -0600, Rob Herring wrote:
> > This adds the following commits from upstream:
> >
> > 183df9e9c2b9 gitignore: Ignore the swp files
> > 0db6d09584e1 gitignore: Add cscope files
> > 307afa1a7be8 Up
CHECK drivers/acpi/property.c
warning: Function parameter or member 'data' not described in
'acpi_data_get_property_array'
warning: Excess function parameter 'adev' description in
'acpi_data_get_property_array'
Fixes: 3a7a2ab839ad ("ACPI / property: Extend fwnode_property_* to data-only
sub
Joel reported long preempt and irq off sequence in newidle_balance because
of a large number of CPU cgroups in use and having to be updated. This
patchset moves the update outside newidle_imblance. This enables to early
abort during the updates in case of pending irq as an example.
Instead of kick
The return of _nohz_idle_balance() is not used anymore so we can remove
it
Signed-off-by: Vincent Guittot
---
kernel/sched/fair.c | 10 +-
1 file changed, 1 insertion(+), 9 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index bfe1e235fe01..f3f0f8cca061 100644
--- a/
idle load balance is the only user of update_nohz_stats and doesn't use
force parameter. Remove it
Signed-off-by: Vincent Guittot
---
kernel/sched/fair.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index f3f0f8cca061..4573a0
On 12/02/2021 03:05, Vladimir Oltean wrote:
From: Vladimir Oltean
The initial goal of this series was to have better support for
standalone ports mode on the DSA drivers like ocelot/felix and sja1105.
This turned out to require some API adjustments in both directions:
to the information pres
Instead of waking up a random and already idle CPU, we can take advantage
of this_cpu being about to enter idle to run the ILB and update the
blocked load.
Signed-off-by: Vincent Guittot
---
kernel/sched/fair.c | 24 +---
kernel/sched/idle.c | 6 ++
kernel/sched/sched.
Reorder the tests and skip useless ones when no load balance has been
performed and rq lock has not been released.
Signed-off-by: Vincent Guittot
---
kernel/sched/fair.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index
On Fri, Feb 12, 2021 at 11:00:41AM -0300, Marcelo Tosatti wrote:
> On Fri, Feb 12, 2021 at 01:25:21PM +0100, Frederic Weisbecker wrote:
> > On Thu, Jan 28, 2021 at 05:21:36PM -0300, Marcelo Tosatti wrote:
> > > Rather than waking up all nohz_full CPUs on the system, only wakeup
> > > the target CP
newidle_balance runs with both preempt and irq disabled which prevent
local irq to run during this period. The duration for updating the
blocked load of CPUs varies according to the number of CPU cgroups
with non-decayed load and extends this critical period to an uncontrolled
level.
Remove the up
Start to update last_blocked_load_update_tick to reduce the possibility
of another cpu starting the update one more time
Signed-off-by: Vincent Guittot
---
kernel/sched/fair.c | 11 ---
1 file changed, 8 insertions(+), 3 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.
Remove the specific case for handling this_cpu outside for_each_cpu() loop
when running ILB. Instead we use for_each_cpu_wrap() and start with the
next cpu after this_cpu so we will continue to finish with this_cpu.
update_nohz_stats() is now used for this_cpu too and will prevents
unnecessary upd
On Thu, Jan 28, 2021 at 05:21:34PM -0300, Marcelo Tosatti wrote:
> When enabling per-CPU posix timers, an IPI to nohz_full CPUs might be
> performed (to re-read the dependencies and possibly not re-enter
> nohz_full on a given CPU).
>
> A common case is for applications that run on nohz_full= CPUs
Previously the variable rate audio pll output was fixed to a divider of
four. This is unfortunately incompatible with generating commonly used
I2S core clock rates like 24.576MHz from the 24MHz parent clock.
This commit adds support for arbitrary audio pll output dividers to fix
that.
Signed-off-b
On 2/12/21 8:50 PM, Gustavo A. R. Silva wrote:
> Cast multiple variables to (int64_t) in order to give the compiler
> complete information about the proper arithmetic to use. Notice that
> these variables are being used in contexts that expect expressions of
> type int64_t (64 bit, signed). And cu
On Thu, Feb 11, 2021 at 09:35:27PM +0100, Greg KH wrote:
> On Fri, Feb 12, 2021 at 01:59:08AM +0530, Anirudh Rayabharam wrote:
> > Fix sparse byte-order warnings in the i2400m_bm_cmd_prepare()
> > function:
> >
> > wimax/i2400m/fw.c:194:36: warning: restricted __le32 degrades to integer
> > wimax/
Add support for Intel's eASIC N5X platform. The clock manager driver for
the N5X is very similar to the Agilex platform, we can re-use most of
the Agilex clock driver.
This patch makes the necessary changes for the driver to differentiate
between the Agilex and the N5X platforms.
Signed-off-by: D
On Fri, Feb 12, 2021 at 3:14 PM Andy Shevchenko
wrote:
>
> Refactor acpi_data_prop_read_single() for less LOCs and better maintenance.
>
> Signed-off-by: Andy Shevchenko
> ---
> drivers/acpi/property.c | 80 ++---
> 1 file changed, 34 insertions(+), 46 deleti
Document the Agilex clock bindings, and add the clock header file. The
clock header is an enumeration of all the different clocks on the eASIC
N5X platform.
Signed-off-by: Dinh Nguyen
---
.../bindings/clock/intel,easic-n5x.yaml | 46 +++
1 file changed, 46 insertions(+)
cr
On 2/10/21 9:05 PM, Stephen Boyd wrote:
Quoting Dinh Nguyen (2021-01-05 11:29:56)
Add support for Intel's eASIC N5X platform. The clock manager driver for
the N5X is very similar to the Agilex platform, we can re-use most of
the Agilex clock driver.
This patch makes the necessary changes for
Hi Vladimir,
On 2/12/21 7:47 PM, Grygorii Strashko wrote:
>
>
> On 12/02/2021 03:05, Vladimir Oltean wrote:
>> From: Vladimir Oltean
[...]
>
> Sorry, but we seems just added more work for you.
> https://lore.kernel.org/patchwork/cover/1379380/
>
Could you squash these when you post new versi
Version 3 of this series uses dev_err_probe() in the second patch,
as suggested by Heiner Kallweit.
Version 2 was sent to ensure the series was based on current
net-next/master, and added copyright updates to files touched.
The original introduction is below.
This patch actually fixes a bug, though it doesn't affect the two
platforms supported currently. The fix implements GSI memory
pointers a bit differently.
For IPA version 4.5 and above, the address space for almost all GSI
registers is adjusted downward by a fixed amount. This is currently
handl
When initializing the IPA core clock and interconnects, it's
possible we'll get an EPROBE_DEFER error. This isn't really an
error, it's just means we need to be re-probed later.
Use dev_err_probe() to report the error rather than dev_err().
This avoids polluting the log with these "error" message
Create a simple helper function that indicates whether a channel has
been initialized. This abstacts/hides the details of how this is
determined.
Signed-off-by: Alex Elder
---
drivers/net/ipa/gsi.c | 22 ++
1 file changed, 14 insertions(+), 8 deletions(-)
diff --git a/drive
In ipa_cmd_register_write_valid() we verify that values we will
supply to a REGISTER_WRITE IPA immediate command will fit in
the fields that need to hold them. This patch fixes some issues
in that function and ipa_cmd_register_write_offset_valid().
The dev_err() call in ipa_cmd_register_write_off
On Fri, Feb 12, 2021 at 3:16 PM Andy Shevchenko
wrote:
>
> After the commit 3a7a2ab839ad couple of functions became a dead code.
> Moreover, for all these years nobody used them. Remove.
>
> Fixes: 3a7a2ab839ad ("ACPI / property: Extend fwnode_property_* to data-only
> subnodes")
> Signed-off-by:
Introduce a new function to abstract the knowledge of whether hashed
routing and filter tables are supported for a given IPA instance.
IPA v4.2 is the only one that doesn't support hashed tables (now
and for the foreseeable future), but the name of the helper function
is better for explaining what
On Thu, Feb 11, 2021 at 7:17 PM Lakshmi Ramasubramanian
wrote:
>
> On 2/11/21 5:09 PM, Thiago Jung Bauermann wrote:
> >
> > There's actually a complication that I just noticed and needs to be
> > addressed. More below.
> >
>
> <...>
>
> >> +
> >> +/*
> >> + * of_kexec_alloc_and_setup_fdt - Alloc a
Hi, Chunfeng:
Chunfeng Yun 於 2021年2月1日 週一 下午3:00寫道：
>
> mt7623-mipi-tx is compatible to mt2701-mipi-tx, and use
> "mediatek,mt2701-mipi-tx" instead on MT7623, so modify
> the compatible items to make dependence clear.
Acked-by: Chun-Kuang Hu
>
> Cc: Chun-Kuang Hu
> Cc: Philipp Zabel
> Signed
On Fri, Feb 12, 2021 at 08:01:33PM +0530, Vignesh Raghavendra wrote:
> Hi Vladimir,
>
> On 2/12/21 7:47 PM, Grygorii Strashko wrote:
> >
> >
> > On 12/02/2021 03:05, Vladimir Oltean wrote:
> >> From: Vladimir Oltean
> [...]
> >
> > Sorry, but we seems just added more work for you.
> > https://
Hi, Chunfeng:
Chunfeng Yun 於 2021年2月1日 週一 下午3:00寫道：
>
> mt7623-hdmi-tx is compatible to mt2701-hdmi-tx, and the compatible
> "mediatek,mt7623-hdmi-tx" is not supported in driver, in fact uses
> "mediatek,mt2701-hdmi-tx" instead on MT7623, so changes the
> compatible items to make dependence clear
On Thu, 11 Feb 2021 13:48:48 -0800
Jason Gerecke wrote:
> When compiling an external kernel module with `-O0` or `-O1`, the following
> compile error may be reported:
>
> ./arch/x86/include/asm/jump_label.h:25:2: error: impossible constraint in
> ‘asm’
>25 | asm_volatile_goto("1:"
Hello.
Sometimes it's handy to display also a filename of a source location, mainly
because
source lines can come from different files. I extended 'k' hotkey and one can
now see:
1) no source lines:
1.31 │ ↓ je 130
On Fri, Feb 12, 2021 at 08:00:25PM +0530, Anirudh Rayabharam wrote:
> On Thu, Feb 11, 2021 at 09:35:27PM +0100, Greg KH wrote:
> > On Fri, Feb 12, 2021 at 01:59:08AM +0530, Anirudh Rayabharam wrote:
> > > Fix sparse byte-order warnings in the i2400m_bm_cmd_prepare()
> > > function:
> > >
> > > wim
On Fri, Feb 12, 2021 at 02:12:02PM +, David Laight wrote:
> From: Catalin Marinas
> > Sent: 12 February 2021 13:28
> > On Fri, Feb 12, 2021 at 12:35:15PM +, Mark Brown wrote:
> > > On Fri, Feb 12, 2021 at 11:30:41AM +, Steven Price wrote:
> > > > On 11/02/2021 20:21, sonicadvan...@gmail
Steven Rostedt (VMware)
Linus,
tracing: Fix buffer overflow in trace event filter
It was reported that if a trace event was larger than a page
and was filtered, that it caused memory corruption. The reason
is that filtered events first go into a buffer to test the filter
before being written in
Hi All,
Since my previous RFC, I've fixed --per-thread mode and solved
most of the open questions. I've also changed --dump-raw-trace
to use the same code path so it's also working now.
I think the only open questions are:
* General approach
* If aux records need to be saved, or if they can b
Refactor the function into separate allocation and
timestamp search parts. Later the timestamp search
will be done multiple times.
Signed-off-by: James Clark
---
tools/perf/util/cs-etm.c | 60 +---
1 file changed, 31 insertions(+), 29 deletions(-)
diff --git
To make sure processing happens in the correct order, queue processing
shouldn't start until every aux queue has had its first timestamp found.
Now that we're only searching for timestamps within each aux record, we
need to wait until all aux records are delivered before starting the
processing.
401 - 500 of 1096 matches
Mail list logo
