On Tue 04 Jun 03:44 PDT 2019, Lee Jones wrote:
> When booting with Device Tree, the current default boot configuration
> table option, the request to boot via 'host mode' comes from the
> "dr_mode" property.
This has been the default on the MTP, but this is changing as this is
causing issues when
Hi Pramod,
> From: Shawn Guo [mailto:shawn...@kernel.org]
> Sent: Wednesday, June 5, 2019 2:35 PM
> Subject: Re: [PATCH v3 1/3] dt-bindings: arm: nxp: Add device tree binding for
> ls1046a-frwy board
>
> On Mon, May 27, 2019 at 12:32:09PM +, Pramod Kumar wrote:
> > Add "fsl,ls1046a-frwy" bind
On Tue 04 Jun 03:44 PDT 2019, Lee Jones wrote:
> dwc3_qcom_clk_init() is called with of_count_phandle_with_args() as an
> argument. If of_count_phandle_with_args() returns an error, the number
> of clocks will be a negative value and will lead to undefined behaviour.
>
> Ensure we check for an e
On Wed 05-06-19 11:32:29, Bharath Vedartham wrote:
> In __alloc_pages_node, there is a VM_BUG_ON on the condition (nid < 0 ||
> nid >= MAX_NUMNODES). Remove this VM_BUG_ON and add a VM_WARN_ON, if the
> condition fails and fail the allocation if an invalid NUMA node id is
> passed to __alloc_pages_
Hi Shimoda-san,
On Wed, Jun 5, 2019 at 6:06 AM Yoshihiro Shimoda
wrote:
> > From: Geert Uytterhoeven, Sent: Wednesday, June 5, 2019 3:06 AM
> > Using a tree based on renesas-drivers-2019-06-04-v5.2-rc3, I started seeing
> > the following warning during a second system suspend (s2idle):
>
> > So
On Tue, 04 Jun 2019, Bjorn Andersson wrote:
> On Tue 04 Jun 03:44 PDT 2019, Lee Jones wrote:
> > diff --git a/drivers/usb/dwc3/dwc3-qcom.c b/drivers/usb/dwc3/dwc3-qcom.c
> [..]
> > @@ -373,7 +416,7 @@ static int dwc3_qcom_clk_init(struct dwc3_qcom *qcom,
> > int count)
> >
> > qcom->num_clo
On Tue, 2019-06-04 at 08:57 +0800, Nicolas Boichat wrote:
> On Mon, Jun 3, 2019 at 4:01 PM Chuanjia Liu wrote:
> >
> > On Fri, 2019-05-31 at 10:17 -0700, Evan Green wrote:
> > > On Fri, May 31, 2019 at 1:06 AM Chuanjia Liu
> > > wrote:
> > > >
> > > > On Thu, 2019-05-30 at 10:12 -0700, Evan Gree
On Tue, 04 Jun 2019, Bjorn Andersson wrote:
> On Tue 04 Jun 03:44 PDT 2019, Lee Jones wrote:
>
> > The Qualcomm Geni I2C driver currently probes silently which can be
> > confusing when debugging potential issues. Add a low level (INFO)
> > print when each I2C controller is successfully initiall
On Tue, May 28, 2019 at 08:45:06PM +0800, Chuanhua Han wrote:
> ls1028a platform uses sp805 watchdog, and use 1/16 platform clock as
> timer clock, this patch fix device tree node.
>
> Signed-off-by: Chuanhua Han
Applied, thanks.
/commits/Greg-Kroah-Hartman/USB-move-usb-debugfs-directory-creation-to-the-usb-common-core/20190605-114326
base: https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/usb.git
usb-testing
config: sh-allmodconfig (attached as .config)
compiler: sh4-linux-gcc (GCC) 7.4.0
reproduce:
wget
https
On Tue, Jun 04, 2019 at 11:17:48PM -0700, Christoph Hellwig wrote:
> > The following patches add the bare minimum tracepoints required to perform
> > EAS
> > testing in Lisa[1].
>
> What is EAS? Whhy is "Lisa" not part of the patch submission?
> submission.
>
> > It is done in this way because
On Wed, 5 Jun 2019 at 09:16, Lee Jones wrote:
>
> On Tue, 04 Jun 2019, Bjorn Andersson wrote:
>
> > On Tue 04 Jun 03:44 PDT 2019, Lee Jones wrote:
> >
> > > The Qualcomm Geni I2C driver currently probes silently which can be
> > > confusing when debugging potential issues. Add a low level (INFO)
Everyone:
This small series contains the code I wrote to expose various power
supply sensors via HWMON layer in order to be able to access all of
the sensors in the system with libsensors.
Changes since [v2]:
- Added missing static specified to devm_power_supply_add_hwmon_sysfs()
- Collec
Expose current sensors found on UCS1002 via HWMON.
Signed-off-by: Andrey Smirnov
Reviewed-by: Guenter Roeck
Cc: Chris Healy
Cc: Cory Tusar
Cc: Lucas Stach
Cc: Fabio Estevam
Cc: Guenter Roeck
Cc: Sebastian Reichel
Cc: linux-kernel@vger.kernel.org
Cc: linux...@vger.kernel.org
---
drivers/po
Add code implementing HWMON adapter/compatibility layer to allow
expositing various sensors present on power supply devices via HWMON
subsystem. This is done in order to allow userspace to use single
ABI/library(libsensors) to access/manipulate all of the sensors of the
system.
Signed-off-by: Andr
Hi,
Greg Kroah-Hartman writes:
>> Greg Kroah-Hartman writes:
>> > diff --git a/drivers/usb/core/usb.c b/drivers/usb/core/usb.c
>> > index 7fcb9f782931..f3d6b1ab80cb 100644
>> > --- a/drivers/usb/core/usb.c
>> > +++ b/drivers/usb/core/usb.c
>> > @@ -1185,19 +1185,17 @@ static struct notifier_blo
On Tue, 04 Jun 2019, Bjorn Andersson wrote:
> On Tue 04 Jun 03:44 PDT 2019, Lee Jones wrote:
>
> > This patch provides basic support for booting with ACPI instead
> > of the currently supported Device Tree. When doing so there are a
> > couple of differences which we need to taken into considera
Hi Bjorn,
On 6/5/19 6:34 AM, Bjorn Andersson wrote:
> On Thu 31 Jan 07:41 PST 2019, Xiang Xiao wrote:
>
>> Hi,
>> This series enhance the buffer allocation by:
>> 1.Support the different buffer number in rx/tx direction
>> 2.Get the individual rx/tx buffer size from config space
>>
>> Here is the
On 03/06/2019 14:00, Anand Moon wrote:
> Hi Niel,
>
> On Mon, 3 Jun 2019 at 14:41, Neil Armstrong wrote:
>>
>> This patch adds basic support for :
>> - Amlogic G12B, which is very similar to G12A
>> - The HardKernel Odroid-N2 based on the S922X SoC
>>
>> The Amlogic G12B SoC is very similar with
On Mon, May 27, 2019 at 05:34:10PM +0900, Masahiro Yamada wrote:
> Some in-kernel headers use _BITUL() instead of BIT().
>
> arch/arm64/include/asm/sysreg.h
> arch/s390/include/asm/*.h
>
> I think the reason is because BIT() is currently not available
> in assembly. It hard-codes 1UL, which is
On 04/06/2019 01:31, Kevin Hilman wrote:
> Neil Armstrong writes:
>
>> From: Jerome Brunet
>>
>> The Amlogic G12A SDIO Controller has a bug preventing direct DDR access,
>> add the port A (SDIO) pinctrl and controller nodes and mark this specific
>> controller with the amlogic,dram-access-quirk
On 03/06/2019 11:47, Neil Armstrong wrote:
> The 32k low power clock is necessary for the bluetooth part of the
> combo module to initialize correctly, simply add the same clock we
> use for the sdio pwrseq.
>
> Fixes: c5c9c7cff269 ("arm64: dts: meson-g12a-x96-max: Enable BT Module")
> Signed-off-
On 03/06/2019 11:47, Neil Armstrong wrote:
> The 32k low power clock is necessary for the bluetooth part of the
> combo module to initialize correctly, simply add the same clock we
> use for the sdio pwrseq.
>
> Fixes: d1c023af1988 ("arm64: dts: meson-g12a-sei510: Add ADC Key and BT
> support")
>
On Tue, May 28, 2019 at 8:05 PM Eduardo Valentin wrote:
>
> On Thu, May 23, 2019 at 07:48:56PM -0700, Andrey Smirnov wrote:
> > On Mon, Apr 29, 2019 at 9:51 AM Daniel Lezcano
> > wrote:
> > >
> > > On 24/04/2019 01:08, Daniel Lezcano wrote:
> > > > On 23/04/2019 17:44, Eduardo Valentin wrote:
> >
Roman Gushchin wrote:
> # Why do we need this?
>
> We've noticed that the number of dying cgroups is steadily growing on most
> of our hosts in production. The following investigation revealed an issue
> in userspace memory reclaim code [1], accounting of kernel stacks [2],
> and also the mainrea
Hi Waiman,
On Wed, 5 Jun 2019 at 00:00, Waiman Long wrote:
> With my patchset applied, the reader-writer ordering is still supposed
> to be preserved. Of course, there can be exceptions depending on the
> exact timing, but we can't rely on that to prevent deadlock.
This is exactly what I want to
On Tue, 2019-06-04 at 13:59 +0200, Greg Kroah-Hartman wrote:
> On Tue, Jun 04, 2019 at 11:32:58AM +0200, Greg Kroah-Hartman wrote:
> > The USB gadget subsystem wants to use the USB debugfs root directory, so
> > move it to the common "core" USB code so that it is properly initialized
> > and remove
On 6/3/2019 8:37 PM, Douglas Anderson wrote:
Normally when the MMC core sees an "-EILSEQ" error returned by a host
controller then it will trigger a retuning of the card. This is
generally a good idea.
However, if a command is expected to sometimes cause transfer errors
then these transfer erro
Hi
> On 3/06/19 4:48 PM, Ulf Hansson wrote:
> > + Adrian
> >
> > On Thu, 30 May 2019 at 11:20, Takao Orito wrote:
> >>
> >> SD Host controller on Milbeaut consists of two controller parts.
> >> One is core controller F_SDH30, this is similar to sdhci-fujitsu
> >> controller.
> >> Another is bri
The patch adds k3 am654 compatible, specific properties and
an example.
Signed-off-by: Keerthy
---
.../devicetree/bindings/gpio/gpio-davinci.txt | 18 ++
1 file changed, 18 insertions(+)
diff --git a/Documentation/devicetree/bindings/gpio/gpio-davinci.txt
b/Documentation/devic
Add gpio0 node under wakeup domain. This has 56 gpios
and all are capable of generating banked interrupts.
Signed-off-by: Keerthy
---
arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi | 15 +++
1 file changed, 15 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-am65-wakeup.dtsi
b/arch
On Wed, Jun 05, 2019 at 08:16:25AM +0100, Lee Jones wrote:
> On Tue, 04 Jun 2019, Bjorn Andersson wrote:
>
> > On Tue 04 Jun 03:44 PDT 2019, Lee Jones wrote:
> >
> > > The Qualcomm Geni I2C driver currently probes silently which can be
> > > confusing when debugging potential issues. Add a low l
There are 2 push buttons: SW5 and SW6 that are basically connected to
WKUP_GPIO0_24 and WKUP_GPIO0_27 respectively. Add the respective
nodes and the pinctrl data to set the mode to GPIO and Input.
Signed-off-by: Keerthy
---
.../arm64/boot/dts/ti/k3-am654-base-board.dts | 27 +++
K3 AM6 platform has 2 instances of gpio banks on main domain
and 1 instance on wakeup domin. All are capable of generating
banked interrupts.
This series also adds 2 goio_keys nodes connected to SW6 SW5
switches and tested for gpio_keys interrupts.
The series depends on:
https://patchwork.kernel.
Add gpio0/1 nodes under main domain. They have 96 and 90 gpios
respectively and all are capable of generating banked interrupts.
Signed-off-by: Keerthy
---
arch/arm64/boot/dts/ti/k3-am65-main.dtsi | 32
1 file changed, 32 insertions(+)
diff --git a/arch/arm64/boot/dts/t
On 6/5/19 1:30 AM, Mike Kravetz wrote:
> While looking at some really long hugetlb page allocation times, I noticed
> instances where should_compact_retry() was returning true more often that
> I expected. In one allocation attempt, it returned true 765668 times in a
> row. To me, this was unexpe
On Wed, Jun 05, 2019 at 09:54:12AM +0300, Talel Shenhar wrote:
> --- /dev/null
> +++ b/include/linux/irqchip/al-fic.h
> @@ -0,0 +1,21 @@
> +/* SPDX-License-Identifier: GPL-2.0 */
> +/**
> + * Copyright 2019 Amazon.com, Inc. or its affiliates. All Rights Reserved.
> + */
> +
> +#ifndef _AL_FIC_H_
>
On Wed, Jun 05, 2019 at 09:54:13AM +0300, Talel Shenhar wrote:
> The FIC supports either a (single) wired output, or generation of an MSI-X
> interrupt per input (for cases where it is embedded in a PCIe device,
> hence, allowing the PCIe drivers to call this API).
> This patch introduces the suppo
K3 AM6 platform has 2 instances of gpio banks on main domain
and 1 instance on wakeup domin. All are capable of generating
banked interrupts.
Changes in v2:
* Introduced a separate compatible for am654.
Documentation patch link: https://patchwork.kernel.org/patch/10976445/
Keerthy (3):
gpi
Fix the compiler warning with ARM64 config enabled
as the current mask assumes 32 bit by default.
Signed-off-by: Keerthy
---
drivers/gpio/gpio-davinci.c | 6 +++---
1 file changed, 3 insertions(+), 3 deletions(-)
diff --git a/drivers/gpio/gpio-davinci.c b/drivers/gpio/gpio-davinci.c
index 3bbf5
Add K3 dependencies to enable the driver on K3 platforms.
Signed-off-by: Keerthy
---
drivers/gpio/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/gpio/Kconfig b/drivers/gpio/Kconfig
index 62f3fe06cd2f..28dba62e2219 100644
--- a/drivers/gpio/Kconfig
+++ b/drive
Add new compatible for K3 AM654 SoCs.
Signed-off-by: Keerthy
---
drivers/gpio/gpio-davinci.c | 1 +
1 file changed, 1 insertion(+)
diff --git a/drivers/gpio/gpio-davinci.c b/drivers/gpio/gpio-davinci.c
index 0977590eb996..fc494a84a29d 100644
--- a/drivers/gpio/gpio-davinci.c
+++ b/drivers/gpio/
On 6/5/19 4:40 AM, xiang xiao wrote:
> On Tue, Jun 4, 2019 at 10:25 PM Arnaud Pouliquen
> wrote:
>>
>> Hello Xiang,
>>
>> On 5/9/19 3:00 PM, xiang xiao wrote:
>>> On Thu, May 9, 2019 at 8:36 PM Arnaud Pouliquen
>>> wrote:
Hello Xiang,
Similar mechanism has been proposed by
Hi,
Anurag Kumar Vulisha writes:
> As a process of preparing TRBs usb_gadget_map_request_by_dev() is
> called from dwc3_prepare_trbs() for mapping the request. This will
> call dma_map_sg() if req->num_sgs are greater than 0. dma_map_sg()
> will map the sg entries in sglist and return the number
On Wed, 05 Jun 2019, Johan Hovold wrote:
> On Wed, Jun 05, 2019 at 08:16:25AM +0100, Lee Jones wrote:
> > On Tue, 04 Jun 2019, Bjorn Andersson wrote:
> >
> > > On Tue 04 Jun 03:44 PDT 2019, Lee Jones wrote:
> > >
> > > > The Qualcomm Geni I2C driver currently probes silently which can be
> > > >
On Tue, Jun 04, 2019 at 08:04:04PM +0300, Andy Shevchenko wrote:
> On Tue, May 28, 2019 at 03:28:58PM +0100, Charles Keepax wrote:
> > Bring the ACPI path in sync with the device tree path and handle all the
> > IRQ fetching at probe time. This leaves the only IRQ handling at device
> > registratio
On Wed, 05 Jun 2019, Ard Biesheuvel wrote:
> On Wed, 5 Jun 2019 at 09:16, Lee Jones wrote:
> >
> > On Tue, 04 Jun 2019, Bjorn Andersson wrote:
> >
> > > On Tue 04 Jun 03:44 PDT 2019, Lee Jones wrote:
> > >
> > > > The Qualcomm Geni I2C driver currently probes silently which can be
> > > > confusi
On Wed, Jun 5, 2019 at 6:30 AM Eduardo Valentin wrote:
>
> Hey Andry,
>
> Long time no seeing :-)
True!
> > > +#define MQ_MSGBUF_SIZE CONFIG_I2C_SLAVE_MQUEUE_MESSAGE_SIZE
> > > +#define MQ_QUEUE_SIZE CONFIG_I2C_SLAVE_MQUEUE_QUEUE_SIZE
> >
> > > +#define MQ_QUEUE_NEXT(x)
On Tue, Jun 04, 2019 at 08:00:52PM +0300, Andy Shevchenko wrote:
> On Tue, May 28, 2019 at 03:28:56PM +0100, Charles Keepax wrote:
> > Use the available IRQ helper functions, most of the functions have
> > additional helpful side affects like configuring the trigger type of the
> > IRQ.
> >
>
> Y
On Sun, Jun 2, 2019 at 5:30 PM Emanuel Bennici
wrote:
>
> Check the return value of pci_hp_register() in Function
> ebda_rsrc_controller()
>
Maybe this is correct, maybe not.
You are changing behaviour of the function.
How did you test this?
> Signed-off-by: Emanuel Bennici
> ---
> drivers/pci
From: Bartosz Golaszewski
Extend the davinci-timer driver to also register a clock source.
Signed-off-by: Bartosz Golaszewski
---
drivers/clocksource/timer-davinci.c | 85 +
1 file changed, 85 insertions(+)
diff --git a/drivers/clocksource/timer-davinci.c
b/driver
From: Bartosz Golaszewski
Currently the clocksource and clockevent support for davinci platforms
lives in mach-davinci. It hard-codes many things, uses global variables,
implements functionalities unused by any platform and has code fragments
scattered across many (often unrelated) files.
Implem
From: Bartosz Golaszewski
This is another version of the new davinci clocksource driver. After much
discussion this contains many changes to simplify and improve the driver.
v1 -> v2:
- changed the format of the copyright notice
- removed all mentiones of the periodic timer setting
- added cachi
On Wed, Jun 05, 2019 at 09:20:47AM +0100, Lee Jones wrote:
> On Wed, 05 Jun 2019, Johan Hovold wrote:
> > No, we don't add noise like this to the logs just because it may be
> > useful while debugging. Even one-liners add up.
>
> One line per device is should not cause an issue.
>
> Problems occ
On Wed, 05 Jun 2019, Bjorn Andersson wrote:
> On Tue 04 Jun 03:44 PDT 2019, Lee Jones wrote:
>
> > When booting with Device Tree, the current default boot configuration
> > table option, the request to boot via 'host mode' comes from the
> > "dr_mode" property.
>
> This has been the default on t
On Wed, Jun 5, 2019 at 3:33 PM Arnaud Pouliquen wrote:
>
> Hi Bjorn,
>
> On 6/5/19 6:34 AM, Bjorn Andersson wrote:
> > On Thu 31 Jan 07:41 PST 2019, Xiang Xiao wrote:
> >
> >> Hi,
> >> This series enhance the buffer allocation by:
> >> 1.Support the different buffer number in rx/tx direction
> >>
On Wed, 2019-06-05 at 10:28 +0300, Felipe Balbi wrote:
> Hi,
>
> Greg Kroah-Hartman writes:
> >> Greg Kroah-Hartman writes:
> >> > diff --git a/drivers/usb/core/usb.c b/drivers/usb/core/usb.c
> >> > index 7fcb9f782931..f3d6b1ab80cb 100644
> >> > --- a/drivers/usb/core/usb.c
> >> > +++ b/drivers/
On Wed, Jun 5, 2019 at 4:02 PM Arnaud Pouliquen wrote:
>
>
>
> On 6/5/19 4:40 AM, xiang xiao wrote:
> > On Tue, Jun 4, 2019 at 10:25 PM Arnaud Pouliquen
> > wrote:
> >>
> >> Hello Xiang,
> >>
> >> On 5/9/19 3:00 PM, xiang xiao wrote:
> >>> On Thu, May 9, 2019 at 8:36 PM Arnaud Pouliquen
> >>> w
Hi Måns,
On 2019-05-22 12:54, Måns Rullgård wrote:
> Marek Szyprowski writes:
>> On 2019-05-21 15:30, Måns Rullgård wrote:
>>> Marek Szyprowski writes:
Commit 69bec7259853 ("USB: core: let USB device know device node") added
support for attaching devicetree node for USB devices. Those
If the three termios local flags isig, icanon, iexten are enabled
and the local flag nokerninfo is disabled for a tty governed
by the n_tty line discipline, then on receiving the keyboard status
character n_tty will generate a status message and write it out to
the tty before sending SIGINFO to the
There was no architecture we had to increase NCCS on,
so the size of struct termios did not change.
Signed-off-by: Arseny Maslennikov
---
arch/alpha/include/asm/termios.h | 4 ++--
arch/alpha/include/uapi/asm/termbits.h | 1 +
arch/ia64/include/asm/termios.h | 4 ++--
arch/ia6
This complementary patch defines SIGINFO as a synonym for SIGPWR
on every architecture supported by the kernel.
The particular signal number chosen does not really matter and is only
required for the related tty functionality to work properly,
so if it does not suite expectations, any suggestions a
This patch series introduces TTY keyboard status request, a feature of
the n_tty line discipline that reserves a character in struct termios
(^T by default) and reacts to it by printing a short informational line
to the terminal and sending a Unix signal to the tty's foreground
process group. The p
Signed-off-by: Arseny Maslennikov
---
arch/alpha/include/uapi/asm/termbits.h | 1 +
arch/ia64/include/uapi/asm/termbits.h| 1 +
arch/mips/include/uapi/asm/termbits.h| 1 +
arch/parisc/include/uapi/asm/termbits.h | 1 +
arch/powerpc/include/uapi/asm/termbits.h | 1 +
arch/sparc/include/
No kerninfo line is printed yet.
No existing implementation of this on any Unix-like system echoes
the status character; no existing implementation discards or flushes
pending input on VSTATUS receipt.
There are existing popular TUI applications (e. g. mutt) that only
turn off icanon and not iext
This matches the behaviour of other Unix-like systems that have SIGINFO
and causes less harm to processes that do not install handlers for this
signal, making the keyboard status character non-fatal for them.
This is implemented with the assumption that SIGINFO is defined
to be equivalent to SIGPW
To simplify internal re-use of the line discipline's write method,
we isolate the work it does to its own function.
Since in-kernel callers might not refer to the tty through a file,
the struct file* argument might make no sense, so we also stop
tty_io_nonblock() from dereferencing file too early,
On Sun, Jun 2, 2019 at 7:25 PM Emanuel Bennici
wrote:
>
> Fix checkpatch.pl 'line over 80 characters' Warning in ibmphp_ebda.c and
> ibmphp_hpc.c
I'm not sure it's needed.
And actually some of the changes are the regressions in order of
readability ratio.
> + debug(
Hi Trond,
I have been noticing intermittent failures with a system suspend test on
some of our machines that have a NFS mounted root file-system. Bisecting
this issue points to your commit 431235818bc3 ("SUNRPC: Declare RPC
timers as TIMER_DEFERRABLE") and reverting this on top of v5.2-rc3 does
ap
On Sun, Jun 2, 2019 at 7:35 PM Emanuel Bennici
wrote:
>
> The 'Exit' Debug message is superfluous ftrace can be used instead.
>
When reviewer gives you a comment in one entry, your job is to check
your entire series and address the same comment in other places.
There are many such unneeded debug
From: Peter Ujfalusi
J721E SoCs have same I2C IP as OMAP SoCs. Add new compatible to
handle J721E SoCs.
Signed-off-by: Peter Ujfalusi
Signed-off-by: Vignesh Raghavendra
---
Initial support for J721E Platform is proposed here:
https://lore.kernel.org/patchwork/cover/1077382/
Documentation/de
On Wed, May 29, 2019 at 10:44 AM Chunfeng Yun wrote:
>
> Due to the requirement of usb-connector.txt binding, the old way
> using extcon to support USB Dual-Role switch is now deprecated
> when use Type-B connector.
> This patch introduces a driver of Type-B connector which typically
> uses an inp
On Wed, 05 Jun 2019, Johan Hovold wrote:
> On Wed, Jun 05, 2019 at 09:20:47AM +0100, Lee Jones wrote:
> > On Wed, 05 Jun 2019, Johan Hovold wrote:
>
> > > No, we don't add noise like this to the logs just because it may be
> > > useful while debugging. Even one-liners add up.
> >
> > One line pe
On Wed, Jun 05, 2019 at 03:50:31PM +0800, Chunfeng Yun wrote:
> On Tue, 2019-06-04 at 13:59 +0200, Greg Kroah-Hartman wrote:
> > On Tue, Jun 04, 2019 at 11:32:58AM +0200, Greg Kroah-Hartman wrote:
> > > The USB gadget subsystem wants to use the USB debugfs root directory, so
> > > move it to the co
在 2019/6/4 23:24, Eric Dumazet 写道:
> On Tue, Jun 4, 2019 at 7:47 AM Mao Wenan wrote:
>>
>> There is one issue about bonding mode BOND_MODE_BROADCAST, and
>> two slaves with diffierent affinity, so packets will be handled
>> by different cpu. These are two pre-conditions in this case.
>> Signed
On Wed, Jun 05, 2019 at 09:49:21AM +0100, Lee Jones wrote:
> On Wed, 05 Jun 2019, Johan Hovold wrote:
>
> > On Wed, Jun 05, 2019 at 09:20:47AM +0100, Lee Jones wrote:
> > > On Wed, 05 Jun 2019, Johan Hovold wrote:
> > > > There are plenty of options for debugging already ranging from adding a
>
On 06/04, Linus Torvalds wrote:
>
> On Tue, Jun 4, 2019 at 6:41 AM Oleg Nesterov wrote:
> >
> > This is the minimal fix for stable, I'll send cleanups later.
>
> Ugh. I htink this is correct, but I wish we had a better and more
> intuitive interface.
Yes,
> In particular, since restore_user_sigm
Hi all, this is Philip who maintains the 0-Day CI test service.
Thanks for anyone who subscribing to the service. We will have a
major lab construction during next few days, thus need to pause
the service until Jun 11. Sorry for any inconvenience caused by
this, we will try our best to have it onli
On Mon, 6 May 2019 at 15:00, Marek Szyprowski wrote:
>
> Samsung Exynos SoCs require to force UTMI width to 8bit, otherwise the
> host side of the shared USB2 PHY doesn't work.
>
> Reported-by: Krzysztof Kozlowski
> Fixes: 707d80f0a3c5 ("usb: dwc2: gadget: Replace phyif with phy_utmi_width")
> Si
>> /*
>> * For now, we have a linear search to go find the appropriate
>> * memory_block corresponding to a particular phys_index. If
>> @@ -658,6 +670,11 @@ static int init_memory_block(struct memory_block
>> **memory, int block_id,
>> unsigned long start_pfn;
>> int ret = 0;
>>
>> +
On Wed, 2019-06-05 at 11:41 +0300, Andy Shevchenko wrote:
> On Sun, Jun 2, 2019 at 7:25 PM Emanuel Bennici
> wrote:
[]
> > + debug("%s - call process_changeinstatus for"
> > + "slot[%d]\n", __func__, i);
>
> Do not split string lit
On 05.06.19 00:07, Wei Yang wrote:
> On Mon, May 27, 2019 at 01:11:50PM +0200, David Hildenbrand wrote:
>> Let's factor out removing of memory block devices, which is only
>> necessary for memory added via add_memory() and friends that created
>> memory block devices. Remove the devices before call
On Wed, Jun 5, 2019 at 4:36 PM Catalin Marinas wrote:
>
> On Mon, May 27, 2019 at 05:34:10PM +0900, Masahiro Yamada wrote:
> > Some in-kernel headers use _BITUL() instead of BIT().
> >
> > arch/arm64/include/asm/sysreg.h
> > arch/s390/include/asm/*.h
> >
> > I think the reason is because BIT() i
Locking is not needed for the phy_g12a_usb3_pcie_cr_bus_read/write() and
currently it causes the following BUG because of the usage of the
regmap_read_poll_timeout() running in spinlock_irq, configured by regmap
fast_io.
Simply disable locking in the cr_regmap config since it's only used from the
From: Linus Torvalds
> Sent: 04 June 2019 22:27
> Ugh. I htink this is correct, but I wish we had a better and more
> intuitive interface.
>
> In particular, since restore_user_sigmask() basically wants to check
> for "signal_pending()" anyway (to decide if the mask should be
> restored by signal
On Tue, May 28, 2019 at 05:57:44AM -0700, Angus Ainslie (Purism) wrote:
> The Librem5 devkit is based on the imx8mq from NXP. This is a default
> devicetree to boot the board to a command prompt.
>
> Changes since v14:
>
> Add regulator-always-on for the SNVS regulators.
> Added pgc nodes.
> Fixe
On 06/04, Eric W. Biederman wrote:
>
> >> - restore_user_sigmask(ksig.sigmask, &sigsaved);
> >> - if (signal_pending(current) && !ret)
> >> +
> >> + interrupted = signal_pending(current);
> >> + restore_user_sigmask(ksig.sigmask, &sigsaved, interrupted);
> >> + if (int
On Tue, May 28, 2019 at 09:11:01AM -0700, Angus Ainslie (Purism) wrote:
> Add a node for the snvs power key, "disabled" by default.
>
> Signed-off-by: Angus Ainslie (Purism)
Applied, thanks.
From: Spyridon Papageorgiou
When a USB device fails to enumerate, only a kernel message is printed.
With this patch, a uevent is also generated to notify userspace.
Services can monitor for the event through udev and handle failures
accordingly.
The "port_enumerate_fail_notify()" function name f
On Tue, Jun 04, 2019 at 03:50:40PM -0700, kan.li...@linux.intel.com wrote:
> From: Kan Liang
>
> There is no function to retrieve die id information of a given CPU.
>
> Add cpu_map__get_die_id() to retrieve die id information.
>
> Signed-off-by: Kan Liang
> ---
>
> No changes since V2.
Revie
As for FOLL_LONGTERM, it is checked in the slow path
__gup_longterm_unlocked(). But it is not checked in the fast path, which
means a possible leak of CMA page to longterm pinned requirement through
this crack.
Place a check in the fast path.
Signed-off-by: Pingfan Liu
Cc: Ira Weiny
Cc: Andrew
To better reflect the held state of pages and make code self-explaining,
rename nr as nr_pinned.
Signed-off-by: Pingfan Liu
Cc: Ira Weiny
Cc: Andrew Morton
Cc: Mike Rapoport
Cc: Dan Williams
Cc: Matthew Wilcox
Cc: John Hubbard
Cc: "Aneesh Kumar K.V"
Cc: Keith Busch
Cc: Christoph Hellwig
On Tue, 2019-06-04 at 17:00 -0700, Eric Anholt wrote:
> Nicolas Saenz Julienne writes:
>
> > Registers clk-raspberrypi as a platform device as part of the driver's
> > probe sequence.
>
> Similar to how we have VCHI register platform devices for the services
> VCHI provides, shouldn't we have th
Hi Eric,
On Tue, 2019-06-04 at 17:18 -0700, Eric Anholt wrote:
> Nicolas Saenz Julienne writes:
>
> > Raspberry Pi's firmware offers and interface though which update it's
> > performance requirements. It allows us to request for specific runtime
> > frequencies, which the firmware might or migh
The patch changes the way how the 'ops' gets populated for different
device versions. The matching function now uses 'of_device_id' in order
to identify the device type.
Signed-off-by: Lukasz Luba
Signed-off-by: Chanwoo Choi
---
drivers/devfreq/event/exynos-ppmu.c | 38 +++--
This patch adds posibility to choose what type of data should be counted
by the PPMU counter. Now the type comes from DT where the event has been
defined. When there is no 'event-data-type' the default value is used,
which is 'read+write data in bytes'.
It is needed when you want to know not only r
Greetings,
I humbly solicit for your partnership to transfer €15 million Euros
into your personal or company’s account .Contact me for more detailed
explanation.
Kindly send me the followings
Full Names
Address
Occupation
Direct Mobile Telephone Lines
Nationality
Ahmed Zama
+22675844869
The patch adds new field in the PPMU event which shows explicitly
what kind of data the event is monitoring. It is possible to change it
using defined values in exynos_ppmu.h file.
Acked-by: Chanwoo Choi
Signed-off-by: Lukasz Luba
---
arch/arm/boot/dts/exynos4412-ppmu-common.dtsi | 10 +
Extend the documenation by events description with new 'event-data-type'
field. Add example how the event might be defined in DT.
Signed-off-by: Lukasz Luba
Signed-off-by: Chanwoo Choi
---
.../bindings/devfreq/event/exynos-ppmu.txt| 26 +--
1 file changed, 24 insertions(+),
This patch add support of a new feature which can be used in DT:
Performance Monitoring Unit with defined event data type.
In this patch the event data types are defined for Exynos PPMU.
The patch also updates the MAINTAINERS file accordingly and
adds the header file to devfreq event subsystem.
Ac
1 - 100 of 913 matches
Mail list logo