Hi Heiko,
On Sat, 13 Jun 2020 11:24:35 +0100
Marc Zyngier wrote:
> Booting a recent kernel on a rk3399-based system (nanopc-t4),
> equipped with a recent u-boot and ATF results in the following:
>
> [5.607431] Unable to handle kernel NULL pointer dereference at virtual
> address 00
Add support for Ethernet Backplane KR driver only on DPAA1 devices.
Ethernet Backplane KR generic driver is using link training
(ieee802.3ap/ba standards), equalization algorithms (bee, fixed) and
enable qoriq family of devices.
This driver is dependent on uboot Backplane KR support:
patchwork.ozla
Add ethernet backplane documentation
Signed-off-by: Florinel Iordache
---
Documentation/networking/backplane.rst | 159 +
Documentation/networking/phy.rst | 9 +-
2 files changed, 165 insertions(+), 3 deletions(-)
create mode 100644 Documentation/networki
Add support for bee equalization algorithm used by kr training:
3-Taps Bit Edge Equalization (BEE) algorithm
Signed-off-by: Florinel Iordache
---
drivers/net/phy/backplane/Kconfig | 11 +
drivers/net/phy/backplane/Makefile |1 +
drivers/net/phy/backplane/eq_bee.c | 1076 ++
Add ethernet backplane device tree bindings
Signed-off-by: Florinel Iordache
---
.../bindings/net/ethernet-controller.yaml | 7 ++-
.../devicetree/bindings/net/ethernet-phy.yaml | 50 ++
.../devicetree/bindings/net/serdes-lane.yaml | 49 ++
Add kr support in mac driver for dpaa1
Signed-off-by: Florinel Iordache
---
drivers/net/ethernet/freescale/fman/mac.c | 10 --
1 file changed, 8 insertions(+), 2 deletions(-)
diff --git a/drivers/net/ethernet/freescale/fman/mac.c
b/drivers/net/ethernet/freescale/fman/mac.c
index 43427c
Add dt nodes with serdes, lanes, mdio generic description for supported
platform: ls1046. This is a prerequisite to enable backplane on device
tree for these platforms.
Signed-off-by: Florinel Iordache
---
arch/arm64/boot/dts/freescale/fsl-ls1046a.dtsi | 33 +-
.../boot/d
Enable backplane support for qoriq family of devices
Signed-off-by: Florinel Iordache
---
drivers/net/phy/backplane/Kconfig| 11 +-
drivers/net/phy/backplane/Makefile | 2 +
drivers/net/phy/backplane/qoriq_backplane.c | 473 ++
drivers/net/phy/ba
Add support for backplane kr generic driver including link training
(ieee802.3ap/ba) and fixed equalization algorithm
Signed-off-by: Florinel Iordache
---
drivers/net/phy/Kconfig |2 +
drivers/net/phy/Makefile |1 +
drivers/net/phy/backplane/Kconfig
The INIT_B pin reports the status during startup and after the end of the
programming process. However the current driver completely ignores it.
Check the pin status during startup to make sure programming is never
started too early and also to detect any hardware issues in the FPGA
connection.
T
The INIT_B is used by the 6 and 7 series to report the programming status,
providing more control and information about programming errors.
Signed-off-by: Luca Ceresoli
---
Changes in v2:
- rename init_b-gpios to init-b-gpios (Rob Herring suggested to not use '_'
in property names)
---
...
On Sun, Jun 21, 2020 at 08:50:09PM -0700, Linus Torvalds wrote:
> On Sun, Jun 21, 2020 at 8:02 PM Jason A. Donenfeld wrote:
> >
> > This reverts commit 8ece3b3eb576a78d2e67ad4c3a80a39fa6708809.
> >
> > This commit broke userspace. Bash uses ESPIPE to determine whether or
> > not the file should be
Add support for Ethernet Backplane KR driver only on DPAA1 devices.
Ethernet Backplane KR generic driver is using link training
(ieee802.3ap/ba standards), equalization algorithms (bee, fixed) and
enable qoriq family of devices.
This driver is dependent on uboot Backplane KR support:
patchwork.ozla
Commit ed318a6cc0b6 ("fscrypt: support test_dummy_encryption=v2") added an
entry to the massive option table in Documentation/filesystems/f2fs.txt.
The option was too wide for the formatting of the table, though, leading to
a verbose and ugly docs-build warning starting with:
Documentation/fil
On Mon, Jun 22, 2020 at 11:37:38AM +0200, Bartosz Golaszewski wrote:
> From: Bartosz Golaszewski
>
> Currently the PHY ID is read without taking the PHY out of reset. This
> can only work if no resets are defined. This change delays the ID read
> until we're actually registering the PHY device -
22.06.2020 01:29, Laurent Pinchart пишет:
> Hi Dmitry,
>
> Thank you for the patch.
>
> On Mon, Jun 22, 2020 at 01:27:41AM +0300, Dmitry Osipenko wrote:
>> The EDT ET057090DHU panel has a DPI connector and not LVDS. This patch
>> corrects the panel's description.
>>
>> Reported-by: Laurent Pincha
On 6/22/20 3:26 PM, Kurt Van Dijck wrote:
> On ma, 22 jun 2020 14:54:15 +0200, Marc Kleine-Budde wrote:
>> On 6/22/20 2:43 PM, Kurt Van Dijck wrote:
>>> I get RX-0: FIFO overflows in listen-only mode (back-to-back burst of
>>> the single other node).
>>
>> Single other node? Who's ACKing the CAN fr
On Wed, 17 Jun 2020 11:54:56 +0100, Steven Price wrote:
> If SVE is enabled then 'ret' can be assigned the return value of
> kvm_vcpu_enable_sve() which may be 0 causing future "goto out" sites to
> erroneously return 0 on failure rather than -EINVAL as expected.
>
> Remove the initialisation of '
On 6/22/20 1:58 AM, Vinod Koul wrote:
So we had some discussions of the stream states, so I thought it is a
good idea to document the state transitions, so add it documentation
Signed-off-by: Vinod Koul
---
.../sound/designs/compress-offload.rst| 52 +++
1 file cha
On 6/22/20 12:34 AM, Vinod Koul wrote:
On 19-06-20, 09:27, Pierre-Louis Bossart wrote:
+For Gapless, we move from running state to partial drain and back, along
+with setting of meta_data and signalling for next track ::
+
+
++--+
+
On Mon, 22 Jun 2020 10:30:18 +0200
Peter Enderborg wrote:
> This is a preparation for debugfs restricted mode.
> We don't need debugfs to trace, the removed check stop tracefs to work
> if debugfs is not initialised. We instead tries to automount within
> debugfs and relay on it's handling. The c
: 6 weeks ago
config: x86_64-randconfig-a003-20200622 (attached as .config)
compiler: gcc-9 (Debian 9.3.0-13) 9.3.0
reproduce (this is a W=1 build):
git checkout 49e649c3e0a6ec8a12976e331a2c1f29dc7dd3a9
# save the attached .config to linux build tree
make W=1 ARCH=x86_64
If
Florinel Iordache would like to recall the message, "[PATCH net-next v2 0/9]
net: ethernet backplane support on DPAA1".
On Mon, Jun 22, 2020 at 03:39:40PM +0200, Andrew Lunn wrote:
> The PHY subsystem cannot be the first to run into this problem, that
> you need a device structure to make use of the regulator API, but you
> need the regulator API to probe the device. How do other subsystems
> work around this?
If
Hi Marc,
Am Montag, 22. Juni 2020, 15:31:55 CEST schrieb Marc Zyngier:
> On Sat, 13 Jun 2020 11:24:35 +0100
> Marc Zyngier wrote:
>
> > Booting a recent kernel on a rk3399-based system (nanopc-t4),
> > equipped with a recent u-boot and ATF results in the following:
> >
> > [5.607431] Unable
On 20/06/20 00:45, Jim Mattson wrote:
>> + /*
>> +* TODO: if both L0 and L1 need the same MASK and MATCH,
>> +* go ahead and use it?
>> +*/
> I'm not sure there's much "TODO", since L0's MASK and MATCH are both
> 0. So, if L1's MASK and
> On 22 June 2020 at 14:27 Richard Weinberger
> wrote:
>
>
> On Mon, Jun 22, 2020 at 2:02 PM Thomas Ruf wrote:
> > > more the reason not do do so, why cant a kernel driver be added for your
> > > usage?
> >
> > by chance i have written a driver allowing dma from user space using a
> > memcpy
On 2020-06-21 17:49, Frank Rowand wrote:
> On 2020-06-21 17:45, Frank Rowand wrote:
>> Tim Bird started a thread [1] proposing that he document the selftest result
>> format used by Linux kernel tests.
>>
>> [1]
>> https://lore.kernel.org/r/cy4pr13mb1175b804e31e502221bc8163fd...@cy4pr13mb1175.na
From: "Rafael J. Wysocki"
Implement acpi_os_unmap_deferred() and
acpi_os_release_unused_mappings() and set ACPI_USE_DEFERRED_UNMAPPING
to allow ACPICA to use deferred unmapping of memory in
acpi_ex_system_memory_space_handler() so as to avoid RCU-related
performance issues with memory opregions.
> On 22 June 2020 at 14:30 Federico Vaga wrote:
>
>
> On Mon, Jun 22, 2020 at 02:01:12PM +0200, Thomas Ruf wrote:
> >> On 22 June 2020 at 06:47 Vinod Koul wrote:
> >>
> >> On 21-06-20, 22:36, Federico Vaga wrote:
> >> > On Sun, Jun 21, 2020 at 12:54:57PM +0530, Vinod Koul wrote:
> >> > > On 1
From: "Rafael J. Wysocki"
The ACPICA's strategy with respect to the handling of memory mappings
associated with memory operation regions is to avoid mapping the
entire region at once which may be problematic at least in principle
(for example, it may lead to conflicts with overlapping mappings
ha
From: "Rafael J. Wysocki"
Add acpi_os_map_memory_fast_path() and set ACPI_USE_FAST_PATH_MAPPING
to allow acpi_ex_system_memory_space_handler() to avoid unnecessary
memory mapping and unmapping overhead by retaining all memory
mappings created by it until the memory opregions associated with
them
From: "Rafael J. Wysocki"
The ACPI OS layer in Linux uses RCU to protect the walkers of the
list of ACPI memory mappings from seeing an inconsistent state
while it is being updated. Among other situations, that list can
be walked in (NMI and non-NMI) interrupt context, so using a
sleeping lock t
Hi All,
This series is to address the problem with RCU synchronization occurring,
possibly relatively often, inside of acpi_ex_system_memory_space_handler(),
when the namespace and interpreter mutexes are held.
Like I said before, I had decided to change the approach used in the previous
iteratio
Ping
On 6/5/20 5:39 PM, Tony Krowiak wrote:
Note: Patch 1 - s390/ap: introduce new ap function ap_get_qdev() - is not
a part of this series. It is a forthcoming patch that is a
prerequisite to this series and is being provided so this series
will compile.
The current design
On 22.06.2020 15:11, Jiri Olsa wrote:
> On Mon, Jun 22, 2020 at 01:50:03PM +0300, Alexey Budankov wrote:
>>
>> On 22.06.2020 13:21, Jiri Olsa wrote:
>>> On Mon, Jun 22, 2020 at 12:47:19PM +0300, Alexey Budankov wrote:
>>>
>>> SNIP
>>>
>> fdarray__del(array, fdkey);
>
> I thi
On 22.06.20 15:10, Wei Yang wrote:
> On Mon, Jun 22, 2020 at 11:51:34AM +0200, David Hildenbrand wrote:
>> On 22.06.20 11:22, Wei Yang wrote:
>>> On Mon, Jun 22, 2020 at 10:43:11AM +0200, David Hildenbrand wrote:
On 22.06.20 10:26, Wei Yang wrote:
> On Fri, Jun 19, 2020 at 02:59:20PM +0200
On 6/21/20 2:53 PM, William Breathitt Gray wrote:
Synapses simply indicate a change in a Count value
Ah, ok. I understand now that synapse is the wrong term for things like
the change in direction event or error events.
For example, in the dual-axes positioning table scenario, a user
applicat
+ linux-wireless
kernel test robot writes:
> tree: https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git
> master
> head: 5e857ce6eae7ca21b2055cca4885545e29228fe2
> commit: 9c29da3f4e7ef9810bdfaf3d8aa5e6d2e33136f8 brcmfmac: Fix P2P
> Group Formation failure via Go-neg method
>
Hello, I have sent you this message earlier, but your failure to
respond, Please get back to me.Best Regard,Mr.David Keller.
If the UVC_QUIRK_IGNORE_SELECTOR_UNIT flag is set, then there is a
problem that the code uses "iterm" after the end of the
list_for_each_entry() loop. It should only be used when the
UVC_ENTITY_IS_ITERM() condition is true and we break from the loop.
Fixes: d5e90b7a6cd1 ("[media] uvcvideo: Move t
On 22.06.20 11:22, Wei Yang wrote:
> On Mon, Jun 22, 2020 at 10:43:11AM +0200, David Hildenbrand wrote:
>> On 22.06.20 10:26, Wei Yang wrote:
>>> On Fri, Jun 19, 2020 at 02:59:20PM +0200, David Hildenbrand wrote:
Especially with memory hotplug, we can have offline sections (with a
garbage
Good day
Is this email private for discussion and personal to you?
Em Mon, Jun 22, 2020 at 03:04:07PM +0200, Borislav Petkov escreveu:
> On Mon, Jun 22, 2020 at 11:38:24AM +1000, Stephen Rothwell wrote:
> > I applied that patch to the tip tree merge today.
> >
> > Tested-by: Stephen Rothwell # build tested
>
> Here's v2 instead, addressing acme's request. I did
Flavio Suligoi writes:
> Fix typo: "EZUSB_REQUEST_TRIGER" --> "EZUSB_REQUEST_TRIGGER"
>
> Signed-off-by: Flavio Suligoi
> ---
> drivers/net/wireless/intersil/orinoco/orinoco_usb.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
The prefix should be "orinoco_usb: ", but I can fix
Hi, Hsin-Yi:
Hsin-Yi Wang 於 2020年6月22日 週一 下午1:32寫道：
>
> Disable the plane if it's not visible. Otherwise mtk_ovl_layer_config()
> would proceed with invalid plane and we may see vblank timeout.
Except the Fixes tag,
Reviewed-by: Chun-Kuang Hu
>
> Signed-off-by: Hsin-Yi Wang
> ---
> drivers/
Hi Laurent,
Thanks for the comment.
>-Original Message-
>From: Laurent Pinchart
>Sent: Wednesday, June 17, 2020 3:18 AM
>To: Venkateshwar Rao Gannavarapu
>Cc: Hyun Kwon ; dri-de...@lists.freedesktop.org;
>airl...@linux.ie; dan...@ffwll.ch; linux-kernel@vger.kernel.org; Sandip Kothari
>;
On Wed, Jun 17, 2020 at 12:38:48PM +0100, Alexandru Elisei wrote:
> From: Julien Thierry
>
> perf_event_overflow() can queue an irq_work on the current PE, which is
> executed via an IPI. Move the processing of the irq_work from the PMU IRQ
> handler to the IPI handler, which gets executed immedi
From: Borislav Petkov
> The whitelist is still TBD, I might be able to remove it competely and defer
> the
> whole whitelisting to the future. when people start reporting MSRs (see
> pr_err_ratelimited() call below).
I am also working on a similar functionality where we allow specific
MSRs(whi
On Thu, Jun 18, 2020 at 04:44:13PM -0600, Rob Herring wrote:
> Convert the common GPIO, LED, and PWM backlight bindings to DT schema
> format.
>
> Given there's only 2 common properties and the descriptions are slightly
> different, I opted to not create a common backlight schema.
>
> Cc: Lee Jon
On Mon 22-06-20 11:04:39, Mel Gorman wrote:
> On Mon, Jun 22, 2020 at 06:40:20PM +0900, ? wrote:
> > >But more importantly, I have hard time to follow why we need both
> > >zone_watermark_fast and zone_watermark_ok now. They should be
> > >essentially the same for anything but order == 0. F
On Mon, Jun 22, 2020 at 04:35:21PM +0300, Florinel Iordache wrote:
> Add support for backplane kr generic driver including link training
> (ieee802.3ap/ba) and fixed equalization algorithm
Hi Florinel
This is still a PHY device. I don't remember any discussions which
resolved the issues of if at
Hi Quentin,
Quoting Quentin Schulz (2020-06-21 17:38:42)
> On 2020-06-19 14:22, Antoine Tenart wrote:
> > This patch takes in account the use of the 1588 block in the MACsec
> > initialization, as a conditional configuration has to be done (when the
> > 1588 block is used).
> >
> > Signed-off-by:
This reverts commit 44331189f9082c7e659697bbac1747db3def73e7.
Now that the VL805 init routine is run through a reset controller driver
the device dependencies are being taken care of by the device core. No
need to do it manually here.
Signed-off-by: Nicolas Saenz Julienne
Reviewed-by: Florian Fa
> When adding first socket to nbd,
…
Can the term “network block device” matter for this change description?
> … A memory leak will occur
> then because the function "nbd_config_put" will free "config->socks" only
> when "config->num_connections" is not zero.
Will an additional imperative wor
Hello,
This patch series adds initial Device Trees for Realtek RTD1319 SoC and
Realtek Pym Particles EVB.
This v4 is an update of James' v3, incorporating pending review comments.
Upstreaming progress being tracked at:
https://en.opensuse.org/HCL:Realtek_DHC
Latest experimental patches at:
http
On 18. 06. 20, 18:47, Andy Shevchenko wrote:
> For unifying console ->setup() handling, which is pure documented,
Did you mean s/pure/poorly/ in all the patches? Or purely? But then where?
> return error code, rather than non-zero arbitrary number.
>
> Signed-off-by: Andy Shevchenko
> Cc: Thoma
This reverts commit c65822fef4adc0ba40c37a47337376ce75f7a7bc.
The initialization of Raspberry Pi 4's USB chip is now handled through a
reset controller. No need to directly call the firmware routine trough a
pci quirk.
Signed-off-by: Nicolas Saenz Julienne
Reviewed-by: Florian Fainelli
---
dri
From: James Tai
Add Device Trees for Realtek RTD1319 SoC family, RTD1319 SoC and
Realtek Pym Particles EVB.
Signed-off-by: James Tai
Signed-off-by: Andreas Färber
---
v3 -> v4:
* Updated Realtek copyright for 2 out of 3 files from v3
* Renamed from rtd1319-pymparticle.dts to rtd1319-pympart
Turn the SoC-level comments into description properties.
Signed-off-by: Andreas Färber
---
v4: New
.../devicetree/bindings/arm/realtek.yaml | 24 +--
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/realtek.yaml
b/Docu
Some atypical users of xhci-pci might need to manually reset their xHCI
controller before starting the HCD setup. Check if a reset controller
device is available to the PCI bus and trigger a reset.
Signed-off-by: Nicolas Saenz Julienne
Acked-by: Mathias Nyman
Reviewed-by: Philipp Zabel
---
Ch
From: James Tai
Define compatible strings for Realtek RTD1319 SoC and Realtek Pym Particles
EVB.
Signed-off-by: James Tai
Signed-off-by: Andreas Färber
---
v3 -> v4:
* Renamed compatible from pymparticle to pym-particles
* Turned SoC comment into description
v2 -> v3: Unchanged
v1 ->
On 6/22/20 3:03 AM, Johnson CH Chen (陳昭勳) wrote:
> Here provide Watchdog function from rtc-ds1374.c which is in RTC subsystem
> originally. Besides, add nowayout and implement Watchdog margin time when
> DS1374 Watchdog device is found.
>
> Signed-off-by: Johnson Chen
> ---
> drivers/watchdog/Kc
Now that the reset driver exposing Raspberry Pi 4's firmware based USB
reset routine is available, let's add the device tree node exposing it.
Signed-off-by: Nicolas Saenz Julienne
Reviewed-by: Florian Fainelli
---
Changes since v1:
- Update cell nr to match new bindings
arch/arm/boot/dts/b
Hello,
This patch series adds initial Device Trees for Realtek RTD1319 SoC and
Realtek Pym Particles EVB.
This v4 is an update of James' v3, incorporating pending review comments.
Upstreaming progress being tracked at:
https://en.opensuse.org/HCL:Realtek_DHC
Latest experimental patches at:
http
On Mon, Jun 22, 2020 at 12:14:13PM +0100, Lee Jones wrote:
> On Mon, 22 Jun 2020, Johnson CH Chen (陳昭勳) wrote:
>
> > Dallas/Maxim DS1374 is a counter designed to continuously count
> > time in seconds. It provides an I2C interface to the host to
> > access RTC clock or Alarm/Watchdog timer.
> >
>
From: Daniel Thompson
Add a generic NMI fallback to support kgdb NMI console feature which can
be overridden by arch specific implementation.
This common fallback mechanism utilizes kgdb IO based interrupt in order
to support entry into kgdb if a user types in kgdb_nmi_magic sequence. So
during
Support kgdb NMI console feature via implementing poll_get_irq()
interface. This will allow usage of RX interrupts to support kgdb entry
while serial device is operating in polling mode.
Signed-off-by: Sumit Garg
---
drivers/tty/serial/amba-pl011.c | 12
1 file changed, 12 insertion
Traditionally, kgdb NMI console relied on cmdline option "console=" to
enable/disable consoles. But it didn't took into account DT/ACPI modes
which can also provide default preferred console that can be enabled
prior to kgdb NMI console. And if that default preferred console is
used for debug IO op
From: Daniel Thompson
Support kgdb NMI console feature via implementing poll_get_irq()
interface. This will allow usage of RX interrupts to support kgdb entry
while serial device is operating in polling mode.
Signed-off-by: Daniel Thompson
Signed-off-by: Sumit Garg
---
drivers/tty/serial/8250
From: Daniel Thompson
Add new API: poll_get_irq() to the polling interface in order for user
of polling interface to retrieve allocated IRQ corresponding to
underlying serial device.
Although, serial interface still works in polling mode but interrupt
associated with serial device can be leverag
Raspberry Pi 4's co-processor controls some of the board's HW
initialization process, but it's up to Linux to trigger it when
relevant. Introduce a reset controller capable of interfacing with
RPi4's co-processor that models these firmware initialization routines as
reset lines.
Signed-off-by: Nic
This work is derived from Daniel's prior work here [1]. It has been
rebased (tag: kgdb-5.8-rc1 + console hardening patch-set[2]), reworked
to use serial RX interrupt as NMI (pseudo NMI on aarch64) in order to
drop into debugger and tested on Developerbox (using amba-pl011).
- Patch #1 is more of a
From: Daniel Thompson
Add request_nmi() callback to install a non-maskable interrupt handler
corresponding to IRQ retrieved from polling interface. If NMI handler
installation fails due to missing support from underlying irqchip driver
then fallback to install it as normal interrupt handler.
Sig
The chip is hardwired to the board's PCIe bus and needs to be properly
setup trough a firmware routine after a PCI fundamental reset. Pass the
reset controller phandle that takes care of triggering the
initialization to the relevant PCI device.
Signed-off-by: Nicolas Saenz Julienne
---
Changes
From: James Tai
Define compatible strings for Realtek RTD1319 SoC and Realtek Pym Particles
EVB.
Signed-off-by: James Tai
Signed-off-by: Andreas Färber
---
v3 -> v4:
* Renamed compatible from pymparticle to pym-particles
* Turned SoC comment into description
v2 -> v3: Unchanged
v1 ->
The board doesn't need the quirks to be run, and takes care of its own
initialization through a reset controller device. So let's bypass them.
Signed-off-by: Nicolas Saenz Julienne
Reviewed-by: Florian Fainelli
---
Changes since v2:
- Correct reference counting on parent device node
Changes
On 2020/6/18 06:33, Gustavo A. R. Silva wrote:
> Make use of the struct_size() helper instead of an open-coded version
> in order to avoid any potential type mistakes.
>
> This code was detected with the help of Coccinelle and, audited and
> fixed manually.
>
> Signed-off-by: Gustavo A. R. Silva
The firmware running on the RPi VideoCore can be used to reset and
initialize HW controlled by the firmware.
Signed-off-by: Nicolas Saenz Julienne
Reviewed-by: Florian Fainelli
---
Changes since v2:
- Add include file for reset IDs
Changes since v1:
- Correct cells binding as per Florian's c
From: James Tai
Add Device Trees for Realtek RTD1319 SoC family, RTD1319 SoC and
Realtek Pym Particles EVB.
Signed-off-by: James Tai
Signed-off-by: Andreas Färber
---
v3 -> v4:
* Updated Realtek copyright for 2 out of 3 files from v3
* Renamed from rtd1319-pymparticle.dts to rtd1319-pympart
On 19. 06. 20, 18:28, Andrzej Pietrasiewicz wrote:
> There exist machines which don't have SysRq key at all, e.g. chromebooks.
>
> This patch allows configuring an alternative key to act as SysRq. Devices
> which declare KEY_SYSRQ in their 'keybit' bitmap continue using KEY_SYSRQ,
> but other devi
Hi Alex,
On Thu, Jun 11, 2020 at 07:05:21PM -0400, Alex Xu (Hello71) wrote:
> I am using an ASRock B450 Pro4 with Ryzen 1600 and ASUS RX 480. I don't
> understand this code at all, but let me know what I can do to
> troubleshoot.
Does it boot without SME enabled?
Regards,
Joerg
Turn the SoC-level comments into description properties.
Signed-off-by: Andreas Färber
---
v4: New
.../devicetree/bindings/arm/realtek.yaml | 24 +--
1 file changed, 12 insertions(+), 12 deletions(-)
diff --git a/Documentation/devicetree/bindings/arm/realtek.yaml
b/Docu
From: Daniel Thompson
Currently kgdb_nmi relies on a 100Hz timer to "defer" work from an NMI
handler. This is essentially doing the job that irq_work is designed to
do but in an odd and inefficient manner. Remove the timer code and
replace it with more appropriate irq_work related APIs.
Signed-o
This reverts commit fbbc5ff3f7f9f4cad562e530ae2cf5d8964fe6d3.
The vl805 init routine has moved into drivers/reset/reset-raspberrypi.c
Signed-off-by: Nicolas Saenz Julienne
Reviewed-by: Florian Fainelli
---
drivers/firmware/raspberrypi.c | 61 --
include/soc/bcm2
On the Raspberry Pi 4, after a PCI reset, VL805's firmware may either be
loaded directly from an EEPROM or, if not present, by the SoC's
co-processor, VideoCore. This series reworks how we handle this.
The previous solution makes use of PCI quirks and exporting platform
specific functions. Albeit
On 22/06/2020 13:50, Wen Su wrote:
> Hi Matthias,
>
> On Mon, 2020-06-22 at 12:12 +0200, Matthias Brugger wrote:
>>
>> On 22/06/2020 08:40, Wen Su wrote:
>>> From: "Wen Su"
>>>
>>> add PMIC MT6359 related nodes which is for MT6779 platform
>>>
>>> Signed-off-by: Wen Su
>>> ---
>>> arch/arm64
Currently updates to Thunderbolt and USB4 controllers are fully atomic
actions. When writing into the non-active NVM nothing gets flushed to
the hardware until authenticate is sent.
There has been some desire to improve the perceived performance of these
updates, particularly for userland that may
This allows userspace to have a shorter period of time that the device
is unusable and to call it at a more convenient time.
For example flushing the image may happen while the user is using the
machine and authenticating/rebooting may happen while logging out.
Signed-off-by: Mario Limonciello
-
Some external devices can support completing thunderbolt authentication
when they are unplugged. For this to work though, the link controller must
remain operational.
The only device known to support this right now is the Dell WD19TB, so add
a quirk for this.
Signed-off-by: Mario Limonciello
---
On 2020-06-22 03:50, Lee Jones wrote:
> On Thu, 18 Jun 2020, Frank Rowand wrote:
>
>> On 2020-06-15 04:26, Lee Jones wrote:
>>> On Sun, 14 Jun 2020, Frank Rowand wrote:
>>>
Hi Lee,
I'm looking at 5.8-rc1.
The only use of OF_MFD_CELL() where the same compatible is specified
On Mon, Jun 22, 2020 at 2:32 AM Dave Chinner wrote:
> On Fri, Jun 19, 2020 at 08:50:36AM -0700, Matthew Wilcox wrote:
> >
> > This patch lifts the IOCB_CACHED idea expressed by Andreas to the VFS.
> > The advantage of this patch is that we can avoid taking any filesystem
> > lock, as long as the p
On 2020-06-22 09:32, Frank Rowand wrote:
> On 2020-06-22 03:50, Lee Jones wrote:
>> On Thu, 18 Jun 2020, Frank Rowand wrote:
>>
>>> On 2020-06-15 04:26, Lee Jones wrote:
On Sun, 14 Jun 2020, Frank Rowand wrote:
> Hi Lee,
>
> I'm looking at 5.8-rc1.
>
> The only use of
Hi Kalle,
>
> Flavio Suligoi writes:
>
> > Fix typo: "EZUSB_REQUEST_TRIGER" --> "EZUSB_REQUEST_TRIGGER"
> >
> > Signed-off-by: Flavio Suligoi
> > ---
> > drivers/net/wireless/intersil/orinoco/orinoco_usb.c | 6 +++---
> > 1 file changed, 3 insertions(+), 3 deletions(-)
>
> The prefix should
Roman Mamedov writes:
> On Sat, 4 Apr 2020 12:18:38 +0800
> Qiujun Huang wrote:
>
>> In ath9k_hif_usb_rx_cb interface number is assumed to be 0.
>> usb_ifnum_to_if(urb->dev, 0)
>> But it isn't always true.
>>
>> The case reported by syzbot:
>> https://lore.kernel.org/linux-usb/666c
On Mon, Jun 22, 2020 at 5:30 PM Jiri Slaby wrote:
>
> On 18. 06. 20, 18:47, Andy Shevchenko wrote:
> > For unifying console ->setup() handling, which is pure documented,
>
> Did you mean s/pure/poorly/ in all the patches? Or purely? But then where?
Poorly.
--
With Best Regards,
Andy Shevchenko
On 21.06.20 22:32, Kaaira Gupta wrote:
On Sat, Jun 20, 2020 at 12:05:28PM +0200, Dafna Hirschfeld wrote:
Hi, thanks for the patch
On 18.06.20 21:05, Kaaira Gupta wrote:
Add a control in VIMC to display information such as the correct oder of
colors for a given test pattern, brightness, hue,
On 6/20/20 9:32 AM, Linus Torvalds wrote:
> On Fri, Jun 19, 2020 at 8:14 PM Kees Cook wrote:
>>
>> On Wed, Jun 10, 2020 at 10:34:16AM -, tip-bot2 for Peter Zijlstra wrote:
>>> The following commit has been merged into the sched/urgent branch of tip:
>>>
>>> Commit-ID: bfb9fbe0f7e70ec5c8e51
On 22/06/20 00:26, Igor Mammedov wrote:
>
> following sequence looks like a race that can cause lost map update events:
>
> cpu1cpu2
>
> apic_map_dirty = true
> --
> -Original Message-
> From: Limonciello, Mario
> Sent: Monday, June 22, 2020 9:31 AM
> To: Andreas Noever; Michael Jamet; Mika Westerberg; Yehezkel Bernat
> Cc: linux-...@vger.kernel.org; linux-kernel@vger.kernel.org; Limonciello,
> Mario
> Subject: [PATCH 0/2] Allow breaking up Thunderbo
201 - 300 of 1785 matches
Mail list logo
