On Wed, May 13, 2020 at 11:15 PM Mark Greer wrote:
>
> On Thu, May 07, 2020 at 11:29:11PM +0200, Alexandre Belloni wrote:
> > GREYBUS_AUDIO_MSM8994 is not an existing configuration option and as
> > reported in September 2016, it depends on an "out-of-tree qualcomm audio
> > driver". This driver
On Wed, May 13, 2020 at 9:00 AM Christoph Hellwig wrote:
>
> this series start cleaning up the safe kernel and user memory probing
> helpers in mm/maccess.c, and then allows architectures to implement
> the kernel probing without overriding the address space limit and
> temporarily allowing
On Wed, May 13, 2020 at 08:02:07PM +0100, Al Viro wrote:
> > https://lore.kernel.org/linux-fsdevel/20200507145924.ga28...@lst.de/T/#t
> >
> > which is waiting to be picked up [1], and also has some chance for conflicts
> > due to changes next to the access_ok.
> >
> > [1] except for the first
On Wed, May 13, 2020 at 9:01 AM Christoph Hellwig wrote:
>
> + arch_kernel_read(dst, src, type, err_label);\
I'm wondering if
(a) we shouldn't expose this as an interface in general
(b) it wouldn't be named differently..
The reason for (a) is that several users of
From: Oleksij Rempel
Date: Wed, 13 May 2020 14:34:40 +0200
> Add initial cable testing support.
> This PHY needs only 100usec for this test and it is recommended to run it
> before the link is up. For now, provide at least ethtool support, so it
> can be tested by more developers.
>
> This
On 5/13/2020 5:34 AM, Oleksij Rempel wrote:
> Add initial cable testing support.
> This PHY needs only 100usec for this test and it is recommended to run it
> before the link is up. For now, provide at least ethtool support, so it
> can be tested by more developers.
>
> This patch was tested
On Mon, 11 May 2020 at 05:49, Xiongfeng Wang wrote:
>
> When I cat module parameter 'dma_mode' by sysfs, it displays as follows.
> It is better to add a newline for easy reading.
>
> [root@hulk-202 ~]# cat /sys/module/tw686x/parameters/dma_mode
> memcpy[root@hulk-202 ~]#
>
> Signed-off-by:
On Wed, May 13, 2020 at 8:12 PM Wambui Karuga wrote:
>
>
>
> On Wed, 13 May 2020, Thomas Zimmermann wrote:
>
> > Hi
> >
> > Am 13.05.20 um 13:41 schrieb Wambui Karuga:
> >> Introduce the ability to track requests for the addition of drm debugfs
> >> files at any time and have them added all at
On 5/12/2020 3:47 AM, Stanley Chu wrote:
Currently UFS host driver promises VCC supply if UFS device
needs to do WriteBooster flush during runtime suspend.
However the UFS specification mentions,
"While the flushing operation is in progress, the device is
in Active power mode."
Therefore UFS
> > Do these registers all conform to the standard? Can we pull this code
> > out into a library which all standards conformant PHY drivers can use?
>
> According to opensig, this functionality should be present on all new T1 PHYs.
> But the register/bit layout is no specified as standard. At
On Wed, 13 May 2020 18:15:57 +0200
Sven Schnelle wrote:
> Thanks for looking into this. I've attached my /proc/config.gz to this Mail.
> The x86 system is my Laptop which is a Thinkpad X280 with 4 HT CPUs (so 8 cpus
> in total). I've tried disabling preemption, but this didn't help.
>
> It's
Hello Greg,
> From: stable-ow...@vger.kernel.org On
> Behalf Of Greg Kroah-Hartman
> Sent: 13 May 2020 10:44
>
> This is the start of the stable review cycle for the 4.19.123 release.
> There are 48 patches in this series, all will be posted as a response
> to this one. If anyone has any
On 13/05/2020 21.32, Andrew Morton wrote:
On Wed, 13 May 2020 17:05:25 +0300 Konstantin Khlebnikov
wrote:
Function isolate_migratepages_block() runs some checks out of lru_lock
when choose pages for migration. After checking PageLRU() it checks extra
page references by comparing page_count()
On Wed, May 13, 2020 at 12:11:27PM -0700, Linus Torvalds wrote:
> On Wed, May 13, 2020 at 9:01 AM Christoph Hellwig wrote:
> >
> > +static void bpf_strncpy(char *buf, long unsafe_addr)
> > +{
> > + buf[0] = 0;
> > + if (strncpy_from_kernel_nofault(buf, (void *)unsafe_addr,
> > +
On Tue 2020-05-12 14:47:13, Tony Lindgren wrote:
> Let's enable the TS 27.010 /dev/gsmmux* interfaces via Linux n_gsm that
> can be used for voice calls and SMS with commands using a custom Motorola
> format.
>
> And let's also enable the kernel GNSS driver via serdev-ngsm that uses a
> dedicated
On Tue 2020-05-12 14:47:10, Tony Lindgren wrote:
> For motorola modem case, we may have a GNSS device on channel 4.
> Let's add that to the binding and example.
>
> Signed-off-by: Tony Lindgren
Reviewed-by: Pavel Machek
BTW it looks like Alan's email address no longer works.
: host
On Tue 2020-05-12 14:47:08, Tony Lindgren wrote:
> We can make use of serdev drivers to do simple device drivers for
> TS 27.010 chanels, and we can handle vendor specific protocols on top
> of TS 27.010 with serdev drivers.
>
> So far this has been tested with Motorola droid4 where there is a
From: Martin Blumenstingl
Date: Tue, 12 May 2020 23:10:55 +0200
> The Ethernet TX performance has been historically bad on Meson8b and
> Meson8m2 SoCs because high packet loss was seen. I found out that this
> was related (yet again) to the RGMII TX delay configuration.
> In the process of
Hi Vinod,
Few high-level comments:
- handful of functions always return 0 and the return value is never
checked - switch to return void
- annotate all (nearly) arrays as static const
- consistently use multi_reg_write - in some cases non-const array
will be fine, overwriting a few entries as
Split be_hw_params_fixup function for different codecs as current common
function, leads to crash while trying to get snd_soc_dpcm with
container_of() macro in kabylake_ssp_fixup().
The crash call path looks as below:
soc_pcm_hw_params()
snd_soc_dai_hw_params(codec_dai, substream, _params);
On 2020-05-13 12:03 p.m., Mimi Zohar wrote:
On Wed, 2020-05-13 at 11:53 -0700, Scott Branden wrote:
Hi Mimi,
On 2020-05-13 11:39 a.m., Mimi Zohar wrote:
[Cc'ing linux-security-module, linux-integrity]
On Thu, 2020-05-07 at 17:27 -0700, Scott Branden wrote:
Add kernel_pread_file* support
On 5/13/2020 12:06 PM, Roelof Berg wrote:
> Microchip lan7431 is frequently connected to a phy. However, it
> can also be directly connected to a MII remote peer without
> any phy in between. For supporting such a phyless hardware setup
> in Linux we added the capability to the driver to
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 4c74d51dab3dd655062a4740af150c1835e19cff
Gitweb:
https://git.kernel.org/tip/4c74d51dab3dd655062a4740af150c1835e19cff
Author:Vitaly Kuznetsov
AuthorDate:Tue, 28 Apr 2020 11:38:23 +02:00
Fix flag in PCIe controllers device-tree nodes 'ranges' property to correctly
represent 64-bit resources.
Signed-off-by: Vidya Sagar
---
arch/arm64/boot/dts/nvidia/tegra194.dtsi | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/arch/arm64/boot/dts/nvidia/tegra194.dtsi
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: fad1940a6a856f59b073e8650e02052ce531154c
Gitweb:
https://git.kernel.org/tip/fad1940a6a856f59b073e8650e02052ce531154c
Author:Vitaly Kuznetsov
AuthorDate:Tue, 28 Apr 2020 11:38:22 +02:00
This patch will add indentation to multiline variable and put
obj-$(CONFIG_X) at the beginning of the file. This order of variables is
used in other drives, so this will make vt665x Makefiles fit into the
pattern.
Indentation is fixed in vt6655/Makefile.
Order of variable declaration is changed
This patch is removing definition of CFLAGS in Makefile of vt6656 and
vt6655, as those are defining macros that are not used. This will remove
undef of one macro from vt6655/device_main.c, as it is only undef and it is
not used anywhere else, so it is safe to remove it.
Macros are removed from
This patchset will remove unused definitions of C Macros, reorder variable
definition in Makefiles and increase indentation to match visual block.
Macros are removed from vt665x/Makefile and vt6655/device_main.c.
Indentation is fixed in vt6655/Makefile.
Order of variable declaration is changed
The following commit has been merged into the x86/entry branch of tip:
Commit-ID: 82ff351052bcc4bf49dc966960f563d25f54d22b
Gitweb:
https://git.kernel.org/tip/82ff351052bcc4bf49dc966960f563d25f54d22b
Author:Vitaly Kuznetsov
AuthorDate:Tue, 28 Apr 2020 11:38:24 +02:00
Corrected error handling goto sequnece. Level put_pages should
be called when pinned pages >= 0 && pinned != npages. Level
free_pages should be called when pinned pages < 0.
Signed-off-by: Souptick Joarder
---
drivers/fpga/dfl-afu-dma-region.c | 4 ++--
1 file changed, 2 insertions(+), 2
On Tue, May 12, 2020 at 8:25 PM Navid Emamdoost
wrote:
> I found this via static analysis and as a result, did had the inputs
> to test it with (like the way fuzzing works).
Fuzzing is dynamic analysis, so I'm not sure how that fits.
> It may be beneficial if you could point me to any testing
>
On Wed, May 13, 2020 at 9:01 AM Christoph Hellwig wrote:
>
> +static void bpf_strncpy(char *buf, long unsafe_addr)
> +{
> + buf[0] = 0;
> + if (strncpy_from_kernel_nofault(buf, (void *)unsafe_addr,
> + BPF_STRNCPY_LEN))
> +
to specify the
base tree in git format-patch, please see https://stackoverflow.com/a/37406982]
url:
https://github.com/0day-ci/linux/commits/Shijie-Hu/hugetlbfs-Get-unmapped-area-below-TASK_UNMAPPED_BASE-for-hugetlbfs/20200513-221024
base: https://git.kernel.org/pub/scm/linux/kernel/git
From: Christoph Hellwig
Date: Wed, 13 May 2020 08:26:15 +0200
> Hi Dave,
>
> this series removes the kernel_setsockopt and kernel_getsockopt
> functions, and instead switches their users to small functions that
> implement setting (or in one case getting) a sockopt directly using
> a normal
Hi!
> Here's the updated set of these patches fixed up for Johan's and
> Pavel's earlier comments.
>
> This series does the following:
>
> 1. Adds functions to n_gsm.c for serdev-ngsm.c driver to use
>
> 2. Adds a generic serdev-ngsm.c driver that brings up the TS 27.010
>TTY ports
On Wed 13 May 04:12 PDT 2020, Rajendra Nayak wrote:
> geni spi needs to express a perforamnce state requirement on CX
> depending on the frequency of the clock rates. Use OPP table from
> DT to register with OPP framework and use dev_pm_opp_set_rate() to
> set the clk/perf state.
>
>
commit 9e73fa02aa009 ("PCI: dwc: Warn if MEM resource size exceeds max for
32-bits") enables warning for MEM resources of size >4GB but prefetchable
memory resources also come under this category where sizes can go beyond
4GB. Avoid logging a warning for prefetchable memory resources.
Microchip lan7431 is frequently connected to a phy. However, it
can also be directly connected to a MII remote peer without
any phy in between. For supporting such a phyless hardware setup
in Linux we added the capability to the driver to understand
the fixed-link and the phy-connection-type
On Thu, May 7, 2020 at 12:17 PM Gustavo A. R. Silva
wrote:
>
> The current codebase makes use of the zero-length array language
> extension to the C90 standard, but the preferred mechanism to declare
> variable-length types such as these ones is a flexible array member[1][2],
> introduced in C99:
On Wed, 2020-05-13 at 11:53 -0700, Scott Branden wrote:
> Hi Mimi,
>
> On 2020-05-13 11:39 a.m., Mimi Zohar wrote:
> > [Cc'ing linux-security-module, linux-integrity]
> >
> > On Thu, 2020-05-07 at 17:27 -0700, Scott Branden wrote:
> >> Add kernel_pread_file* support to kernel to allow for partial
On Wed, May 13, 2020 at 12:05 AM Kalle Valo wrote:
> Actually it's already reverted in -next, nobody just realised that it's
> a regression from commit 728c1e2a05e4:
>
> ced21a4c726b ath9k: Fix use-after-free Read in htc_connect_service
Nice.
> v5.8-rc1 should be the first release having the
Vitaly Kuznetsov writes:
> Vitaly Kuznetsov writes:
>
>> This series is a successor of "[PATCH] x86/idt: Keep spurious entries unset
>> in system_vectors".
>>
>> The original issue I tried to address was that /proc/interrupts output
>> was always containing all possible system vectors, including
On Sun, May 10, 2020 at 12:02:41AM -0700, Christoph Hellwig wrote:
> On Sun, May 10, 2020 at 12:45:41AM +0100, Al Viro wrote:
> > From: Al Viro
> >
> > we use copy_to_user() on that thing anyway (and always had).
>
> I already have this patch in this series:
>
>
On Tue, May 12, 2020 at 1:01 PM Fangrui Song wrote:
>
> >Fangrui, I wasn't able to easily find what version of binutils first
> >added support. Can you please teach me how to fish?
>
> I actually downloaded https://ftp.gnu.org/gnu/binutils/ archives and
> located the sources... I think an easier
From: madhuparnabhowmi...@gmail.com
Date: Wed, 13 May 2020 11:46:10 +0530
> From: Madhuparna Bhowmik
>
> This patch fixes the following warning:
>
> =
> WARNING: suspicious RCU usage
> 5.7.0-rc4-next-20200507-syzkaller #0 Not tainted
> -
Expose averaged current information, which is part of the SBS
standard and should be supported by all batteries.
Signed-off-by: Sebastian Reichel
---
drivers/power/supply/sbs-battery.c | 12 +---
1 file changed, 9 insertions(+), 3 deletions(-)
diff --git
On Mon, May 11, 2020 at 1:29 AM Xiongfeng Wang
wrote:
>
> Add a missing newline when printing module parameter 'start_ro' by
> sysfs.
>
> Signed-off-by: Xiongfeng Wang
Applied to md-next. Thanks for the patch!
Add a property for reporting the error margin expected
by fuel gauge chips.
Signed-off-by: Sebastian Reichel
---
Documentation/ABI/testing/sysfs-class-power | 15 +++
drivers/power/supply/power_supply_sysfs.c | 1 +
include/linux/power_supply.h| 1 +
3 files
Some battery fuel gauges know when the battery needs to
be recalibrated before providing usable values. This
should be reported via the health property.
Signed-off-by: Sebastian Reichel
---
Documentation/ABI/testing/sysfs-class-power | 2 +-
drivers/power/supply/power_supply_sysfs.c | 1 +
SBS battery driver exposes 32 power supply properties now,
which will result in uevent failure on (un)plugging the
battery. Other drivers (e.g. bq27xxx) are also coming close
to this limit, so increase it.
Signed-off-by: Sebastian Reichel
---
include/linux/kobject.h | 2 +-
1 file changed, 1
This patchset improves support for SBS compliant batteries. Due to
the changes, the battery now exposes 32 power supply properties and
(un)plugging it generates a backtrace containing the following message
without the first patch in this series:
---
WARNING: CPU: 0 PID: 20
Add support for reporting the MaxError register from
battery fuel gauges following the smart battery standard.
Signed-off-by: Sebastian Reichel
---
drivers/power/supply/sbs-battery.c | 5 +
1 file changed, 5 insertions(+)
diff --git a/drivers/power/supply/sbs-battery.c
The SBS battery implements SMBus block reads. Currently the
driver "emulates" this by doing an I2C byte read for the
length followed by an I2C block read. The I2C subsystem
actually provides a proper API for doing SMBus block reads,
which can and should be used instead. The current implementation
On 2020-05-13 11:53 a.m., Scott Branden wrote:
Hi Mimi,
On 2020-05-13 11:39 a.m., Mimi Zohar wrote:
[Cc'ing linux-security-module, linux-integrity]
On Thu, 2020-05-07 at 17:27 -0700, Scott Branden wrote:
Add kernel_pread_file* support to kernel to allow for partial read
of files with an
Expose maximum charge current/voltage information requested
by the battery.
Signed-off-by: Sebastian Reichel
---
drivers/power/supply/sbs-battery.c | 12
1 file changed, 12 insertions(+)
diff --git a/drivers/power/supply/sbs-battery.c
b/drivers/power/supply/sbs-battery.c
index
Expose the battery's manufacture date to userspace.
Signed-off-by: Sebastian Reichel
---
drivers/power/supply/sbs-battery.c | 43 ++
1 file changed, 43 insertions(+)
diff --git a/drivers/power/supply/sbs-battery.c
b/drivers/power/supply/sbs-battery.c
index
Convert sbs-battery bindings to YAML.
Signed-off-by: Sebastian Reichel
---
.../power/supply/sbs,sbs-battery.yaml | 83 +++
.../bindings/power/supply/sbs_sbs-battery.txt | 30 ---
2 files changed, 83 insertions(+), 30 deletions(-)
create mode 100644
A battery, that is neither charged, nor discharged is not
always Full. If the charger is disabled for other reasons
it might simply be idle and should be marked accordingly.
Signed-off-by: Sebastian Reichel
---
drivers/power/supply/sbs-battery.c | 6 +++---
1 file changed, 3 insertions(+), 3
Add support for BQ20Z65 manufacturer data to the sbs-battery
driver. Implementation has been verified using the public TRM
available from [0] and tested using a GE Flex 3S2P battery.
[0] http://www.ti.com/lit/pdf/sluu386
Signed-off-by: Sebastian Reichel
---
Add support for reporting the SBS battery's condition flag
to userspace using the new "Calibration required" health status.
Signed-off-by: Sebastian Reichel
---
drivers/power/supply/sbs-battery.c | 27 ---
1 file changed, 24 insertions(+), 3 deletions(-)
diff --git
Switch from DT specific of_property_* API to generic and more
modern device_property_* API.
Signed-off-by: Sebastian Reichel
---
drivers/power/supply/sbs-battery.c | 14 +++---
1 file changed, 7 insertions(+), 7 deletions(-)
diff --git a/drivers/power/supply/sbs-battery.c
Some smart batteries store their manufacture date, which is
useful to identify the battery and/or to know about the cell
quality.
Signed-off-by: Sebastian Reichel
---
Documentation/ABI/testing/sysfs-class-power | 28 +
drivers/power/supply/power_supply_sysfs.c | 3 +++
SBS batteries optionally have support for PEC. This enables
PEC handling based on the implemented SBS version as suggested
by the standard. The support for PEC is re-evaluated when the
battery is hotplugged into the system, since there might be
systems supporting batteries from different SBS
From: Jean-Francois Dagenais
In certain designs, it is possible to add a battery on a populated i2c
bus without an sbs compliant charger. In that case, the battery will
un-necessarily and sometimes un-desirably master the bus trying to write
info in the charger.
It is observed in many occasion
Signed-off-by: Sebastian Reichel
---
drivers/power/supply/sbs-battery.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/power/supply/sbs-battery.c
b/drivers/power/supply/sbs-battery.c
index f0392be350eb..f4f73e669460 100644
--- a/drivers/power/supply/sbs-battery.c
This reads the battery chemistry from the battery chip instead
of incorrectly hardcoding the type to be Li-Ion.
Signed-off-by: Sebastian Reichel
---
drivers/power/supply/sbs-battery.c | 43 --
1 file changed, 41 insertions(+), 2 deletions(-)
diff --git
sbs-battery does not use the ID parameter, so switch to i2c's
probe_new API.
Signed-off-by: Sebastian Reichel
---
drivers/power/supply/sbs-battery.c | 5 ++---
1 file changed, 2 insertions(+), 3 deletions(-)
diff --git a/drivers/power/supply/sbs-battery.c
b/drivers/power/supply/sbs-battery.c
On Wed, May 13, 2020 at 05:46:13PM +0100, Dave Martin wrote:
> On Mon, May 11, 2020 at 11:04:03PM +0100, Cristian Marussi wrote:
> > Hi Dave
> >
> > thanks for the review first of all.
> >
[snip]
> >
> > First of all the enabled flag does not probably belong to this commit
> > properly;
> >
On 13.05.2020 20:12, Russell King - ARM Linux admin wrote:
> On Wed, May 13, 2020 at 05:41:58PM +0200, Fredrik Strupe wrote:
>> Hi,
>>
>> This is more of a question than a patch, but I hope the attached patch makes
>> the issue a bit clearer.
>>
>> The arm port of Linux supports hooking/trapping
From: Xiaoliang Yang
Date: Wed, 13 May 2020 10:25:07 +0800
> This patch series support tc taprio and CBS hardware offload according
> to IEEE 802.1Qbv and IEEE-802.1Qav on VSC9959.
>
> v1->v2 changes:
> - Move port_qos_map_init() function to be common felix codes.
> - Keep const for
On Wed, 13 May 2020 at 19:47, Will Deacon wrote:
>
> On Wed, May 13, 2020 at 07:32:58PM +0200, Marco Elver wrote:
> > On Wed, 13 May 2020 at 18:50, Will Deacon wrote:
> > >
> > > On Wed, May 13, 2020 at 03:15:55PM +0200, Marco Elver wrote:
> > > > On Wed, 13 May 2020 at 14:40, Will Deacon
Hi Mimi,
On 2020-05-13 11:39 a.m., Mimi Zohar wrote:
[Cc'ing linux-security-module, linux-integrity]
On Thu, 2020-05-07 at 17:27 -0700, Scott Branden wrote:
Add kernel_pread_file* support to kernel to allow for partial read
of files with an offset into the file. Existing kernel_read_file
vabits_actual variable on arm64 indicates the actual VA space size,
and allows a single binary to support both 48-bit and 52-bit VA
spaces.
If the ARMv8.2-LVA optional feature is present, and we are running
with a 64KB page size; then it is possible to use 52-bits of address
space for both
On Wed, May 13, 2020 at 04:43:02PM +0530, Rajendra Nayak wrote:
> QSPI needs to vote on a performance state of a power domain depending on
> the clock rate. Add support for it by specifying the perf state/clock rate
> as an OPP table in device tree.
>
> Signed-off-by: Rajendra Nayak
> Cc: Mark
Apologies for the delayed update. Its been quite some time since I
posted the last version (v5), but I have been really caught up in some
other critical issues.
Changes since v5:
- v5 can be viewed here:
http://lists.infradead.org/pipermail/kexec/2019-November/024055.html
-
Right now user-space tools like 'makedumpfile' and 'crash' need to rely
on a best-guess method of determining value of 'MAX_PHYSMEM_BITS'
supported by underlying kernel.
This value is used in user-space code to calculate the bit-space
required to store a section for SPARESMEM (similar to the
On Wed, May 13, 2020 at 1:34 AM Saravana Kannan wrote:
>
> On Wed, May 13, 2020 at 1:22 AM Greg Kroah-Hartman
> wrote:
> >
> > On Tue, May 12, 2020 at 06:34:15PM -0700, Saravana Kannan wrote:
> > > This can be used to check if a device supports sync_state() callbacks
> > > and therefore keeps
From: Michael Srba
On some msm8916 devices, attempts at initializing coresight cause the boot to
fail. This was fixed by disabling the coresight-related nodes in the board dts
files. However, a cleaner approach was chosen for fixing the same issue on
msm8998: disabling coresight by default, and
On Wed, 13 May 2020 15:43:16 -0300 Jason Gunthorpe wrote:
> On Sat, May 09, 2020 at 08:51:50PM -0700, Jakub Kicinski wrote:
> > On Thu, 7 May 2020 13:59:21 -0500 Gustavo A. R. Silva wrote:
> > > The current codebase makes use of the zero-length array language
> > > extension to the C90 standard,
From: Rodrigo Rolim Mendes de Alencar
This patch provides support for displays like VGM128064B0W10,
which requires a column offset of 2, i.e., its segments starts
in SEG2 and ends in SEG129.
Signed-off-by: Rodrigo Alencar <455.rodrigo.alen...@gmail.com>
---
Document the available properties for the SoC root node and the
CPU nodes of the devicetree for the Ingenic XBurst SoCs.
Tested-by: H. Nikolaus Schaller
Tested-by: Paul Boddie
Signed-off-by: 周琰杰 (Zhou Yanjie)
---
Notes:
v1->v2:
Change the two Document from txt to yaml.
Introduce SMP support for MIPS Creator CI20, which is
based on Ingenic JZ4780 SoC.
周琰杰 (Zhou Yanjie) (6):
MIPS: JZ4780: Introduce SMP support.
MIPS: CI20: Modify DTS to support high resolution timer for SMP.
clocksource: Ingenic: Add high resolution timer support for SMP.
dt-bindings:
Modify DTS, change tcu channel from 2 to 3, channel #0 and #1 for
per core local timer, #2 for clocksource.
Tested-by: H. Nikolaus Schaller
Tested-by: Paul Boddie
Signed-off-by: 周琰杰 (Zhou Yanjie)
---
Notes:
v1->v2:
No change.
v2->v3:
No change.
v3->v4:
Rebase
Add "CONFIG_SMP=y" and "CONFIG_NR_CPUS=2" to support SMP.
Tested-by: H. Nikolaus Schaller
Tested-by: Paul Boddie
Signed-off-by: 周琰杰 (Zhou Yanjie)
---
Notes:
v1->v2:
No change.
v2->v3:
No change.
v3->v4:
Rebase on top of kernel 5.6-rc1.
v4->v5:
No
Add 'cpus' node to the jz4740.dtsi, jz4770.dtsi, jz4780.dtsi
and x1000.dtsi files.
Tested-by: H. Nikolaus Schaller
Tested-by: Paul Boddie
Signed-off-by: 周琰杰 (Zhou Yanjie)
---
Notes:
v1->v2:
No change.
v2->v3:
No change.
v3->v4:
Rebase on top of kernel
Enable clock event handling on per CPU core basis.
Make sure that interrupts raised on the first core execute
event handlers on the correct CPU core.
Tested-by: H. Nikolaus Schaller
Tested-by: Paul Boddie
Signed-off-by: 周琰杰 (Zhou Yanjie)
---
Notes:
v1->v2:
1.Adjust function naming to
Introduce SMP support for MIPS Creator CI20, which is
based on Ingenic JZ4780 SoC.
Forward port smp support from kernel 3.18.3 of CI20_linux
to upstream kernel 5.6.
Tested-by: H. Nikolaus Schaller
Tested-by: Paul Boddie
Signed-off-by: 周琰杰 (Zhou Yanjie)
Reviewed-by: Jiaxun Yang
---
Notes:
v1->v2:
1.Remove unnecessary "plat_irq_dispatch(void)" in irq-ingenic.c.
On Wed, May 13, 2020 at 04:23:55PM +0200, Vitaly Kuznetsov wrote:
[..]
> >> Also,
> >> kdump kernel may not even support APF so it will get very confused when
> >> APF events get delivered.
> >
> > New kernel can just ignore these events if it does not support async
> > pf?
> >
> > This is
On Wed, May 13, 2020 at 11:33 AM Christoph Hellwig wrote:
>
> On Wed, May 13, 2020 at 11:29:17AM -0700, Song Liu wrote:
> > On Fri, May 8, 2020 at 9:17 AM Christoph Hellwig wrote:
> > >
> > > Signed-off-by: Christoph Hellwig
> >
> > Thanks for the cleanup. IIUC, you want this go through md
Hi Dave,
this series removes the kernel_setsockopt and kernel_getsockopt
functions, and instead switches their users to small functions that
implement setting (or in one case getting) a sockopt directly using
a normal kernel function call with type safety and all the other
benefits of not
On 13.05.2020 08:51, Jisheng Zhang wrote:
> Hi,
>
> On Tue, 12 May 2020 20:43:40 +0200 Heiner Kallweit wrote:
>
>>
>>
>> On 12.05.2020 12:46, Jisheng Zhang wrote:
>>> The PHY Register Accessible Interrupt is enabled by default, so
>>> there's such an interrupt during init. In PHY POLL mode case,
On Sat, May 09, 2020 at 08:51:50PM -0700, Jakub Kicinski wrote:
> On Thu, 7 May 2020 13:59:21 -0500 Gustavo A. R. Silva wrote:
> > The current codebase makes use of the zero-length array language
> > extension to the C90 standard, but the preferred mechanism to declare
> > variable-length types
On Wed, May 13, 2020 at 06:47:14PM +0200, Frederic Weisbecker wrote:
> Not for merge.
>
> Make nocb toggable for a given CPU using:
> /sys/devices/system/cpu/cpu*/hotplug/nocb
>
> This is only intended for those who want to test this patchset. The real
> interfaces will be cpuset/isolation
On 13/05/2020 17:43, Thomas Gleixner wrote:
> Wojciech Kudla writes:
>> On 13/05/2020 13:24, Thomas Gleixner wrote:
>>
>>> Why would the SMP call function single interrupt go through the
>>> PLATFORM_IPI_VECTOR? It goes as the name says through the
>>> CALL_FUNCTION_SINGLE_VECTOR.
>>>
>>
>> Wrong
On Wed, May 13, 2020 at 06:47:13PM +0200, Frederic Weisbecker wrote:
> This is essentially the reverse operation of de-offloading. For now it's
> only supported on CPUs that used to be offloaded and therefore still have
> the relevant nocb_cb/nocb_gp kthreads around.
And I still believe that this
On Wed, May 13, 2020 at 04:43:01PM +0530, Rajendra Nayak wrote:
> Add support to add OPP tables and perf voting on the OPP powerdomain.
> This is needed so venus votes on the corresponding performance state
> for the OPP powerdomain along with setting the core clock rate.
>
> Signed-off-by:
Fix for non-working buttons on knock-off USB dongles for Sony
controllers. These USB dongles are used to connect older Sony DA/DS1/DS2
controllers via USB and are common on Amazon, AliExpress, etc. Without
the patch, the square, X, and circle buttons do not function. These
dongles used to work
On Wed, May 13, 2020 at 11:41:14PM +0530, Naresh Kamboju wrote:
> While running LTP sched on stable-rc 4.19 branch kernel on arm64 hikey device.
> Thermal alarm triggered and followed by kernel warnings and Internal
> error: Oops:
Hi!
I just happened to see this on lkml. It looks a lot like
Thanks for link.
On 2020-05-13 5:30 a.m., Luis Chamberlain wrote:
On Wed, May 13, 2020 at 08:50:46AM +0200, Greg Kroah-Hartman wrote:
On Tue, May 12, 2020 at 11:31:28PM -0700, Scott Branden wrote:
That's not how kernel drivers in the tree work, sorry. They do not
contain "older kernel
401 - 500 of 1758 matches
Mail list logo
