On Mon, Feb 08, 2021 at 08:56:53PM +0900, Hector Martin 'marcan' wrote:
> On 08/02/2021 20.04, Krzysztof Kozlowski wrote:
> > apple
> >
> > Don't make things different for this one platform (comparing to all
> > other platforms). Apple is not that special. :)
>
> AAPL is the old vendor prefix
On Mon, 8 Feb 2021 at 20:07, Kaneda, Erik wrote:
>
>
>
> > -Original Message-
> > From: Rafael J. Wysocki
> > Sent: Monday, February 8, 2021 5:01 AM
> > To: Shawn Guo ; Ard Biesheuvel
> > ; Kaneda, Erik
> > Cc: Linux ARM ; ACPI Devel Maling
> > List ; Linux Kernel Mailing List >
On Mon, Feb 08, 2021 at 05:03:30PM +0300, Serge Semin wrote:
> There has been no user of the denoted array of the device private data
> since commit e7f4dc3536a4 ("mdio: Move allocation of interrupts into
> core"). Discard it then.
>
> Signed-off-by: Serge Semin
Reviewed-by: Andrew Lunn
Hi Mark, Lee,
On 2/4/21 12:24 PM, Hans de Goede wrote:
> Hi all,
>
> Here is v4 of my series to rework the arizona codec jack-detect support
> to use the snd_soc_jack helpers instead of direct extcon reporting.
>
> This is a resend with some extra *-by tags collected and with the extcon
> folks
Hi Mark,
On 2/8/21 7:38 PM, Mark Brown wrote:
> On Wed, 20 Jan 2021 22:49:52 +0100, Hans de Goede wrote:
>> Here is v4 of my series to add support for Intel Bay Trail based devices
>> which use a WM5102 codec for audio output/input.
>>
>> This was developed and tested on a Lenovo Yoga Tablet
On Mon, 8 Feb 2021 16:04:31 +0100 Stefano Garzarella wrote:
> What do you suggest?
>
> I did it this way because by modifying only the caller, we would have a
> nested lock.
>
> This way instead we are sure that if we backport this patch, we don't
> forget to touch hvs_shutdown() as well.
I'm
Em Mon, Feb 08, 2021 at 07:25:46AM -0800, kan.li...@linux.intel.com escreveu:
> From: Jin Yao
>
> A group mixed with hybrid event and global event is allowed. For example,
> group leader is 'cpu-clock' and the group member is 'cpu_atom/cycles/'.
>
> e.g.
> perf stat -e
On 2/8/21 2:00 AM, Peter Zijlstra wrote:
This needs a binutils version number.
Yes, we will add it in next version.
--
Sathyanarayanan Kuppuswamy
Linux Kernel Developer
On Mon, Feb 08, 2021 at 02:04:24PM -0500, Liang, Kan wrote:
> On 2/8/2021 12:56 PM, Borislav Petkov wrote:
>
> I think it's good enough for perf, but I'm not sure whether other codes need
> the CPU type information.
>
> Ricardo, do you know?
>
> Maybe we should implement a generic function as
Em Mon, Feb 08, 2021 at 07:25:40AM -0800, kan.li...@linux.intel.com escreveu:
> From: Jin Yao
>
> Previously if '-e' is not specified in perf stat, some software events
> and hardware events are added to evlist by default.
>
> root@otcpl-adl-s-2:~# ./perf stat -- ./triad_loop
>
> Performance
On 2/8/2021 12:56 PM, Borislav Petkov wrote:
On Mon, Feb 08, 2021 at 07:24:59AM -0800, kan.li...@linux.intel.com wrote:
diff --git a/arch/x86/include/asm/processor.h b/arch/x86/include/asm/processor.h
index c20a52b..1f25ac9 100644
--- a/arch/x86/include/asm/processor.h
+++
On 2/8/21 8:59 AM, Peter Zijlstra wrote:
'cute', might be useful to have that mentioned somewhere.
we will add a note for it in comments.
--
Sathyanarayanan Kuppuswamy
Linux Kernel Developer
Em Mon, Feb 08, 2021 at 07:25:29AM -0800, kan.li...@linux.intel.com escreveu:
> From: Jin Yao
>
> It would be useful to let user know the hybrid topology.
> For example, the HYBRID_TOPOLOGY feature in header indicates which
> cpus are core cpus, and which cpus are atom cpus.
Can you please
On 2021-02-08 19:38:10 [+0100], Miguel Ojeda wrote:
> Hi Sebastian,
Hi,
> > Therefore there is no need to use `in_interrupt()' to figure out if it
> > is save to sleep because it always is.
>
> save -> safe
>
> Does it hurt to have `in_interrupt()`? Future patches could make it so
Yes.
> that
Em Mon, Feb 08, 2021 at 07:25:36AM -0800, kan.li...@linux.intel.com escreveu:
> From: Jin Yao
>
> On hybrid platform, same raw event is possible to be available on
> both cpu_core pmu and cpu_atom pmu. So it's supported to create
> two raw events for one event encoding.
>
>
> -Original Message-
> From: Rafael J. Wysocki
> Sent: Monday, February 8, 2021 5:01 AM
> To: Shawn Guo ; Ard Biesheuvel
> ; Kaneda, Erik
> Cc: Linux ARM ; ACPI Devel Maling
> List ; Linux Kernel Mailing List ker...@vger.kernel.org>; open list:ACPI COMPONENT ARCHITECTURE
> (ACPICA) ;
Hi,
On 2/7/21 12:21 AM, Rikard Falkeborn wrote:
> The only usage of it is to assign its address to the ops field in the
> regulator_desc struct, which is a pointer to const struct regulator_ops.
> Make it const to allow the compiler to put it in read-only memory.
>
> Signed-off-by: Rikard
On Mon, 8 Feb 2021 16:55:44 +0300 Serge Semin wrote:
> Baikal-T1 SoC is equipped with two Synopsys DesignWare GMAC v3.73a-based
> ethernet interfaces with no internal Ethernet PHY attached. The IP-cores
> are configured as GMAC-AXI with CSR interface clocked by a dedicated
> signal. Each of which
On Mon, Feb 08, 2021 at 03:53:03PM +, Serapheim Dimitropoulos wrote:
> vread() has been linearly searching vmap_area_list for looking up
> vmalloc areas to read from. These same areas are also tracked by
> a rb_tree (vmap_area_root) which offers logarithmic lookup.
>
> This patch modifies
Hi Peter & Paul,
The traces below are present in the boot dmesg log on my Dell XPS13 9360.
I haven't had the time to look into this in detail yet, but here it goes in
case you know what's going on already.
Cheers!
[ 86.762542] IPv6: ADDRCONF(NETDEV_CHANGE): wlan0: link becomes ready
[
> Hi Andrew,
>
> I honestly tried to find any doc with a glimpse of errata for RTL8211E
> PHY, but with no luck. Official datasheet didn't have any info regarding
> possible hw bugs too. Thus I had no choice but to find a fix of the
> problem myself.
>
> It took me some time to figure out why
Hi,
On 2/5/21 2:26 AM, Maximilian Luz wrote:
> Some Surface Book 2 and 3 models have a discrete GPU (dGPU) that is
> hot-pluggable. On those devices, the dGPU is contained in the base,
> which can be separated from the tablet part (containing CPU and
> touchscreen) while the device is running.
>
On Mon, Feb 08, 2021 at 04:06:18PM +0100, Sascha Hauer wrote:
> Hi Dan,
>
> On Mon, Feb 08, 2021 at 04:45:17PM +0300, Dan Carpenter wrote:
> > On Sun, Feb 07, 2021 at 05:23:28PM +0800, Youling Tang wrote:
> > > Fix the below ignoring return value warning for device_reset.
> > >
> > >
From: Rafael J. Wysocki
Rearrange the code in acpi_check_resource_conflict() so as to drop
redundant checks and uneeded local variables from there and modify
the messages printed by that function to be more concise and
hopefully easier to understand.
While at it, replace direct printk() usage
Hi All,
These two patches clean up some code in osl.c.
The first one simplifies acpi_check_resource_confllict() and the second one
deals with
message printing in this file.
See patch changelogs for details.
Thanks!
From: Rafael J. Wysocki
Replace the ACPI_DEBUG_PRINT() instance in osl.c unrelated to the
ACPICA debug with acpi_handle_debug(), add a pr_fmt() definition
to osl.c and replace direct printk() usage in that file with the
suitable pr_*() calls.
While at it, add a physical address value to the
Em Mon, Feb 08, 2021 at 07:25:32AM -0800, kan.li...@linux.intel.com escreveu:
> From: Jin Yao
>
> For hardware events, they have pre-defined configs. The kernel
> needs to know where the event comes from (e.g. from cpu_core pmu
> or from cpu_atom pmu). But the perf type 'PERF_TYPE_HARDWARE'
>
Hi Jens, when you get a moment, could you take a quick look at this one for ack?
On Thu, Feb 4, 2021 at 11:49 AM Laurence Oberman wrote:
>
> On Thu, 2021-02-04 at 10:27 +0800, Ming Lei wrote:
> > On Mon, Feb 01, 2021 at 11:48:50AM -0500, David Jeffery wrote:
> > > When a stacked block device
On Mon, Feb 08, 2021 at 07:12:22PM +0100, Paolo Bonzini wrote:
> On 08/02/21 19:04, Sean Christopherson wrote:
> > > That said, the case where we saw MSR autoload as faster involved EFER, and
> > > we decided that it was due to TLB flushes (commit f6577a5fa15d, "x86, kvm,
> > > vmx: Always use
The cleanup patch broke a6xx_gmu_clear_oob, fix it by adding the missing
bitshift operation.
Fixes: 555c50a4a19b ("drm/msm: Clean up GMU OOB set/clear handling")
Signed-off-by: Jonathan Marek
---
drivers/gpu/drm/msm/adreno/a6xx_gmu.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff
Em Mon, Feb 08, 2021 at 07:25:24AM -0800, kan.li...@linux.intel.com escreveu:
> From: Jin Yao
>
> On hybrid platform, one event is available on one pmu
> (such as, cpu_core or cpu_atom).
>
> This patch saves the pmu name to the pmu field of struct perf_pmu_alias.
> Then next we can know the pmu
On Mon, Feb 08, 2021 at 07:09:47PM +0200, Ioana Ciornei wrote:
> From: Dan Carpenter
>
> The "desc" pointer can't possibly be NULL here. If we can't find the
> correct "desc" then tt points to the last element of the
> fsl_mc_accepted_cmds[] array. Fix this by testing if
> "i ==
On Mon, Feb 08, 2021 at 05:50:21PM +0200, Avi Kivity wrote:
On 05/02/2021 16.26, Greg Kroah-Hartman wrote:
I'm announcing the release of the 4.9.256 kernel.
This, and the 4.4.256 release are a little bit "different" than normal.
This contains only 1 patch, just the version bump from .255 to
Quoting Joe Perches (2021-02-06 21:06:54)
> On Sat, 2021-02-06 at 20:18 -0800, Stephen Boyd wrote:
> > A missing semicolon here causes my external display to stop working.
> > Indeed, missing the semicolon on the return statement leads to
> > dp_panel_update_tu_timings() not existing because the
On Mon, Feb 08, 2021 at 04:56:16PM +, Vincenzo Frascino wrote:
> When MTE async mode is enabled TFSR_EL1 contains the accumulative
> asynchronous tag check faults for EL1 and EL0.
>
> During the suspend/resume operations the firmware might perform some
> operations that could change the state
On Sat, Feb 06, 2021 at 11:08:30PM +0800, Leo Yan wrote:
> From: Suzuki K Poulose
>
> If the kernel is running at EL2, the pid of a task is exposed via VMID
> instead of the CONTEXTID. Add support for this in the perf tool.
>
> This patch respects user setting if user has specified any configs
On Mon, Feb 08, 2021 at 07:25:21PM +0100, Johannes Berg wrote:
On Mon, 2021-02-08 at 18:00 +, Sasha Levin wrote:
From: Johannes Berg
[ Upstream commit 55b6f763d8bcb5546997933105d66d3e6b080e6a ]
On ARCH=um, loading a module doesn't result in its constructors getting
called, which breaks
Em Mon, Feb 08, 2021 at 07:25:25AM -0800, kan.li...@linux.intel.com escreveu:
> From: Jin Yao
>
> We identify the cpu_core pmu and cpu_atom pmu by explicitly
> checking following files:
>
> For cpu_core, check:
> "/sys/bus/event_source/devices/cpu_core/cpus"
>
> For cpu_atom, check:
>
On Thu, 2021-02-04 at 11:43 -0500, Laurence Oberman wrote:
> On Thu, 2021-02-04 at 10:27 +0800, Ming Lei wrote:
> > On Mon, Feb 01, 2021 at 11:48:50AM -0500, David Jeffery wrote:
> > > When a stacked block device inserts a request into another block
> > > device
> > > using
On Feb 8, 2021, at 04:33, Borislav Petkov wrote:
> On Wed, Dec 23, 2020 at 07:57:04AM -0800, Chang S. Bae wrote:
>> init_fpstate is used to record the initial xstate value for convenience
>
> convenience?
Yes, this is vague. I think the usage is when (re-)initializing the register
states, e.g.
On Mon, Feb 08, 2021 at 10:50:07AM -0800, Yu, Yu-cheng wrote:
> I have not run into the situation. Initially it was there because other
> faults have it.
Which other faults?
> When you asked, I went through it and put out my reasoning.
What does that mean?
> I think it still makes sense to
On Fri, Feb 5, 2021 at 4:09 PM Daniel Latypov wrote:
>
> When using `kunit.py run` to run tests, users must populate a
> `kunitconfig` file to select the options the tests are hidden behind and
> all their dependencies.
>
> The patch [1] to allow specifying a path to kunitconfig promises to make
On Mon, 2021-02-08 at 18:40 +0100, Mauro Carvalho Chehab wrote:
> Em Mon, 08 Feb 2021 13:57:56 -0300
> Ezequiel Garcia escreveu:
>
> > On Mon, 2021-02-08 at 18:46 +0200, Sakari Ailus wrote:
> > > Hi Ezequiel,
> > >
> > > Thanks for addressing this.
> > >
> > > On Mon, Feb 08, 2021 at
On Fri, Feb 05, 2021 at 01:14:11PM -0500, Peter Xu wrote:
> But I do have a question on why dax as the only user needs to pass in the
> notifier to follow_pte() for initialization.
Not sure either, why does DAX opencode something very much like
page_mkclean() with dax_entry_mkclean()?
Also it
From: "Maciej S. Szmigiero"
When retpolines are enabled they have high overhead in the inner loop
inside kvm_handle_hva_range() that iterates over the provided memory area.
Let's mark this function and its TDP MMU equivalent __always_inline so
compiler will be able to change the call to the
On Sun, 07 Feb 2021 18:20:14 -0800 syzbot wrote:
> Hello,
>
> syzbot found the following issue on:
>
> HEAD commit:e93fac3b drivers: net: xen-netfront: Simplify the calculat..
> git tree: net-next
> console output: https://syzkaller.appspot.com/x/log.txt?x=160930c4d0
> kernel
On 2/8/2021 10:20 AM, Borislav Petkov wrote:
On Fri, Feb 05, 2021 at 10:00:21AM -0800, Yu, Yu-cheng wrote:
The ratelimit here is only for #CP, and its rate is not counted together
with other types of faults. If a task gets here, it will exit. The only
condition the ratelimit will trigger is
On Mon, 8 Feb 2021 at 19:40, Andrey Konovalov wrote:
>
> Currently, whether the alloc/free stack traces collection is enabled by
> default for hardware tag-based KASAN depends on CONFIG_DEBUG_KERNEL.
> The intention for this dependency was to only enable collection on slow
> debug kernels due to
On Mon, Feb 08, 2021 at 12:21:22PM -0600, Bjorn Andersson wrote:
> On Sat 06 Feb 13:47 CST 2021, Geert Uytterhoeven wrote:
>
> > Hi Arnd,
> >
> > On Sat, Feb 6, 2021 at 3:36 PM Arnd Bergmann wrote:
> > > That said, I'm still not happy about the patch we discussed in the
> > > other email
Dear Guoqing,
On 08.02.21 15:53, Guoqing Jiang wrote:
On 2/8/21 12:38, Donald Buczek wrote:
5. maybe don't hold reconfig_mutex when try to unregister sync_thread, like
this.
/* resync has finished, collect result */
mddev_unlock(mddev);
On Mon, 8 Feb 2021 17:19:28 +0530, Bhaskar Chowdhury wrote:
> s/provied/provided/
Applied to
https://git.kernel.org/pub/scm/linux/kernel/git/broonie/spi.git for-next
Thanks!
[1/1] include: linux: spi: Change provied to provided in the file spi.h
commit:
On Sun, 7 Feb 2021 11:09:50 +0800, Leilk Liu wrote:
> Some controllers only have one HW CS, if support multiple devices, other
> devices need
> to use SW CS.
> This patch adds the support of both HW and SW CS via cs_gpio.
>
> leilk.liu (3):
> spi: add power control when set_cs_timing
> spi:
Currently, whether the alloc/free stack traces collection is enabled by
default for hardware tag-based KASAN depends on CONFIG_DEBUG_KERNEL.
The intention for this dependency was to only enable collection on slow
debug kernels due to a significant perf and memory impact.
As it turns out,
On Sun, 7 Feb 2021 14:14:14 +0800, Hsin-Hsiung Wang wrote:
> This patch series adds support for MediaTek PMIC MT6315 regulator driver,
> which adds MT6315 related buck voltage data to the driver.
> This series is based on below patch[1].
>
> [1]
On Mon, Feb 08, 2021 at 05:17:41PM +0100, Stefano Garzarella wrote:
> It's legal to have 'offset + len' equal to
> sizeof(struct virtio_net_config), since 'ndev->config' is a
> 'struct virtio_net_config', so we can safely copy its content under
> this condition.
>
> Fixes: 1a86b377aa21
On Mon, Feb 01, 2021 at 07:11:12PM -0500, Keno Fischer wrote:
> Hi Andrei,
>
> > This series introduces the PTRACE_O_ARM64_RAW_REGS option. If it is set,
> > PTRACE_GETREGSET returns values of all registers, and PTRACE_SETREGSET
> > allows to change any of them.
>
> thanks for picking this up. I
On Wed, 20 Jan 2021 22:49:52 +0100, Hans de Goede wrote:
> Here is v4 of my series to add support for Intel Bay Trail based devices
> which use a WM5102 codec for audio output/input.
>
> This was developed and tested on a Lenovo Yoga Tablet 1051L.
>
> The MFD and ASoC parts do not have any
On Sat, 6 Feb 2021 23:58:49 +0100, Rikard Falkeborn wrote:
> The only usage of these is to assign their address to the 'ops' field in
> the snd_soc_dai_driver struct, which is a pointer to const. Make them
> const to allow the compiler to put them in read-only memory.
Applied to
On Sun, 7 Feb 2021 23:06:56 +0530, Sameer Pujar wrote:
> This series renames exported functions from audio graph for a better
> global visibility. In doing so update the references in audio graph
> and Tegra audio graph card drivers.
>
>
> Changelog
> =
>
> [...]
Applied to
On Sat, 23 Jan 2021 14:09:56 +, Paul Cercueil wrote:
> Add the ingenic,jz4760b-codec and ingenic,jz4760-codec compatible
> strings.
>
> In the process, convert the previous compatible strings to use an enum
> instead.
Applied to
Hi Sebastian,
On Mon, Feb 8, 2021 at 6:59 PM Sebastian Andrzej Siewior
wrote:
>
> charlcd_write() is invoked as a VFS->write() callback and as such it is
> always invoked from preemptible context and may sleep.
>
> charlcd_puts() is invoked from register/unregister callback which is
>
On Tue, Feb 09, 2021 at 01:10:02AM +0900, Hector Martin wrote:
> On 08/02/2021 19.54, Krzysztof Kozlowski wrote:
> > > +enum s3c24xx_irq_type {
> > > + IRQ_DISCRETE = 0,
> > > + IRQ_S3C6400 = 1,
> > > + IRQ_APPLE = 2,
> >
> > It seems you add the third structure to differentiate type of UART.
> >
Hi!
> This is the start of the stable review cycle for the 4.19.175 release.
> There are 38 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.
>
> Responses should be made by Wed, 10 Feb 2021 14:57:55
Hi!
> This is the start of the stable review cycle for the 4.4.257 release.
> There are 38 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.
>
> Responses should be made by Wed, 10 Feb 2021 14:57:55
On Mon 2021-02-08 15:59:47, Greg Kroah-Hartman wrote:
> This is the start of the stable review cycle for the 5.10.15 release.
> There are 120 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.
>
>
On Thu, Feb 04, 2021 at 03:36:15PM +, Will Deacon wrote:
> On Mon, Feb 01, 2021 at 11:40:11AM -0800, Andrei Vagin wrote:
> > We have some ABI weirdness in the way that we handle syscall
> > exit stops because we indicate whether or not the stop has been
> > signalled from syscall entry or
On Mon, Feb 08, 2021 at 09:14:28AM +0100, David Hildenbrand wrote:
> People are constantly struggling with the effects of long term pinnings
> under user space control, like we already have with vfio and RDMA.
>
> And here we are, adding yet another, easier way to mess with core MM in the
> same
On Mon, Feb 08, 2021 at 03:44:54PM +0100, Stefano Garzarella wrote:
> If the socket is closed or is being released, some resources used by
> virtio_transport_space_update() such as 'vsk->trans' may be released.
>
> To avoid a use after free bug we should only update the available credit
> when we
On Mon, Feb 08, 2021 at 11:58:02PM +0530, Mukul Mehar wrote:
> >From 29bcaf0066003983da29b1e026b985c0727b091a Mon Sep 17 00:00:00 2001
> From: Mukul Mehar
> Date: Mon, 8 Feb 2021 01:03:06 +0530
> Subject: [PATCH] Drivers: staging: most: sound: Fixed style issue.
>
> This patch fixes a warning,
>From 29bcaf0066003983da29b1e026b985c0727b091a Mon Sep 17 00:00:00 2001
From: Mukul Mehar
Date: Mon, 8 Feb 2021 01:03:06 +0530
Subject: [PATCH] Drivers: staging: most: sound: Fixed style issue.
This patch fixes a warning, of the line ending with a '(',
generated by checkpatch.pl.
This is my
On Wed, Dec 30, 2020 at 01:05:15PM +0100, Nadeem Athani wrote:
> Cadence controller will not initiate autonomous speed change if strapped
> as Gen2. The Retrain Link bit is set as quirk to enable this speed change.
>
> Signed-off-by: Nadeem Athani
> ---
>
On 2/8/2021 7:09 PM, Ioana Ciornei wrote:
> From: Ioana Ciornei
>
> This patch set adds a fix on the userspace support of the fsl-mc bus.
> Other than that, a missing device type is added and some other commands
> to the list of the accepted ones.
>
> Dan Carpenter (1):
> bus: fsl-mc: Fix
On Mon, 2021-02-08 at 18:00 +, Sasha Levin wrote:
> From: Johannes Berg
>
> [ Upstream commit 55b6f763d8bcb5546997933105d66d3e6b080e6a ]
>
> On ARCH=um, loading a module doesn't result in its constructors getting
> called, which breaks module gcov since the debugfs files are never
>
On 08/02/21 17:21, Vincent Guittot wrote:
> On Thu, 28 Jan 2021 at 19:32, Valentin Schneider
> wrote:
>>
>> Misfit tasks can and will be preempted by the stopper to migrate them over
>> to a higher-capacity CPU. However, when runnable but not current misfit
>> tasks are scanned by the load
Quoting AngeloGioacchino Del Regno (2021-01-14 14:10:59)
> The GPU PLL0 is not a fixed PLL and the rate can be set on it:
> this is necessary especially on boards which bootloader is setting
> a very low rate on this PLL before booting Linux, which would be
> unsuitable for postdividing to reach
Quoting AngeloGioacchino Del Regno (2021-01-14 14:10:59)
> The GPU PLL0 is not a fixed PLL and the rate can be set on it:
> this is necessary especially on boards which bootloader is setting
> a very low rate on this PLL before booting Linux, which would be
> unsuitable for postdividing to reach
Quoting AngeloGioacchino Del Regno (2021-01-14 14:10:58)
> The GPU GX GDSC has GPU_GX_BCR reset and gfx3d_clk CXC, as stated
> on downstream kernels (and as verified upstream, because otherwise
> random lockups happen).
> Also, add PWRSTS_RET and NO_RET_PERIPH: also as found downstream,
> and also
On Sat 06 Feb 13:47 CST 2021, Geert Uytterhoeven wrote:
> Hi Arnd,
>
> On Sat, Feb 6, 2021 at 3:36 PM Arnd Bergmann wrote:
> > That said, I'm still not happy about the patch we discussed in the
> > other email thread[1] and I'd like to handle it a little more strictly in
> > the future, but I
Quoting AngeloGioacchino Del Regno (2021-01-14 14:10:57)
> This GDSC enables (or cuts!) power to the Multimedia Subsystem IOMMU
> (mmss smmu), which has bootloader pre-set secure contexts.
> In the event of a complete power loss, the secure contexts will be
> reset and the hypervisor will crash
On Mon, Feb 08, 2021 at 09:46:11AM -0800, Stephen Boyd wrote:
> Quoting Manivannan Sadhasivam (2021-01-17 20:11:51)
> > Changes in v2:
> >
> > * Modified the max_register value as per the SDX55 IPC offset in mailbox
> > driver.
> >
> > Manivannan Sadhasivam (5):
> > dt-bindings: mailbox: Add
Quoting AngeloGioacchino Del Regno (2021-01-14 14:10:56)
> Hardware clock gating is supported on some of the clocks declared in
> there: ignoring that it does exist may lead to unstabilities on some
> firmwares.
> Add the HWCG registers where applicable to stop potential crashes.
>
> This was
Quoting AngeloGioacchino Del Regno (2021-01-14 14:10:55)
> The pixel and byte clocks rate should not be cached, as a VCO shutdown
> may clear the frequency setup and this may not be set again due to the
> cached rate being present.
> This will also be useful when shadow clocks will be implemented
On Mon, Feb 08, 2021 at 05:07:14PM +, Leo Li wrote:
>
>
> > -Original Message-
> > From: Rob Herring
> > Sent: Monday, February 8, 2021 10:55 AM
> > To: Leo Li
> > Cc: linux-arm-ker...@lists.infradead.org; Oleksij Rempel > privat.de>; Rob Herring ; Krzysztof Kozlowski
> > ;
The following commit has been merged into the x86/urgent branch of tip:
Commit-ID: 2ade0d60939bcd54197c133b03b460fe62a4ec47
Gitweb:
https://git.kernel.org/tip/2ade0d60939bcd54197c133b03b460fe62a4ec47
Author:Jarkko Sakkinen
AuthorDate:Mon, 08 Feb 2021 00:14:01 +02:00
Quoting AngeloGioacchino Del Regno (2021-01-14 14:10:55)
> The pixel and byte clocks rate should not be cached, as a VCO shutdown
> may clear the frequency setup and this may not be set again due to the
> cached rate being present.
> This will also be useful when shadow clocks will be implemented
On Mon, Feb 08, 2021 at 05:50:07PM +, Christoph Hellwig wrote:
On Sun, Feb 07, 2021 at 11:13:52AM -0500, Sasha Levin wrote:
+ (u8)(LINUX_VERSION_MAJOR), (u8)(LINUX_VERSION_PATCHLEVEL),
+ (u16)(LINUX_VERSION_SUBLEVEL));
No need for the casts and braces.
Le 26/01/2021 à 11:16, Nicholas Piggin a écrit :
Excerpts from Christophe Leroy's message of January 26, 2021 12:48 am:
Only PPC64 has scv. No need to check the 0x7ff0 trap on PPC32.
And ignore the scv parameter in syscall_exit_prepare (Save 14 cycles
346 => 332 cycles)
Signed-off-by:
Quoting AngeloGioacchino Del Regno (2021-01-14 14:10:53)
> The GPU IOMMU depends on this clock and the hypervisor will crash
> the SoC if this clock gets disabled because the secure contexts
> that have been set on this IOMMU by the bootloader will become
> unaccessible (or they get reset).
> Mark
On 08/02/21 18:39, Christoph Hellwig wrote:
+int follow_pte(struct mm_struct *mm, unsigned long address,
+ pte_t **ptepp, spinlock_t **ptlp)
+{
+ return follow_invalidate_pte(mm, address, NULL, ptepp, NULL, ptlp);
+}
+EXPORT_SYMBOL_GPL(follow_pte);
I still don't think this
On Fri, Feb 05, 2021 at 10:00:21AM -0800, Yu, Yu-cheng wrote:
> The ratelimit here is only for #CP, and its rate is not counted together
> with other types of faults. If a task gets here, it will exit. The only
> condition the ratelimit will trigger is when multiple tasks hit #CP at once,
>
Quoting AngeloGioacchino Del Regno (2021-01-14 14:10:54)
> All of the GPLLs in the MSM8998 Global Clock Controller are Fabia PLLs
> and not generic alphas: this was producing bad effects over the entire
> clock tree of MSM8998, where any GPLL child clock was declaring a false
> clock rate, due to
Quoting AngeloGioacchino Del Regno (2021-01-14 14:10:52)
> To achieve CPR-Hardened functionality this clock must be on: add it
> in order to be able to get it managed by the CPR3 driver.
>
> Signed-off-by: AngeloGioacchino Del Regno
>
> ---
Applied to clk-next
Quoting AngeloGioacchino Del Regno (2021-01-14 14:10:51)
> Add new clock definition to gcc-msm8998 dt-bindings
>
> Signed-off-by: AngeloGioacchino Del Regno
>
> ---
Applied to clk-next
Quoting AngeloGioacchino Del Regno (2021-01-14 14:10:50)
> This clock enables the GPLL0 output to the multimedia subsystem
> clock controller.
>
> Signed-off-by: AngeloGioacchino Del Regno
>
> ---
Applied to clk-next
Quoting AngeloGioacchino Del Regno (2021-01-14 14:10:49)
> Add new clock definition to gcc-msm8998 dt-bindings.
>
> Signed-off-by: AngeloGioacchino Del Regno
>
> ---
Applied to clk-next
Quoting AngeloGioacchino Del Regno (2021-01-14 14:10:53)
> The GPU IOMMU depends on this clock and the hypervisor will crash
> the SoC if this clock gets disabled because the secure contexts
> that have been set on this IOMMU by the bootloader will become
> unaccessible (or they get reset).
> Mark
On Sun, Feb 07, 2021 at 03:24:02PM +0800, Chengming Zhou wrote:
> The FULL state doesn't exist for the CPU resource at the system level,
> but exist at the cgroup level, means all non-idle tasks in a cgroup are
> delayed on the CPU resource which used by others outside of the cgroup.
>
>
From: "Ahmed S. Darwish"
The usage of in_interrupt() in drivers is phased out for various
reasons.
In both exported functions where BUG_ON(in_interrupt()) is invoked,
there is a mutex_lock() afterwards. mutex_lock() contains a
might_sleep() which will already trigger a stack trace if the target
On Mon, Feb 8, 2021 at 1:08 AM Yanan Wang wrote:
>
> Add a macro to get string of the backing source memory type, so that
> application can add choices for source types in the help() function,
> and users can specify which type to use for testing.
Coincidentally, I sent out a change last week to
On Fri, Feb 05, 2021 at 11:42:11AM +1100, Alexey Kardashevskiy wrote:
> > A real nvswitch function?
>
> What do you mean by this exactly? The cpu side of nvlink is "emulated pci
> devices", the gpu side is not in pci space at all, the nvidia driver manages
> it via the gpu's mmio or/and cfg
601 - 700 of 2121 matches
Mail list logo
