The BQ256XX family of devices are highly integrated buck chargers
for single cell batteries.
Signed-off-by: Ricardo Rivera-Matos
---
drivers/power/supply/Kconfig | 11 +
drivers/power/supply/Makefile |1 +
drivers/power/supply/bq256xx_charger.c | 1769
From: Vineeth Pillai
Hotplug fixes to core-scheduling require a new cpumask iterator
which iterates through all online cpus in both the given cpumasks.
This patch introduces it.
Signed-off-by: Vineeth Pillai
Signed-off-by: Joel Fernandes (Google)
---
include/linux/cpumask.h | 42
From: Peter Zijlstra
Introduce the basic infrastructure to have a core wide rq->lock.
Signed-off-by: Peter Zijlstra (Intel)
Signed-off-by: Julien Desfossez
Signed-off-by: Vineeth Remanan Pillai
---
kernel/Kconfig.preempt | 6 +++
kernel/sched/core.c| 95
From: Peter Zijlstra
Introduce task_struct::core_cookie as an opaque identifier for core
scheduling. When enabled; core scheduling will only allow matching
task to be on the core; where idle matches everything.
When task_struct::core_cookie is set (and core scheduling is enabled)
these tasks
From: Peter Zijlstra
Because sched_class::pick_next_task() also implies
sched_class::set_next_task() (and possibly put_prev_task() and
newidle_balance) it is not state invariant. This makes it unsuitable
for remote task selection.
Signed-off-by: Peter Zijlstra (Intel)
Signed-off-by: Vineeth
From: Peter Zijlstra
In preparation of playing games with rq->lock, abstract the thing
using an accessor.
Signed-off-by: Peter Zijlstra (Intel)
Signed-off-by: Vineeth Remanan Pillai
Signed-off-by: Julien Desfossez
---
kernel/sched/core.c | 46 +-
kernel/sched/cpuacct.c
From: Vineeth Pillai
Hotplug fixes to core-scheduling require a new bitops API.
Introduce a new API find_next_or_bit() which returns the
bit number of the next set bit in OR-ed bit masks of the
given bit masks.
Signed-off-by: Vineeth Pillai
Signed-off-by: Joel Fernandes (Google)
---
From: Peter Zijlstra
Signed-off-by: Peter Zijlstra (Intel)
---
kernel/sched/fair.c | 12 ++--
1 file changed, 10 insertions(+), 2 deletions(-)
diff --git a/kernel/sched/fair.c b/kernel/sched/fair.c
index 1a1bf726264a..af8c40191a19 100644
--- a/kernel/sched/fair.c
+++
Seventh iteration of the Core-Scheduling feature.
(Note that this iteration is a repost of the combined v6 and v6+ series,
and does not include the new interface discussed at LPC).
Core scheduling is a feature that allows only trusted tasks to run
concurrently on cpus sharing compute resources
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
acpi-5.9-rc3
with top-most commit 4f31d53c21ec98a2c8973cff759804bd1c217c93
Merge branch 'acpi-mm'
on top of commit 9123e3a74ec7b934a4a099e98af6a61c2f80bbf5
Linux 5.9-rc1
to receive
Hi Linus,
Please pull from the tag
git://git.kernel.org/pub/scm/linux/kernel/git/rafael/linux-pm.git \
pm-5.9-rc3
with top-most commit ef7d960403ecd87276e12b69c26bf0fdd5f21a0e
Merge branch 'pm-cpufreq'
on top of commit d012a7190fc1fd72ed48911e77ca97ba4521bccd
Linux 5.9-rc2
to receive
On Tue, Jul 28, 2020 at 4:08 AM Kevin Tang wrote:
>
> From: Kevin Tang
>
> The Unisoc DRM master device is a virtual device needed to list all
> DPU devices or other display interface nodes that comprise the
> graphics subsystem
>
> Cc: Orson Zhai
> Cc: Chunyan Zhang
> Signed-off-by: Kevin
On Wed, Aug 26, 2020 at 12:54 PM Mark Brown wrote:
>
> On Wed, Aug 26, 2020 at 12:48:49PM -0600, Rob Herring wrote:
> > The binding was added in 2013 and has had no driver since 2015.
>
> There is the hdmi-codec driver that covers such hardware and would be
> compatible with the binding. Of
On 8/28/20 6:05 AM, Andre Przywara wrote:
> This is an attempt to convert the SP805 watchdog DT binding to yaml.
> This is done in the first patch, the remaining nine fix some DT users.
>
> I couldn't test any of those DT files on actual machines, but tried
> to make the changes in a way that
On 8/28/20 6:05 AM, Andre Przywara wrote:
> The SP805 binding sets the name for the actual watchdog clock to
> "wdog_clk" (with an underscore).
>
> Change the name in the DTs for Broadcom platforms to match that. The
> Linux and U-Boot driver use the *first* clock for this purpose anyway,
> so it
> -Original Message-
> From: Masami Hiramatsu
>
> @@ -1311,24 +1257,23 @@ void kprobe_busy_end(void)
> void kprobe_flush_task(struct task_struct *tk)
> {
> struct kretprobe_instance *ri;
> - struct hlist_head *head;
> - struct hlist_node *tmp;
> - unsigned
On 8/28/20 6:06 AM, Andre Przywara wrote:
> The SP805 binding sets the name for the actual watchdog clock to
> "wdog_clk" (with an underscore).
>
> Change the name in the DTs for the Broadcom NSP platform to match that.
> The Linux and U-Boot driver use the *first* clock for this purpose
>
On 8/28/20 6:06 AM, Andre Przywara wrote:
> The SP805 DT binding requires two clocks to be specified, but the
> Broadcom Cygnus DT currently only specifies one clock.
>
> In practice, Linux would pick a clock named "apb_pclk" for the bus
> clock, and the Linux and U-Boot SP805 driver would use
On Wed, Aug 19, 2020 at 09:50:06AM -0500, Josh Poimboeuf wrote:
> The x86 uaccess code uses barrier_nospec() in various places to prevent
> speculative dereferencing of user-controlled pointers (which might be
> combined with further gadgets or CPU bugs to leak data).
>
> There are some issues
On 8/28/20 12:24 PM, Jens Axboe wrote:
> On 8/28/20 11:40 AM, Arnd Bergmann wrote:
>> On Mon, Jun 22, 2020 at 9:29 PM Minchan Kim wrote:
>>> So finally, the API is as follows,
>>>
>>> ssize_t process_madvise(int pidfd, const struct iovec *iovec,
>>>unsigned long vlen, int
From: Akshay Gupta
...because future AMD systems will support up to 64 MCA banks per CPU.
MAX_NR_BANKS is used to allocate a number of data structures, and it is
used as a ceiling for values read from MCG_CAP[Count]. Therefore, this
change will have no functional effect on existing systems with
On Fri, 28 Aug 2020 at 15:29, Paul E. McKenney wrote:
>
> On Fri, Aug 28, 2020 at 09:37:17AM +0200, Anders Roxell wrote:
> > On Wed, 26 Aug 2020 at 21:39, Paul E. McKenney wrote:
> > >
> > > On Wed, Aug 26, 2020 at 08:19:01PM +0200, Anders Roxell wrote:
> > > > On Wed, 26 Aug 2020 at 08:33,
On Fri, Aug 28, 2020 at 12:21:13PM +0200, Miroslav Benes wrote:
> > Hi there! I was trying to find a super easy way to address this, so I
> > thought the best thing would be if there were a compiler or linker
> > switch to just eliminate any duplicate symbols at compile time for
> > vmlinux. I
The PMIC node can be a clock provider (for its 32 kHz clock) and authors
of imx8mq-librem5-devkit.dts apparently wanted this because they added
input clock and clock-output-names.
Add necessary clock-cells to the PMIC node.
Signed-off-by: Krzysztof Kozlowski
---
Device tree schema expects NAND controller to be named
"nand-controller", otherwise dtbs_check complain with a warning like:
arch/arm/boot/dts/imx28-eukrea-mbmx283lc.dt.yaml: gpmi-nand@8000c000:
$nodename:0: 'gpmi-nand@8000c000' does not match
'^nand-controller(@.*)?'
Signed-off-by:
Device tree schema expects NAND controller to be named
"nand-controller", otherwise dtbs_check complain with a warning like:
arch/arm/boot/dts/imx28-eukrea-mbmx283lc.dt.yaml: gpmi-nand@8000c000:
$nodename:0: 'gpmi-nand@8000c000' does not match
'^nand-controller(@.*)?'
Signed-off-by:
Device tree schema expects NAND controller to be named
"nand-controller", otherwise dtbs_check complain with a warning like:
arch/arm/boot/dts/imx6dl-apf6dev.dt.yaml: gpmi-nand@112000:
$nodename:0: 'gpmi-nand@112000' does not match '^nand-controller(@.*)?'
Signed-off-by: Krzysztof
Most of Freescale/NXP GPMI device trees use size-cells==1 (even when
actually not needed except few boards). This fixes dtbs_check warnings
like:
arch/arm64/boot/dts/freescale/imx8mm-beacon-kit.dt.yaml:
nand-controller@33002000: #size-cells:0:0: 0 was expected
Signed-off-by: Krzysztof
Hey Andy, Linus,
Thanks for looking at this.
On 28/08/2020 11:09, Andy Shevchenko wrote:
On Fri, Aug 14, 2020 at 1:35 PM Thomas Preston
wrote:
- Fix a typo where mcp23x17 configs are referred to as mcp23x16.
I'm not sure it's correct. MPC23016 is an existing I²C IO expander.
The
Hi Maxime,
Am 28.08.20 um 17:25 schrieb Maxime Ripard:
> Hi,
>
> On Fri, Aug 28, 2020 at 02:45:49PM +0200, Stefan Wahren wrote:
>> Am 28.08.20 um 08:30 schrieb Hoegeun Kwon:
>>> On 8/27/20 6:49 PM, Stefan Wahren wrote:
Am 27.08.20 um 06:35 schrieb Hoegeun Kwon:
> Hi Stefan,
>
>
Hi Luc,
On Fri, Aug 28, 2020 at 10:53 AM Luc Van Oostenryck
wrote:
>
> Hi Miguel,
>
> Could you also take this patch in your queue?
> It has already be sent twice but ignored by the other channels.
Yeah, no problem. However, what about all those emails from the test
bot? Is the bot using an old
On Fri, Aug 28, 2020 at 08:25:34PM +0200, Christian Brauner wrote:
> On Fri, Aug 28, 2020 at 8:24 PM Jens Axboe wrote:
> >
> > On 8/28/20 11:40 AM, Arnd Bergmann wrote:
> > > On Mon, Jun 22, 2020 at 9:29 PM Minchan Kim wrote:
> > >> So finally, the API is as follows,
> > >>
> > >> ssize_t
On Sat, Aug 29, 2020 at 03:37:26AM +0900, Masami Hiramatsu wrote:
> cd /sys/kernel/debug/tracing/
>
> echo r:schedule schedule >> kprobe_events
> echo 1 > events/kprobes/enable
>
> sleep 333
Thanks! that does indeed trigger it reliably. Let me go have dinner and
then I'll try and figure out
Hi Mani,
Thanks for the review!
On Fri, Aug 28, 2020 at 06:34:04PM +0530, Manivannan Sadhasivam wrote:
> On 0803, Cristian Ciocaltea wrote:
> > Atomic transfers are required to properly power off a machine through
> > an I2C controlled PMIC, such as the Actions Semi ATC260x series.
> >
> >
Hi,
I sent a v2 patch last night, thanks for all the comments here!
Adam
On Mon, Aug 24, 2020 at 11:04:12AM -0700, Kyung Min Park wrote:
> +If the expected flag does not appear in /proc/cpuinfo, things are murkier.
> +Users need to find out the reason why the flag is missing and find the way
> +how to enable it, which is not always easy. There are several factors that
On Thu, Aug 27 2020 at 09:17, Marc Zyngier wrote:
> On 2020-08-26 12:17, Thomas Gleixner wrote:
>> #ifdef CONFIG_GENERIC_MSI_IRQ_DOMAIN
>> +void msi_domain_set_default_info_flags(struct msi_domain_info *info)
>> +{
>> +/* Required so that a device latches a valid MSI message on startup
>> */
On Fri, Aug 28, 2020 at 08:29:24PM +0200, Rafael J. Wysocki wrote:
> CAUTION: This email originated from outside of the organization. Do not click
> links or open attachments unless you can confirm the sender and know the
> content is safe.
>
>
>
> On Fri, Aug 28, 2020 at 8:26 PM Anchal
Linus
On 8/27/20 5:58 PM, Linus Walleij wrote:
On Wed, Aug 12, 2020 at 9:50 PM Dan Murphy wrote:
Add the reg property to each channel node. This update is
to accommodate the multicolor framework. In addition to the
accommodation this allows the LEDs to be placed on any channel
and allow
On Fri, 28 Aug 2020 21:30:06 +0900
Masami Hiramatsu wrote:
> From: Peter Zijlstra
>
> The kretprobe hash is mostly superfluous, replace it with a per-task
> variable.
>
> This gets rid of the task hash and it's related locking.
>
> The whole invalidate_rp_inst() is tedious and could go away
On Mon, 2020-08-24 at 15:17 +1000, Alexey Kardashevskiy wrote:
>
> On 18/08/2020 09:40, Leonardo Bras wrote:
> > As of today, if the biggest DDW that can be created can't map the whole
> > partition, it's creation is skipped and the default DMA window
> > "ibm,dma-window" is used instead.
> >
>
From: Randy Dunlap
Fix build warning since this file is already listed in
include/asm-generic/Kbuild.
../scripts/Makefile.asm-generic:25: redundant generic-y found in
arch/microblaze/include/asm/Kbuild: hw_irq.h
Fixes: 7e8f54cd4e26 ("microblaze: Remove empty headers")
Signed-off-by: Randy
I think the original code complaining parsing error is there for a reason,
A better way is to modify ct_sip_parse_numerical_param() and let it return
a real parsing error code instead of returning FOUND(1) and NOT FOUND(0)
if deemed necessary
Once again I'm not an expert and I'm may suggest
On Thu, Aug 27 2020 at 13:20, Bjorn Helgaas wrote:
> On Wed, Aug 26, 2020 at 01:17:02PM +0200, Thomas Gleixner wrote:
>> Make the architectures and drivers which rely on them select them in Kconfig
>> and if not selected replace them by stub functions which emit a warning and
>> fail the PCI/MSI
On Fri, Aug 28, 2020 at 8:26 PM Anchal Agarwal wrote:
>
> On Fri, Aug 21, 2020 at 10:22:43PM +, Anchal Agarwal wrote:
> > Hello,
> > This series fixes PM hibernation for hvm guests running on xen hypervisor.
> > The running guest could now be hibernated and resumed successfully at a
> > later
On Fri, Aug 28, 2020 at 1:54 AM Chenyi Qiang wrote:
>
> A minor fix for the update of VM_EXIT_LOAD_IA32_PERF_GLOBAL_CTRL field
> in exit_ctls_high.
>
> Fixes: 03a8871add95 ("KVM: nVMX: Expose load IA32_PERF_GLOBAL_CTRL
> VM-{Entry,Exit} control")
> Signed-off-by: Chenyi Qiang
> Reviewed-by:
On Fri, Aug 21, 2020 at 10:22:43PM +, Anchal Agarwal wrote:
> Hello,
> This series fixes PM hibernation for hvm guests running on xen hypervisor.
> The running guest could now be hibernated and resumed successfully at a
> later time. The fixes for PM hibernation are added to block and
>
On Fri, Aug 28, 2020 at 8:24 PM Jens Axboe wrote:
>
> On 8/28/20 11:40 AM, Arnd Bergmann wrote:
> > On Mon, Jun 22, 2020 at 9:29 PM Minchan Kim wrote:
> >> So finally, the API is as follows,
> >>
> >> ssize_t process_madvise(int pidfd, const struct iovec *iovec,
> >>unsigned
On Fri, Aug 28, 2020 at 1:54 AM Chenyi Qiang wrote:
>
> When setting the nested VMX MSRs, verify it with the values in
> vmcs_config.nested_vmx_msrs, which reflects the global capability of
> VMX controls MSRs.
>
> Signed-off-by: Chenyi Qiang
You seem to have entirely missed the point of this
On 8/28/20 11:40 AM, Arnd Bergmann wrote:
> On Mon, Jun 22, 2020 at 9:29 PM Minchan Kim wrote:
>> So finally, the API is as follows,
>>
>> ssize_t process_madvise(int pidfd, const struct iovec *iovec,
>>unsigned long vlen, int advice, unsigned int flags);
>
> I had not
On Thu, Aug 27, 2020 at 10:20 AM Andy Shevchenko
wrote:
>
> On Tue, Aug 25, 2020 at 12:58 PM Serge Semin wrote:
> > On Sat, Aug 22, 2020 at 12:27:53PM +0800, Ding Tianhong wrote:
>
> > BTW Linus, could you take a look at my series? Andy and Rob have finished
> > reviewing
> > it almost a month
On 8/28/20 9:14 AM, Michał Mirosław wrote:
> dev_err_probe() prepends the message with an error code. Let's make it
> more readable by translating the code to a more recognisable symbol.
recognizable
>
> Fixes: a787e5400a1c ("driver core: add device probe log helper")
is this change really to
On Fri, Aug 28, 2020 at 02:14:48PM -0400, Tong Zhang wrote:
> Hi Pablo,
> I'm not an expert in this networking stuff.
> But from my point of view there's no point in checking if this
> condition is always true.
Understood.
> There's also no need of returning anything from the
>
On Thu, Aug 27, 2020 at 10:08 PM Krzysztof Kozlowski wrote:
>
> Common pattern of handling deferred probe can be simplified with
> dev_err_probe(). Less code and also it prints the error value.
>
> Signed-off-by: Krzysztof Kozlowski
> ---
> drivers/gpio/gpio-bcm-kona.c | 5 +
> 1 file
On Tue, 2020-08-25 at 14:23 +0200, Rasmus Villemoes wrote:
> On 25/08/2020 02.09, Joe Perches wrote:
> > If a file exists in git and checkpatch is used without the -f
> > flag for scanning a file, then checkpatch will scan the file
> > assuming it's a patch
[]
> > +sub git_is_single_file {
> > +
Hi Pablo,
I'm not an expert in this networking stuff.
But from my point of view there's no point in checking if this
condition is always true.
There's also no need of returning anything from the
ct_sip_parse_numerical_param()
if they are all being ignored like this.
On Fri, Aug 28, 2020 at 2:07
On Mon, Aug 24, 2020 at 10:54:26AM +0200, Joerg Roedel wrote:
> diff --git a/arch/x86/kernel/head_64.S b/arch/x86/kernel/head_64.S
> index 2b2e91627221..800053219054 100644
> --- a/arch/x86/kernel/head_64.S
> +++ b/arch/x86/kernel/head_64.S
> @@ -78,6 +78,14 @@ SYM_CODE_START_NOALIGN(startup_64)
>
On Sat, Aug 15, 2020 at 12:50:30PM -0400, Tong Zhang wrote:
> ct_sip_parse_numerical_param can only return 0 or 1, but the caller is
> checking parsing error using < 0
Is this are real issue in your setup or probably some static analysis
tool is reporting?
You are right that
On Fri, 28 Aug 2020 17:14:38 +0200, Jerome Brunet wrote:
> On g12 and following platforms, The first channel of record with more than
> 2 channels ends being placed randomly on an even channel of the output.
>
> On these SoCs, a bit was added to force the first channel to be placed at
> the
Hi Jagan.
On Fri, Aug 28, 2020 at 09:29:38PM +0530, Jagan Teki wrote:
> Add Ampire, AM-1280800N3TZQW-T00H 10.1" TFT LCD panel timings.
>
> Signed-off-by: Jagan Teki
> ---
> drivers/gpu/drm/panel/panel-simple.c | 28
> 1 file changed, 28 insertions(+)
>
> diff
Hi Kevin.
> >
> > Any specific reason why this is not a ports node like used by many other
> > display bindings?
> > In other words - I think this is too simple.
> We only support one display pipeline now, other interface, like
> DP(DisplayPort), HDMI...will be add later...
>
> ports:
>
Hi Kevin
> >
> > > +
> > > + drm->dev_private = sprd;
> > dev_private is deprecated. Alwyas use upclassing.
> dev_private is deprecated ? I see everyone is still using it, so it
> will be deprecated in the future?
It is deprecated - and a lot of drivers is in need up an update to get
away
On Thu, Aug 27, 2020 at 10:08:13PM +0800, YueHaibing wrote:
> Use ip_is_fragment() to simpify code.
Applied.
Hi Jagan,
I love your patch! Yet something to improve:
[auto build test ERROR on robh/for-next]
[also build test ERROR on drm-intel/for-linux-next drm-tip/drm-tip linus/master
v5.9-rc2 next-20200828]
[If your patch is applied to the wrong git tree, kindly drop us a note.
And when submitting
On Fri, Aug 28, 2020 at 04:38:25PM +0100, Al Viro wrote:
> On Fri, Aug 28, 2020 at 06:18:17AM -0700, syzbot wrote:
> > Hello,
> >
> > syzbot found the following issue on:
> >
> > HEAD commit:d012a719 Linux 5.9-rc2
> > git tree: upstream
> > console output:
Hi Robin,
Thanks for the review. Please find my comment below inline.
> -Original Message-
> From: Robin Murphy
> Sent: Friday, August 28, 2020 12:17 AM
> To: Manish Narani ; gre...@linuxfoundation.org;
> robh...@kernel.org; Michal Simek ; ba...@kernel.org;
> p.za...@pengutronix.de
>
On Fri, 2020-08-28 at 11:39 +0200, Peter Rosin wrote:
> On 2020-08-28 09:03, Krzysztof Kozlowski wrote:
> > > > If there is no consensus among discussing people, I find this 100 line
> > > > more readable, already got review, checkpatch accepts it so if subsystem
> > > > maintainer likes it, I
On Tue, Aug 25, 2020 at 02:23:05PM +0800, Feng Tang wrote:
> Also one good news is, we seem to identify the 2 key percpu variables
> out of the list mentioned in previous email:
> 'arch_freq_scale'
> 'tsc_adjust'
>
> These 2 variables are accessed in 2 hot call stacks (for this 288
Hi,
On Wed, Jul 29, 2020 at 11:49:13AM +0100, Jack Mitchell wrote:
> Signed-off-by: Jack Mitchell
> ---
^ missing long description
Also the patch does not apply and needs to be rebased.
-- Sebastian
> drivers/power/supply/axp20x_battery.c | 39 +++
> 1 file changed,
On Fri, Aug 28, 2020 at 10:39 AM Andy Lutomirski wrote:
>
> On Fri, Aug 28, 2020 at 4:38 AM H.J. Lu wrote:
> >
> > On Thu, Aug 27, 2020 at 11:24 PM Florian Weimer wrote:
> > >
> > > * H. J. Lu:
> > >
> > > > Can you think of ANY issues of passing more arguments to arch_prctl?
> > >
> > > On
On 28/08/2020 01:46, Chun-Kuang Hu wrote:
Hi, Frank:
Matthias Brugger 於 2020年8月27日 週四 下午10:28寫道：
On 27/08/2020 15:41, Frank Wunderlich wrote:
Hi Matthias,
any opinions about the dts-changes?
they look good to me.
maybe series except the tmds-Patch get merged...so i add it only to
On 8/27/20 4:50 PM, Thiago Jung Bauermann wrote:
Lakshmi Ramasubramanian writes:
@@ -63,7 +29,22 @@ void remove_ima_buffer(void *fdt, int chosen_node)
if (!prop)
return;
- ret = do_get_kexec_buffer(prop, len, , );
+ ret = fdt_address_cells(fdt, chosen_node);
Hi Nicolas,
On Wed, Aug 19, 2020 at 08:24:33PM +0200, Nicolas Saenz Julienne wrote:
> There is no benefit in splitting the 32-bit address space into two
> distinct DMA zones when the 30-bit address space isn't even available on
> a device. If that is the case, default to one big ZONE_DMA spanning
On Fri, Aug 28, 2020 at 1:54 AM Chenyi Qiang wrote:
>
> KVM supports the nested VM_{EXIT, ENTRY}_LOAD_IA32_PERF_GLOBAL_CTRL and
> VM_{ENTRY_LOAD, EXIT_CLEAR}_BNDCFGS, but they doesn't expose during
> the setup of nested VMX controls MSR.
>
Aren't these features added conditionally in
Hi,
On Wed, Jun 24, 2020 at 06:56:28PM +0300, Iskren Chernev wrote:
> Rewrite i2c operations from i2c client read/write to regmap i2c. As
> a result, most private functions now accept the private driver data
> instead of an i2c client pointer.
>
> Signed-off-by: Iskren Chernev
> ---
This still
On Thu, 27 Aug 2020 at 19:20, Johnny Chuang wrote:
>
> This patch adds a new behavior to report touch major resolution
> based on information provided by firmware.
>
> In initial process, driver acquires touch information from touch ic.
> It contains one byte about the resolution value of
On 8/27/20 6:23 PM, Thiago Jung Bauermann wrote:
Lakshmi Ramasubramanian writes:
+/**
+ * ima_get_kexec_buffer - get IMA buffer from the previous kernel
+ * @addr: On successful return, set to point to the buffer contents.
+ * @size: On successful return, set to the buffer size.
+
Building the Rockchip saradc driver can trigger the following error if the
driver is compiled into the kernel, but the IIO triggered buffer is not:
aarch64-linux-gnu-ld: drivers/iio/adc/rockchip_saradc.o: in function
`rockchip_saradc_probe':
/path/to/linux/drivers/iio/adc/rockchip_saradc.c:427:
On 8/27/20 4:35 PM, Thiago Jung Bauermann wrote:
Lakshmi Ramasubramanian writes:
The functions ima_get_kexec_buffer() and ima_free_kexec_buffer() that
handle carrying forward the IMA measurement logs on kexec for powerpc
do not have architecture specific code, but they are currently defined
On Mon, Jun 22, 2020 at 9:29 PM Minchan Kim wrote:
> So finally, the API is as follows,
>
> ssize_t process_madvise(int pidfd, const struct iovec *iovec,
>unsigned long vlen, int advice, unsigned int flags);
I had not followed the discussion earlier and only now came across
On Fri, Aug 28, 2020 at 4:38 AM H.J. Lu wrote:
>
> On Thu, Aug 27, 2020 at 11:24 PM Florian Weimer wrote:
> >
> > * H. J. Lu:
> >
> > > Can you think of ANY issues of passing more arguments to arch_prctl?
> >
> > On x32, the glibc arch_prctl system call wrapper only passes two
> > arguments to
From: Valentin Schneider
arch_scale_freq_invariant() is used by schedutil to determine whether
the scheduler's load-tracking signals are frequency invariant. Its
definition is overridable, though by default it is hardcoded to 'true'
if arch_scale_freq_capacity() is defined ('false' otherwise).
Now that the update of the FI scale factor is done in cpufreq core for
selected functions - target(), target_index() and fast_switch(),
we can provide feedback to the task scheduler and architecture code
on whether cpufreq supports FI.
For this purpose provide an external function to expose
The current frequency passed to arch_set_freq_scale() could end up
being 0, signaling an error in setting a new frequency. Also, if the
maximum frequency in 0, this will result in a division by 0 error.
Therefore, validate these input values before using them for the
setting of the frequency
Hi guys,
Please find here v4:
- addressing Viresh's comments on patches 1/5 and 3/5, and
- with his Acked-by applied for the rest of the patches;
- v3 can be found at [3], and
- this is based on linux-next 20200827.
Many thanks for the review,
Ionela.
---
v2->v3
- v2 can be found at [2]
From: Valentin Schneider
The passed cpumask arguments to arch_set_freq_scale() and
arch_freq_counters_available() are only iterated over, so reflect this
in the prototype. This also allows to pass system cpumasks like
cpu_online_mask without getting a warning.
Signed-off-by: Valentin Schneider
To properly scale its per-entity load-tracking signals, the task scheduler
needs to be given a frequency scale factor, i.e. some image of the current
frequency the CPU is running at. Currently, this scale can be computed
either by using counters (APERF/MPERF on x86, AMU on arm64), or by
Hi,
On Thu, May 14, 2020 at 04:04:25PM -0700, Jonathan Bakker wrote:
> Charger-manager is a virtual driver for unifying chargers, fuel gauges,
> extcon devices, and a thermal device into a battery management system.
>
> Unfortunately, it has been broken since commit 830ae442202e ("extcon:
>
On 28/08/2020 10:28, Andy Shevchenko wrote:
On Fri, Aug 28, 2020 at 11:06:21AM +0200, Linus Walleij wrote:
On Fri, Aug 14, 2020 at 12:04 PM Thomas Preston
wrote:
- Fix a typo where mcp23x17 configs are referred to as mcp23x16.
- Fix precious range to include INTCAP{A,B}, which clear on read.
From: Kan Liang
The Jasper Lake processor is also a Tremont microarchitecture. From the
perspective of perf MSR, there is nothing changed compared with
Elkhart Lake.
Share the code path with Elkhart Lake.
Signed-off-by: Kan Liang
---
arch/x86/events/msr.c | 1 +
1 file changed, 1 insertion(+)
From: Kan Liang
The Jasper Lake processor is also a Tremont microarchitecture. From the
perspective of Intel PMU, there is nothing changed compared with
Elkhart Lake.
Share the perf code with Elkhart Lake.
Signed-off-by: Kan Liang
---
arch/x86/events/intel/core.c | 1 +
1 file changed, 1
On Fri, 2020-07-24 at 12:35 -0700, Joe Perches wrote:
> These are almost all typos where the decimal length value
> should be after the % not before it.
Hey Jiri:
Is the trivial tree still alive?
Do you even look at this stuff anymore?
If not, you should probably just kill the tree
and your
On 28/08/2020 15:55, Dafna Hirschfeld wrote:
In list_add, the first variable is the new node and the second
is the list head. The function is called with a wrong order causing
NULL dereference:
[ 15.527030] Unable to handle kernel NULL pointer dereference at virtual
address
On 08/28/20 19:10, Dietmar Eggemann wrote:
> On 28/08/2020 12:27, Qais Yousef wrote:
> > On 08/28/20 10:00, vincent.donnef...@arm.com wrote:
> >> From: Vincent Donnefort
> >>
> >> rq->cpu_capacity is a key element in several scheduler parts, such as EAS
> >> task placement and load balancing.
Hi Linus,
Please pull the arm64 fixes below. Thanks.
The following changes since commit d012a7190fc1fd72ed48911e77ca97ba4521bccd:
Linux 5.9-rc2 (2020-08-23 14:08:43 -0700)
are available in the Git repository at:
git://git.kernel.org/pub/scm/linux/kernel/git/arm64/linux tags/arm64-fixes
arm-init is responsible for setting up efi runtime and doesn't actually
do any ARM specific stuff. RISC-V can use the same source code as it is.
Rename it to efi-init so that RISC-V can use it.
Signed-off-by: Atish Patra
Acked-by: Ard Biesheuvel
---
drivers/firmware/efi/Makefile
Extend the current page table dump support in RISC-V to include efi
pages as well.
Here is the output of efi runtime page table mappings.
---[ UEFI runtime start ]---
0x20002000-0x20003000 0xbe732000 4K PTE D A . . . W R V
0x20018000-0x20019000
Add a RISC-V architecture specific stub code that actually copies the
actual kernel image to a valid address and jump to it after boot services
are terminated. Enable UEFI related kernel configs as well for RISC-V.
Signed-off-by: Atish Patra
Link:
Linux kernel Image can appear as an EFI application With appropriate
PE/COFF header fields in the beginning of the Image header. An EFI
application loader can directly load a Linux kernel Image and an EFI
stub residing in kernel can boot Linux kernel directly.
Add the necessary PE/COFF header.
This patch adds EFI runtime service support for RISC-V.
Signed-off-by: Atish Patra
Acked-by: Ard Biesheuvel
---
arch/riscv/Kconfig | 2 +
arch/riscv/include/asm/efi.h| 20
arch/riscv/include/asm/mmu.h| 2 +
arch/riscv/include/asm/pgtable.h
201 - 300 of 1034 matches
Mail list logo
