According to the CAN Specification (see ISO 11898-1:2015, 8.3.4
Recovery Management), the M_CAN provides means for automatic
retransmission of frames that have lost arbitration or that
have been disturbed by errors during transmission. By default
automatic retransmission is enabled.
The Bosch MCAN
On 10/16/19 4:55 PM, Ricardo Ribalda Delgado wrote:
> This allows setting the default value on compound controls created via
> v4l2_ctrl_new_custom.
>
> Signed-off-by: Ricardo Ribalda Delgado
> ---
> drivers/media/v4l2-core/v4l2-ctrls.c | 3 ++-
> include/media/v4l2-ctrls.h | 2 ++
> 2
Dan Williams writes:
> Check for NULL entries before checking the entry order, otherwise NULL
> is misinterpreted as a present pte conflict. The 'order' check needs to
> happen before the locked check as an unlocked entry at the wrong order
> must fallback to lookup the correct order.
Please inc
Now that we have the DT validation in place, let's convert the device tree
bindings for the Amlogic AO-CEC controller over to a YAML schemas.
Signed-off-by: Neil Armstrong
---
.../media/amlogic,meson-gx-ao-cec.yaml| 91 +++
.../bindings/media/meson-ao-cec.txt |
Add new entries for linux,rc-map-name:
- rc-khadas
- rc-odroid
- rc-tanix-tx3mini
- rc-wetek-hub
- rc-wetek-play2
- rc-x96max
Signed-off-by: Neil Armstrong
---
Documentation/devicetree/bindings/media/rc.yaml | 6 ++
1 file changed, 6 insertions(+)
diff --git a/Documentation/devicetree/bindi
On Fri, Oct 18, 2019 at 07:32:13PM +0200, Fabien Parent wrote:
> Since commit abf4923e97c3 ("i2c: mediatek: disable zero-length transfers
> for mt8183"), there is a NULL pointer dereference for all the SoCs
> that don't have any quirk. mtk_i2c_functionality is not checking that
> the quirks pointer
The Bosch MCAN hardware (3.1.0 and above) supports interrupt flag to
detect Protocol error in arbitration phase.
Transmit error statistics is currently not updated from the MCAN driver.
Protocol error in arbitration phase is a TX error and the network
statistics should be updated accordingly.
The
On 21/10/2019 12:45, Lee Jones wrote:
On Mon, 21 Oct 2019, Srinivas Kandagatla wrote:
Thanks Lee for taking time to review.
I agree with most of the style related comments, will fix them in next
version. For others I have replied it inline.
[...]
+static int wcd934x_slim_status(struct s
On 19/10/2019 21:28, Marc Zyngier wrote:
> On Fri, 11 Oct 2019 13:59:30 +0100,
> Steven Price wrote:
>>
>> Enable paravirtualization features when running under a hypervisor
>> supporting the PV_TIME_ST hypercall.
>>
>> For each (v)CPU, we ask the hypervisor for the location of a shared
>> page wh
Tom,
On 17/10/19 12:38 AM, Tom Joseph wrote:
> All the platform related APIs/Structures in the driver is extracted
> out to a separate file (pcie-cadence-plat.c). This enables the
> driver to be used as a core library, which could now be used by
> other platform drivers. Testing done using simu
On Mon 21-10-19 19:56:54, Hillf Danton wrote:
>
> Currently soft limit reclaim is frozen, see
> Documentation/admin-guide/cgroup-v2.rst for reasons.
>
> Copying the page lru idea, memcg lru is added for selecting victim
> memcg to reclaim pages from under memory pressure. It now works in
> parall
Allow qcom-hw driver to initialize right after the cpufreq and thermal
subsystems are initialised in core_initcall so we get earlier access to
thermal mitigation.
Signed-off-by: Amit Kucheria
Acked-by: Daniel Lezcano
Acked-by: Taniya Das
Acked-by: Viresh Kumar
---
drivers/cpufreq/qcom-cpufreq
On Mon, 21 Oct 2019 at 14:00, Oleg Nesterov wrote:
>
> On 10/21, Christian Brauner wrote:
> >
> > This traces back to Oleg fixing a race between a group stop and a thread
> > exiting before it notices that it has a pending signal or is in the middle
> > of
> > do_exit() already, causing group sto
Initialize the clock drivers on sdm845 and qcs404 in core_initcall so we
can have earlier access to cpufreq during booting.
Signed-off-by: Amit Kucheria
Acked-by: Stephen Boyd
Acked-by: Viresh Kumar
---
drivers/clk/qcom/clk-rpmh.c | 2 +-
drivers/clk/qcom/gcc-qcs404.c | 2 +-
drivers/clk/qco
This allows HW drivers that depend on cpufreq-dt to initialize earlier.
Signed-off-by: Amit Kucheria
Acked-by: Viresh Kumar
---
drivers/cpufreq/cpufreq-dt-platdev.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/cpufreq/cpufreq-dt-platdev.c
b/drivers/cpufreq/cpufre
Now that the thermal framework is built-in, in order to facilitate
thermal mitigation as early as possible in the boot cycle, move the
thermal framework initialization to core_initcall.
Signed-off-by: Amit Kucheria
Acked-by: Viresh Kumar
---
drivers/thermal/thermal_core.c | 2 +-
1 file changed
There are no users of netlink messages for thermal inside the kernel.
Remove the code and adjust the documentation.
Signed-off-by: Amit Kucheria
Acked-by: Viresh Kumar
---
.../driver-api/thermal/sysfs-api.rst | 26 ++---
drivers/thermal/thermal_core.c| 101 +---
Initialize the cpufreq governors earlier to allow for earlier
performance control during the boot process.
Signed-off-by: Amit Kucheria
Acked-by: Viresh Kumar
Reviewed-by: Rafael J. Wysocki
---
drivers/cpufreq/cpufreq_conservative.c | 2 +-
drivers/cpufreq/cpufreq_ondemand.c | 2 +-
driver
On Mon 21-10-19 07:00:46, Naoya Horiguchi wrote:
> On Fri, Oct 18, 2019 at 01:48:32PM +0200, Michal Hocko wrote:
> > On Thu 17-10-19 16:21:08, Oscar Salvador wrote:
> > > From: Naoya Horiguchi
> > >
> > > Drop the PageHuge check since memory_failure forks into
> > > memory_failure_hugetlb()
> >
On Mon, Oct 21, 2019 at 11:58:19AM +0100, Lee Jones wrote:
> IO regions are now requested and released by this device's parent.
>
> Signed-off-by: Lee Jones
> ---
> arch/x86/platform/olpc/olpc-xo1-pm.c | 6 --
Why doesn't olpc-xo1-sci.c need a similar update.
Daniel.
> 1 file changed, 6
Fix a bug where the mac80211 RX aggregation code sets a new aggregation
"session" at the remote station's request, but the head_seq_num
(the sequence number the receiver expects to receive) isn't reset.
Spotted on a pair of AR9580 in IBSS mode.
diff --git a/net/mac80211/agg-rx.c b/net/mac80211/ag
On 21/10/2019 13.33, Christian Brauner wrote:
> The first approach used smp_load_acquire() and smp_store_release().
> However, after having discussed this it seems that the data dependency
> for kmem_cache_alloc() would be fixed by WRITE_ONCE().
> Furthermore, the smp_load_acquire() would only mana
On Mon 21-10-19 07:02:55, Naoya Horiguchi wrote:
> On Fri, Oct 18, 2019 at 01:52:27PM +0200, Michal Hocko wrote:
> > On Thu 17-10-19 16:21:09, Oscar Salvador wrote:
> > > From: Naoya Horiguchi
> > >
> > > The call to get_user_pages_fast is only to get the pointer to a struct
> > > page of a given
Johannes,
it seems I've encountered a bug in mac80211 RX aggregation handler.
The hw is a pair of stations using AR9580 (PCI ID 168c:0033) PCIe
adapters. Linux 5.4-rc4.
The driver shows the chip is Atheros AR9300 Rev:4.
I'm using (on both ends):
iw wlan0 set type ibss
ip link set w
Em Mon, Oct 21, 2019 at 08:23:54AM +0200, Ingo Molnar escreveu:
> * Arnaldo Carvalho de Melo wrote:
> > Please consider pulling,
> > tools/perf/util/header.c | 4 +++-
> > tools/perf/util/util.c| 6 --
> > 12 files changed, 65 insertions(+), 17 deletions(
On Mon, 2019-10-21 at 12:53 +0100, Lee Jones wrote:
> On Mon, 21 Oct 2019, Lubomir Rintel wrote:
>
> > On Mon, 2019-10-21 at 13:29 +0200, Arnd Bergmann wrote:
> > > On Mon, Oct 21, 2019 at 12:58 PM Lee Jones wrote:
> > > > MFD currently has one over-complicated user. CS5535 uses a mixture of
> >
pon., 21 paź 2019 o 12:45 Daniel Thompson
napisał(a):
>
> On Sat, Oct 19, 2019 at 10:35:50AM +0200, Bartosz Golaszewski wrote:
> > From: Bartosz Golaszewski
> >
> > The GPIO backlight driver currently requests the line 'as is', without
> > acively setting its direction. This can lead to problems:
On Fri, Sep 13, 2019 at 11:35:09AM -0500, Eddie James wrote:
> The driver default behavior works with the AST2600. We need a new
> compatible though to make sure the driver doesn't enable AST2400 or
> AST2500 behavior.
>
> Signed-off-by: Eddie James
Applied to for-next, thanks!
signature.asc
On Fri, Sep 13, 2019 at 11:35:10AM -0500, Eddie James wrote:
> Document the AST2600 I2C bus compatible string.
>
> Signed-off-by: Eddie James
Applied to for-next, thanks!
signature.asc
Description: PGP signature
Hi Marco,
On 21.10.19 13:43, Marco Felsch wrote:
> Hi Frieder,
>
> On 19-10-17 08:24, Schrempf Frieder wrote:
>> Hi Marco,
>>
>> On 17.10.19 10:14, Marco Felsch wrote:
>>> Hi Frieder,
>>>
>>> On 19-10-16 15:06, Schrempf Frieder wrote:
From: Frieder Schrempf
In order to support mor
On 10/14/19 3:22 PM, Thomas Hellström (VMware) wrote:
> From: Thomas Hellström
>
> Graphics APIs like OpenGL 4.4 and Vulkan require the graphics driver
> to provide coherent graphics memory, meaning that the GPU sees any
> content written to the coherent memory on the next GPU operation that
> tou
Add support for ZRX-DC compliant PHYs. If PHY is not compliant to ZRX-DC
specification, then after every 100ms link should transition to recovery
state during the low power states which increases power consumption.
Platforms with ZRX-DC compliant PHY can use "snps,phy-zrxdc-compliant"
property in
On Mon, Oct 21, 2019 at 11:58:16AM +0100, Lee Jones wrote:
> Prior to this patch, IO regions were requested via an MFD subsytem-level
> .enable() call-back and similarly released by a .disable() call-back.
> Double requests/releases were avoided by a centrally handled usage count
> mechanism.
>
>
On 10/8/19 2:34 PM, Thomas Hellström (VMware) wrote:
Hi, Christoph,
Following our previous discussion I wonder if something along the
lines of the following could work / be acceptible
typedef unsigned long dma_pfn_t /* Opaque pfn type. Arch dependent.
This could if needed be a struct with a
On Sun 20-10-19 21:43:04, Hillf Danton wrote:
>
> Unlike cpu preemption, page preemption would have been a two-edge
> option for quite a while. It is added by preventing tasks from
> reclaiming as many lru pages as possible from other tasks of
> higher priorities.
This really begs for more explan
Currently the MTU of vlan netdevice is set to the same MTU
of the lower device, which requires the underlying device
to handle it as the comment has indicated:
/* need 4 bytes for extra VLAN header info,
* hope the underlying device can handle it.
*/
new_dev->mtu
On Mon, Oct 21, 2019 at 11:58:17AM +0100, Lee Jones wrote:
> CS5535 is the only user of mfd_clone_cell(). It makes more sense to
> register child devices in the traditional way and remove the quite
> bespoke mfd_clone_cell() call from the MFD API.
>
> Signed-off-by: Lee Jones
> ---
> drivers/mf
Many platforms use DesignWare controller but the PHY can be different in
different platforms. If the PHY is compliant is to ZRX-DC specification
it helps in low power consumption during power states.
If current data rate is 8.0 GT/s or higher and PHY is not compliant to
ZRX-DC specification, then
On Mon, Oct 21, 2019 at 11:58:18AM +0100, Lee Jones wrote:
> Providing a subsystem-level API helper seems over-kill just to save a
> few lines of C-code. Previous commits saw us convert mfd_clone_cell()'s
> only user over to use a more traditional style of MFD child-device
> registration. Now we
On Mon, Oct 21, 2019 at 11:58:20AM +0100, Lee Jones wrote:
> If a child device calls mfd_cell_{en,dis}able() without an appropriate
> call-back being set, we are likely to encounter a panic. Avoid this
> by adding suitable checking.
>
> Signed-off-by: Lee Jones
Reviewed-by: Daniel Thompson
>
On Mon, Oct 14, 2019 at 5:57 AM Aaron Lu wrote:
>
> I now remembered why I used max().
>
> Assume rq1 and rq2's min_vruntime are both at 2000 and the core wide
> min_vruntime is also 2000. Also assume both runqueues are empty at the
> moment. Then task t1 is queued to rq1 and runs for a long time
On Sat, Oct 19, 2019 at 11:19:26PM -0400, Vivien Didelot wrote:
> Do not let the drivers access the ds->ports static array directly
> while there is a dsa_to_port helper for this purpose.
>
> At the same time, un-const this helper since the SJA1105 driver
> assigns the priv member of the returned
Hi Zhou,
Le sam., oct. 19, 2019 at 01:50, Zhou Yanjie a
écrit :
Add support for the clocks provided by the CGU in the Ingenic X1000
SoC, making use of the cgu code to do the heavy lifting.
Signed-off-by: Zhou Yanjie
---
drivers/clk/ingenic/Kconfig | 10 ++
drivers/clk/ingenic/Makefile
On Mon 2019-08-19 12:47:29, Petr Mladek wrote:
> ( Resending this as a proper patch with updated commit messages.
> The original was
> https://lkml.kernel.org/r/20190605140954.28471-1-pmla...@suse.com )
>
> We were analyzing logs with several softlockup reports in
> flush_tlb_kernel_range().
On Mon, Oct 21, 2019 at 11:58:20AM +0100, Lee Jones wrote:
> If a child device calls mfd_cell_{en,dis}able() without an appropriate
> call-back being set, we are likely to encounter a panic. Avoid this
> by adding suitable checking.
>
> Signed-off-by: Lee Jones
> ---
> drivers/mfd/mfd-core.c |
On Tue, Oct 01, 2019 at 05:03:55PM +0200, Juergen Gross wrote:
> In case a user process using xenbus has open transactions and is killed
> e.g. via ctrl-C the following cleanup of the allocated resources might
> result in a deadlock due to trying to end a transaction in the xenbus
> worker thread:
On Mon, Oct 21, 2019 at 11:58:21AM +0100, Lee Jones wrote:
> The MFD implementation for reference counting was complex and unnecessary.
> There was only one bona fide user which has now been converted to handle
> the process in a different way. Any future resource protection, shared
> enablement fu
On Fri, Oct 18, 2019 at 8:07 PM Greg Kroah-Hartman
wrote:
>
> On Fri, Oct 18, 2019 at 04:55:56PM +0200, Andrey Konovalov wrote:
> > This patch increases the maximum number of Dummy UDC/HCD devices to 32.
>
> Yes, that is a good description of _what_ the patch does, but it does
> not tell us _why_
On Fri, Oct 18, 2019 at 08:33:11AM -0700, Randy Dunlap wrote:
> On 10/18/19 12:03 AM, Stephen Rothwell wrote:
> > Hi all,
> >
> > Changes since 20191017:
> >
>
> on x86_64:
> lib/usercopy.o: warning: objtool: check_zeroed_user()+0x35f: call to
> __ubsan_handle_shift_out_of_bounds() with UACCESS
> +static struct dsa_port *dsa_port_touch(struct dsa_switch *ds, int index)
> +{
> + struct dsa_switch_tree *dst = ds->dst;
> + struct dsa_port *dp;
> +
> + dp = &ds->ports[index];
> +
> + dp->ds = ds;
> + dp->index = index;
> +
> + INIT_LIST_HEAD(&dp->list);
> + list_ad
On Thu, 2019-10-17 at 15:46 +0100, Luis Henriques wrote:
> KASAN reports a use-after-free when running xfstest generic/531, with the
> following trace:
>
> [ 293.903362] kasan_report+0xe/0x20
> [ 293.903365] rb_erase+0x1f/0x790
> [ 293.903370] __ceph_remove_cap+0x201/0x370
> [ 293.903375]
On Sat, Oct 19, 2019 at 11:19:28PM -0400, Vivien Didelot wrote:
> Use the new ports list instead of accessing the dsa_switch array
> of ports in the dsa_to_port helper.
>
> Signed-off-by: Vivien Didelot
Reviewed-by: Andrew Lunn
Andrew
On Mon, 21 Oct 2019, Daniel Thompson wrote:
> On Mon, Oct 21, 2019 at 11:58:20AM +0100, Lee Jones wrote:
> > If a child device calls mfd_cell_{en,dis}able() without an appropriate
> > call-back being set, we are likely to encounter a panic. Avoid this
> > by adding suitable checking.
> >
> > Sig
According the PCI Express base specification when PHY does not meet
ZRX-DC specification, after every 100ms timeout the link should
transition to recovery state when the link is in low power states.
Ports that meet the ZRX-DC specification for 2.5 GT/s while in the
L1.Idle state and are therefore
On Mon, Aug 19, 2019 at 12:47:30PM +0200, Petr Mladek wrote:
> Some bug report included the same softlockups in flush_tlb_kernel_range()
> in regular intervals. Unfortunately was not clear if there was a progress
> or not.
>
> The situation can be simulated with a simply busy loop:
>
> whil
On Sat, Oct 19, 2019 at 11:19:29PM -0400, Vivien Didelot wrote:
> Use the new ports list instead of iterating over switches and their
> ports when looking for a slave device from a given master interface.
>
> Signed-off-by: Vivien Didelot
Reviewed-by: Andrew Lunn
Andrew
On Mon, Aug 19, 2019 at 12:47:31PM +0200, Petr Mladek wrote:
> Softlockup report means that there is no progress on the given CPU. It
> might be a "short" affair where the system gets recovered. But often
> the system stops being responsive and need to get rebooted.
>
> The softlockup might be roo
Hi Krzysztof,
On 21.10.19 12:38, k...@kernel.org wrote:
> On Wed, Oct 16, 2019 at 03:07:25PM +, Schrempf Frieder wrote:
>> From: Frieder Schrempf
>>
>> The baseboard for the Kontron N6310 SoM is also used for other SoMs
>> such as N6311 and N6411. In order to share the code, we move the
>> de
On 7/10/19 3:06 PM, Adrian Hunter wrote:
> On 7/10/19 2:20 PM, Jiri Olsa wrote:
>> On Fri, Oct 04, 2019 at 11:31:20AM +0300, Adrian Hunter wrote:
>>
>> SNIP
>>
>>> u8 pad[8] = {0};
>>>
>>> - if (!perf_data__is_pipe(data) && !perf_data__is_dir(data)) {
>>> + if (!perf_data__is_pipe(data) &
On 21.10.19 12:28, k...@kernel.org wrote:
> On Wed, Oct 16, 2019 at 03:07:19PM +, Schrempf Frieder wrote:
>> From: Frieder Schrempf
>>
>> The Kontron N6311 and N6411 SoMs are very similar to N6310. In
>> preparation to add support for them, we move the common nodes to a
>> separate file imx6ul
From: Bartosz Golaszewski
Convert the binding document for MAX77650 onkey module to YAML.
Signed-off-by: Bartosz Golaszewski
Reviewed-by: Rob Herring
---
.../bindings/input/max77650-onkey.txt | 26 --
.../bindings/input/max77650-onkey.yaml| 35 +++
From: Bartosz Golaszewski
Convert the binding document for MAX77650 LED module to YAML.
Signed-off-by: Bartosz Golaszewski
---
.../bindings/leds/leds-max77650.txt | 57 ---
.../bindings/leds/leds-max77650.yaml | 51 +
2 files changed, 51 inser
From: Bartosz Golaszewski
The DT bindings for MAX77650 MFD have now been converted to YAML.
Update the MAINTAINERS entry for this set of drivers.
Signed-off-by: Bartosz Golaszewski
---
MAINTAINERS | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/MAINTAINERS b/MAINTAINERS
From: Bartosz Golaszewski
Convert the binding document for MAX77650 regulator module to YAML.
Signed-off-by: Bartosz Golaszewski
---
.../bindings/regulator/max77650-regulator.txt | 41 ---
.../regulator/max77650-regulator.yaml | 31 ++
2 files changed, 31 in
From: Bartosz Golaszewski
Convert the binding document for MAX77650 core MFD module to YAML.
Signed-off-by: Bartosz Golaszewski
---
.../devicetree/bindings/mfd/max77650.txt | 46 --
.../devicetree/bindings/mfd/max77650.yaml | 149 ++
2 files changed, 149 insertion
From: Bartosz Golaszewski
Convert the binding document for MAX77650 charger module to YAML.
Signed-off-by: Bartosz Golaszewski
Acked-by: Sebastian Reichel
---
.../power/supply/max77650-charger.txt | 28 ---
.../power/supply/max77650-charger.yaml| 34 +++
On Mon, Oct 21, 2019 at 11:58:22AM +0100, Lee Jones wrote:
> Most of the complexity of mfd_platform_add_cell() has been removed. The
> only functionality left duplicates cell memory into the child's platform
> device. Since it's only a few lines, moving it to the main thread and
> removing the supe
On Mon, Aug 19, 2019 at 12:47:32PM +0200, Petr Mladek wrote:
> Trigger busy loop by:
> $> cat /proc/version
>
> Stop the busy loop by:
> $> cat /proc/consoles
>
> The code also shows the first touch*watchdog() function that hides
> softlockup on a "well known" location.
This seems like a terribl
From: Bartosz Golaszewski
This series converts all DT binding documents for MAX77650 PMIC to YAML.
v1 -> v2:
- use upper case for abbreviations in commit messages
v2 -> v3:
- pull all example fragments into the binding document for the core MFD module
- fix all dt_binding_check errors
- add ref
On 19 Oct 2019, at 23:47, Stephen Rothwell wrote:
> Hi all,
>
> The btrfs tree
> (git://git.kernel.org/pub/scm/linux/kernel/git/mason/linux-btrfs.git#next)
> has not bee updated in more than a year, so I have removed it and then
> renamed the btrfs-kdave tree to btrfs. I hope this is OK and if an
sob., 12 paź 2019 o 15:37 Jonathan Cameron napisał(a):
>
> On Mon, 7 Oct 2019 04:41:31 +0200
> Bartosz Golaszewski wrote:
>
> > From: Bartosz Golaszewski
> >
> > We can drop some duplicate code if we use devm_action for disabling
> > regulators and pm and the managed variant of iio_device_regis
On Mon, 21 Oct 2019, Daniel Thompson wrote:
> On Mon, Oct 21, 2019 at 11:58:16AM +0100, Lee Jones wrote:
> > Prior to this patch, IO regions were requested via an MFD subsytem-level
> > .enable() call-back and similarly released by a .disable() call-back.
> > Double requests/releases were avoided
Hi,
Le mer., août 14, 2019 at 19:32, Uwe Kleine-König
a écrit :
Hello Paul,
On Wed, Aug 14, 2019 at 06:10:35PM +0200, Paul Cercueil wrote:
Le mar. 13 août 2019 à 16:09, Uwe =?iso-8859-1?q?Kleine-K=F6nig?=
a écrit :
> On Tue, Aug 13, 2019 at 02:47:28PM +0200, Paul Cercueil wrote:
> > Le
In do_hres(), we currently use whether the return value of __arch_get_
hw_counter() is negative to indicate fallback, but this is not a good
idea because:
1, ARM64 returns ULL_MAX but MIPS returns 0 when clock_mode is invalid;
2, For a 64bit counter, a "negative" value of counter is actually valid
On Sun, Oct 20, 2019 at 07:42:15PM -0700, Florian Fainelli wrote:
>
>
> On 10/19/2019 8:19 PM, Vivien Didelot wrote:
> > Use the new ports list instead of iterating over switches and their
> > ports when setting up the switches and their ports.
> >
> > At the same time, provide setup states and
On Sat, Oct 19, 2019 at 11:19:31PM -0400, Vivien Didelot wrote:
> Use the new ports list instead of accessing the dsa_switch array
> of ports when iterating over DSA ports of a switch to set up the
> routing table.
>
> Signed-off-by: Vivien Didelot
Reviewed-by: Andrew Lunn
Andrew
On Mon, Oct 21, 2019 at 02:00:30PM +0200, Oleg Nesterov wrote:
> On 10/21, Christian Brauner wrote:
> >
> > This traces back to Oleg fixing a race between a group stop and a thread
> > exiting before it notices that it has a pending signal or is in the middle
> > of
> > do_exit() already, causing
On 18-10-19, 15:39, Taniya Das wrote:
> Add support for clock RPMh driver to vote for ARC and VRM managed
> clock resources.
>
> Signed-off-by: Taniya Das
> ---
> drivers/clk/qcom/clk-rpmh.c | 19 +++
> 1 file changed, 19 insertions(+)
>
> diff --git a/drivers/clk/qcom/clk-rpmh.
This is a tentative to switch powerpc/32 vdso to generic C implementation.
It will likely not work on 64 bits or even build properly at the moment.
powerpc is a bit special for VDSO as well as system calls in the
way that it requires setting CR SO bit which cannot be done in C.
Therefore, entry/ex
* Update AMD cpu microcode for processor family 17h
Key Name= AMD Microcode Signing Key (for signing microcode container
files only)
Key ID = F328AE73
Key Fingerprint = FC7C 6C50 5DAF CC14 7183 57CA E4BE 5339 F328 AE73
Signed-off-by: John Allen
---
WHENCE
On Mon, Oct 21, 2019 at 01:55:32PM +0800, Kefeng Wang wrote:
> For kernel logging macro, pr_warning is completely removed and
> replaced by pr_warn, using pr_warn in tools lib bpf for symmetry
> to kernel logging macro, then we could drop pr_warning in the
> whole linux code.
>
> Cc: Alexei Starov
On Mon, Oct 21, 2019 at 10:44:20AM +0200 Vincent Guittot wrote:
> On Mon, 21 Oct 2019 at 09:50, Ingo Molnar wrote:
> >
> >
> > * Vincent Guittot wrote:
> >
> > > Several wrong task placement have been raised with the current load
> > > balance algorithm but their fixes are not always straight for
On Fri, Oct 18, 2019 at 02:06:15PM +0200, Michal Hocko wrote:
> On Thu 17-10-19 16:21:17, Oscar Salvador wrote:
> [...]
> > +bool take_page_off_buddy(struct page *page)
> > + {
> > + struct zone *zone = page_zone(page);
> > + unsigned long pfn = page_to_pfn(page);
> > + unsigned long flags;
>
Document devicetree's binding for the Kizbox2-2 board of
Overkiz SAS based on SAMA5D31 SoC.
Signed-off-by: Kamel Bouhara
---
Changes in v2:
- Removed other kizbox2 boards as the main difference between
them is the usart configuration, only add the two heads variant
for now
There are several boards available depending on the PCB
(3 antennas support and several revison). Add a dtsi file to share
common binding between all kizbox2 boards. This patch also add support
for the kizbox2-2 variant.
Signed-off-by: Kévin RAYMOND
Signed-off-by: Mickael GARDET
Signed-off-by: K
On Mon, 21 Oct 2019, Lubomir Rintel wrote:
> On Mon, 2019-10-21 at 12:53 +0100, Lee Jones wrote:
> > On Mon, 21 Oct 2019, Lubomir Rintel wrote:
> >
> > > On Mon, 2019-10-21 at 13:29 +0200, Arnd Bergmann wrote:
> > > > On Mon, Oct 21, 2019 at 12:58 PM Lee Jones wrote:
> > > > > MFD currently has
On 16/10/19 18:23, Sean Christopherson wrote:
>> Yes we can get fancy, but remember that KVM is not yet supporting
>> emulation of locked instructions. Adding it is possible but shouldn't
>> be in the critical path for the whole feature.
> Ah, didn't realize that. I'm surprised emulating all lock
On 16/10/19 19:42, Sean Christopherson wrote:
> KVM uses a locked cmpxchg in emulator_cmpxchg_emulated() and the address
> is guest controlled, e.g. a guest could coerce the host into disabling
> split-lock detection via the host's #AC handler by triggering emulation
> and inducing an #AC in the em
On Mon, Oct 21, 2019 at 02:39:19PM +0800, Dilip Kota wrote:
> Add support to PCIe RC controller on Intel Gateway SoCs.
> PCIe controller is based of Synopsys DesignWare pci core.
>
> Intel PCIe driver requires Upconfig support, fast training
> sequence configuration and link speed change. So addin
On Mon 2019-10-21 14:42:14, Peter Zijlstra wrote:
> On Mon, Aug 19, 2019 at 12:47:30PM +0200, Petr Mladek wrote:
> > Some bug report included the same softlockups in flush_tlb_kernel_range()
> > in regular intervals. Unfortunately was not clear if there was a progress
> > or not.
> >
> > The situa
On Mon 2019-10-21 14:45:18, Peter Zijlstra wrote:
> On Mon, Aug 19, 2019 at 12:47:32PM +0200, Petr Mladek wrote:
> > Trigger busy loop by:
> > $> cat /proc/version
> >
> > Stop the busy loop by:
> > $> cat /proc/consoles
> >
> > The code also shows the first touch*watchdog() function that hides
>
On Mon, Oct 21, 2019 at 02:19:01PM +0200, Rasmus Villemoes wrote:
> On 21/10/2019 13.33, Christian Brauner wrote:
> > The first approach used smp_load_acquire() and smp_store_release().
> > However, after having discussed this it seems that the data dependency
> > for kmem_cache_alloc() would be fi
On 2019/10/19 5:25 上午, Eyal Birger wrote:
Hi,
On Fri, 18 Oct 2019 00:33:53 +0800
Zhiyuan Hou wrote:
On 2019/10/16 8:13 下午, Eyal Birger wrote:
Hi,
On Wed, 16 Oct 2019 01:22:01 +0800
Zhiyuan Hou wrote:
On 2019/10/15 1:57 上午, Cong Wang wrote:
On Sat, Oct 12, 2019 at 12:16 AM Zhiyuan Ho
On 17/10/19 03:23, Xiaoyao Li wrote:
> However, without force_emulation_prefix enabled, I'm not sure whether
> malicious guest can create the case causing the emulation with a lock
> prefix and going to the emulator_cmpxchg_emulated().
> I found it impossible without force_emulation_prefix enabled
On 17/10/19 18:05, Sean Christopherson wrote:
> On Wed, Oct 16, 2019 at 11:41:05AM +0200, Paolo Bonzini wrote:
>> On 16/10/19 09:48, Xiaoyao Li wrote:
>>> BTW, could you have a look at the series I sent yesterday to refactor
>>> the vcpu creation flow, which is inspired partly by this issue. Any
>>
On Mon, Oct 21, 2019 at 02:35:49PM +0200, Peter Zijlstra wrote:
> On Fri, Oct 18, 2019 at 08:33:11AM -0700, Randy Dunlap wrote:
> > On 10/18/19 12:03 AM, Stephen Rothwell wrote:
> > > Hi all,
> > >
> > > Changes since 20191017:
> > >
> >
> > on x86_64:
> > lib/usercopy.o: warning: objtool: check
The J721e platform comes with 2 Cadence USB3 controller
instances. This driver supports the TI specific wrapper
on this platform.
Signed-off-by: Roger Quadros
Signed-off-by: Sekhar Nori
---
drivers/usb/cdns3/Kconfig| 10 ++
drivers/usb/cdns3/Makefile | 1 +
drivers/usb/cdns3/cdns3-ti.c
TI platforms have a wrapper module around the Cadence USB3
controller. Add binding information for that.
Cc: Rob Herring
Signed-off-by: Roger Quadros
Signed-off-by: Sekhar Nori
---
.../devicetree/bindings/usb/ti,j721e-usb.txt | 52 +++
1 file changed, 52 insertions(+)
create
Hi,
Texas Instruments SoCs have a wrapper module around the Cadence
USB3 core. It takes care of clocking and powering the core and providing
initial configuration to the core.
This series adds the driver for the TI wrapper and associated DT binding
document. This is for -next kernel. Thanks.
che
On 10/18/19 9:50 AM, Maxime Jourdan wrote:
> On Wed, Oct 9, 2019 at 2:01 PM Hans Verkuil wrote:
>>
>> On 10/8/19 3:40 PM, Maxime Jourdan wrote:
>>> On 07/10/2019 18:39, Hans Verkuil wrote:
On 10/7/19 6:24 PM, Maxime Jourdan wrote:
> On 07/10/2019 17:12, Hans Verkuil wrote:
>> On 10/7/
301 - 400 of 1182 matches
Mail list logo
