07.09.2020 11:27, Andy Shevchenko пишет:
> On Sun, Sep 6, 2020 at 9:52 PM Dmitry Osipenko wrote:
>>
>> Reorder location of functions in the code in order to have definition
>> of functions closer to the place of the invocation. This change makes
>> easier to navigate around the code and removes
From: Yu Chen
There are some problems at the initialization part of this phy.
Solve them.
Signed-off-by: Yu Chen
Signed-off-by: Mauro Carvalho Chehab
---
drivers/phy/hisilicon/phy-hi3670-usb3.c | 70 +++--
1 file changed, 32 insertions(+), 38 deletions(-)
diff --git
The lcdif IP does not support a framebuffer pitch (stride) other than
the CRTC width. Check for equality and reject the state otherwise.
This prevents a distorted picture when using 640x800 and running the
Mesa graphics stack. Mesa tires to use a cache aligned stride, which
leads at that
From: Yu Chen
The HiKey960 has a fairly complex USB configuration due to it
needing to support a USB-C port for host/device mode and multiple
USB-A ports in host mode, all using a single USB controller.
See schematics here:
This binding driver is needed for Hikey 970 to work,
as otherwise a Serror is produced:
[1.837458] SError Interrupt on CPU0, code 0xbf02 -- SError
[1.837462] CPU: 0 PID: 74 Comm: kworker/0:1 Not tainted 5.8.0+ #205
[1.837463] Hardware name: HiKey970 (DT)
[
Use the new YAML for this physical layer.
Signed-off-by: Mauro Carvalho Chehab
---
.../bindings/phy/hisilicon,hi3670-usb3.yaml | 72 +++
.../bindings/phy/phy-hi3670-usb3.txt | 25 ---
2 files changed, 72 insertions(+), 25 deletions(-)
create mode 100644
Add the USB3 bindings for Kirin 970 phy and Hikey 970 board.
Signed-off-by: Mauro Carvalho Chehab
---
.../boot/dts/hisilicon/hi3670-hikey970.dts| 102 ++
arch/arm64/boot/dts/hisilicon/hi3670.dtsi | 58 ++
drivers/misc/hisi_hikey_usb.c | 29 ++---
On Fri, Aug 21, 2020 at 12:57:54PM -0700, kan.li...@linux.intel.com wrote:
> diff --git a/arch/x86/events/core.c b/arch/x86/events/core.c
> index 0f3d01562ded..fa08d810dcd2 100644
> --- a/arch/x86/events/core.c
> +++ b/arch/x86/events/core.c
> @@ -1440,7 +1440,10 @@ static void
Address the issues reported by checkpatch --strict,
and add a SPDX tag.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/phy/hisilicon/phy-hi3670-usb3.c | 157
1 file changed, 76 insertions(+), 81 deletions(-)
diff --git a/drivers/phy/hisilicon/phy-hi3670-usb3.c
From: Yu Chen
Add the Hisilicon Kirin 3670 USB phy driver just after the
hi3660, using the same namespace.
This driver was imported from Linaro's official Hikey 970
tree, from the original patch, removing the addition of
the dwg3-specific parts.
Signed-off-by: Yu Chen
Signed-off-by: Mauro
Rename hikey970 to hi3670, in order to use a namespace
similar to hi3660 driver.
Signed-off-by: Mauro Carvalho Chehab
---
.../bindings/phy/phy-hi3670-usb3.txt | 4 +-
drivers/phy/hisilicon/phy-hi3670-usb3.c | 98 +--
2 files changed, 51 insertions(+), 51
On Mon, Sep 07, 2020 at 04:24:00PM +1000, Herbert Xu wrote:
> On Sun, Sep 06, 2020 at 04:52:24PM +0800, kernel test robot wrote:
> >
> > >> drivers/crypto/allwinner/sun4i-ss/sun4i-ss-hash.c:483:35: sparse:
> > >> sparse: incorrect type in assignment (different base types) @@
> > >> expected
Now that this driver was added upsream, it needs a maintainer.
Signed-off-by: Mauro Carvalho Chehab
---
MAINTAINERS | 9 -
1 file changed, 8 insertions(+), 1 deletion(-)
diff --git a/MAINTAINERS b/MAINTAINERS
index 2f497c7d659c..267ba0b7a52e 100644
--- a/MAINTAINERS
+++ b/MAINTAINERS
Do some changes at the DT properties in order to make it
follow the phy-hi3660-usb3 example and to simplify
usb3-phy-tx-vboost-lvl name.
Signed-off-by: Mauro Carvalho Chehab
---
drivers/phy/hisilicon/phy-hi3670-usb3.c | 10 +-
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git
Add the PHY layer for Hikey 970 and a misc driver that it is
required for the USB hub to work. The same USB hub is needed
by Hikey 960.
That's the second version, addressing the points raised by
Mark on the RFC version and adding an extra patch in order for
it to use the dwc3-of-simple driver.
Hello,
syzbot found the following issue on:
HEAD commit:fc3abb53 Merge branch 'for-linus' of git://git.kernel.org/..
git tree: upstream
console output: https://syzkaller.appspot.com/x/log.txt?x=16ccc8ae90
kernel config: https://syzkaller.appspot.com/x/.config?x=3c5f6ce8d5b68299
The HiKey 970 board is similar to Hikey 960 with regards
to its USB configutation: it also relies on a USB HUB
that is used when DWC3 is at host mode.
However, it requires a few extra DT settings, as it
uses a voltage regulator and GPIO reset pin.
Add support for them.
Signed-off-by: Mauro
Hi Hugues,
Thank you for the review.
On Mon, Sep 7, 2020 at 10:44 AM Hugues FRUCHET wrote:
>
> Hi Prabhakar,
>
> Thanks for your patches, good to see one more OV5640 stakeholder
> upstreaming some fixes/features.
>
> I'm also using a parallel setup with OV5640 connected on STM32 DCMI
> camera
On Tue, Aug 11, 2020 at 09:29:24AM +0800, Anson Huang wrote:
> When devm_clk_get() returns -EPROBE_DEFER, i.MX6 PCI driver should
> NOT print error message, use dev_err_probe() to handle it.
>
> Signed-off-by: Anson Huang
> ---
> drivers/pci/controller/dwc/pci-imx6.c | 35
>
On Mon, Sep 7, 2020 at 4:02 PM Marek Szyprowski
wrote:
>
> Hi Tomasz,
>
> On 07.09.2020 15:07, Tomasz Figa wrote:
> > On Fri, Sep 4, 2020 at 3:35 PM Marek Szyprowski
> > wrote:
> >> Use recently introduced common wrappers operating directly on the struct
> >> sg_table objects and scatterlist
On Wed, Sep 02, 2020 at 04:35:33PM +0200, Takashi Iwai wrote:
> On Wed, 02 Sep 2020 13:01:03 +0200,
> Greg Kroah-Hartman wrote:
> >
> > snd_usb_pipe_sanity_check() is a great function, so let's move it into
> > the USB core so that other parts of the kernel, including the USB core,
> > can call
Em Mon, 07 Sep 2020 17:04:31 +0300
Felipe Balbi escreveu:
> Hi Mauro,
>
> Mauro Carvalho Chehab writes:
>
> > Hi Felipe/Greg,
> >
> > What's the status of this patch?
>
> to be frank, I don't think I have this in my inbox anymore.
>
> > I tested here, together with the Hikey 970 phy RFC
Hi All,
This patch series enables PCIe, SPI NOR flash, CAN0 and SD2 LED indication
on iWave G21D-Q7 board.
Patches apply on top of [1] and also dependent on patch [2]
[1] https://git.kernel.org/pub/scm/linux/kernel/git/geert/
renesas-devel.git/log/?h=renesas-arm-dt-for-v5.10
[2]
This patch enables CAN1 interface exposed through connector J20 on the
carrier board.
Signed-off-by: Lad Prabhakar
Reviewed-by: Chris Paterson
---
arch/arm/boot/dts/r8a7742-iwg21d-q7.dts | 21 +
1 file changed, 21 insertions(+)
diff --git
Add support for LED trigger on SD2 interface.
Signed-off-by: Lad Prabhakar
Reviewed-by: Chris Paterson
Reviewed-by: Geert Uytterhoeven
---
arch/arm/boot/dts/r8a7742-iwg21d-q7.dts | 10 ++
1 file changed, 10 insertions(+)
diff --git a/arch/arm/boot/dts/r8a7742-iwg21d-q7.dts
Add support for the SPI NOR device which is connected to MSIOF0 interface
on the iWave RainboW-G21d-q7 board.
Signed-off-by: Lad Prabhakar
Reviewed-by: Chris Paterson
Reviewed-by: Geert Uytterhoeven
---
arch/arm/boot/dts/r8a7742-iwg21d-q7.dts | 31 +
1 file changed, 31
Hi, Fabien:
Fabien Parent 於 2020年9月7日 週一 下午8:57寫道:
>
> Add binding documentation for topckgen, apmixedsys, infracfg, audsys,
> imgsys, mfgcfg, mmsys, vdecsys on MT8167 SoC.
Why don't you add compatible of "mediatek,mt8167-mmsys"?
Regards,
Chun-Kuang.
>
> Signed-off-by: Fabien Parent
> ---
>
The usb_control_msg_send() and usb_control_msg_recv() calls can return
an error if a "short" write/read happens, and they can handle data off
of the stack, so move the driver over to using those calls instead,
saving some logic when dynamically allocating memory.
Cc: Marcel Holtmann
Cc: Johan
On Mon, Aug 10, 2020 at 06:41:54PM +0100, Lad Prabhakar wrote:
> Hi All,
>
> This patch set adds PCIe instance to r8a7742 Soc dtsi.
> patches apply on-top of [1] + [2]
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/geert/
> renesas-devel.git/log/?h=renesas-arm-dt-for-v5.10
> [2]
The usb_control_msg_recv() function can handle data on the stack, as
well as properly detecting short reads, so move to use that function
instead of the older usb_control_msg() call. This ends up removing a
lot of extra lines in the driver.
Cc: Juergen Stuber
Cc:
A USB device will always haev a bi-directional endpoint 0, that's just
how the devices work, so no need to check for that in a few quirk tests
as it will always pass.
Cc: Jaroslav Kysela
Cc: Takashi Iwai
Cc: Alexander Tsoy
Cc: alsa-de...@alsa-project.org
Reported-by: Alan Stern
Signed-off-by:
The usb_control_msg_send() call can handle data on the stack, as well as
returning an error if a "short" write happens, so move the driver over
to using that call instead. This ends up removing a helper function
that is no longer needed.
Cc: Jaroslav Kysela
Cc: alsa-de...@alsa-project.org
On Mon, Sep 07, 2020 at 04:56:44PM +0200, Greg Kroah-Hartman wrote:
> On Mon, Sep 07, 2020 at 04:51:00PM +0200, Greg Kroah-Hartman wrote:
> > There are a few calls to usb_control_msg() that can be converted to use
> > usb_control_msg_send() instead, so do that in order to make the error
> >
There are a few calls to usb_control_msg() that can be converted to use
usb_control_msg_send() instead, so do that in order to make the error
checking a bit simpler and the code smaller.
Cc: Alan Stern
Signed-off-by: Greg Kroah-Hartman
---
v2:
- dropped changes to usb_req_set_sel() thanks to
On 9/7/20 4:20 AM, Jan Kiszka wrote:
> Hi all,
>
> Arsalan reported that the upstream driver for sp5100_tco does not work
> for embedded Ryzen. Meanwhile, I was able to confirm that on an R1505G:
>
> [ 11.607251] sp5100_tco: SP5100/SB800 TCO WatchDog Timer Driver
> [ 11.607337] sp5100-tco
The usb_control_msg_send() and usb_control_msg_recv() calls can return
an error if a "short" write/read happens, and they can handle data off
of the stack, so move the driver over to using those calls instead,
saving some logic when dynamically allocating memory.
Cc: Jaroslav Kysela
Cc: Vasily
From: Tom Rix
clang static analyzer reports this problem
sb_edac.c:959:2: warning: Undefined or garbage value
returned to caller
return type;
^~~
This is a false positive.
However by initializing the type to DEV_UNKNOWN the 3 case can be
removed from the switch,
On Mon, Sep 07, 2020 at 02:41:49PM +1200, Chris Packham wrote:
> Add pinctrl information for the 98dx3236 (and variants). There is only
> one choice for i2c0 MPP14 and MPP15.
>
> Signed-off-by: Chris Packham
Reviewed-by: Andrew Lunn
Andrew
The stack dumping code needs to work for both kernel and user mode,
and currently this works by using set_fs() and then calling get_user()
to carefully access a potentially invalid pointer.
Change both locations to handle user and kernel mode differently, using
get_kernel_nofault() in case of
On 07.09.20 17:31, Guenter Roeck wrote:
> On 9/7/20 4:20 AM, Jan Kiszka wrote:
>> Hi all,
>>
>> Arsalan reported that the upstream driver for sp5100_tco does not work
>> for embedded Ryzen. Meanwhile, I was able to confirm that on an R1505G:
>>
>> [ 11.607251] sp5100_tco: SP5100/SB800 TCO
On Mon, Sep 07, 2020 at 02:41:48PM +1200, Chris Packham wrote:
> The switches with integrated CPUs have only got a single i2c controller.
> The incorrectly gained one when they were split from the Armada-XP.
>
> Fixes: 43e28ba87708 ("ARM: dts: Use armada-370-xp as a base for
>
On Mon, Sep 07, 2020 at 02:41:47PM +1200, Chris Packham wrote:
> Per the datasheet the i2c functions use MPP_Sel=0x1. They are documented
> as using MPP_Sel=0x4 as well but mixing 0x1 and 0x4 is clearly wrong. On
> the board tested 0x4 resulted in a non-functioning i2c bus so stick with
> 0x1
On Mon 2020-09-07 12:36:45, John Ogness wrote:
> On 2020-09-07, Petr Mladek wrote:
> > This extra metadata are not currently read by crashdump tools.
>
> crash [0] prints dictionary data.
> [0] https://github.com/crash-utility/crash
Grr, I have missed this. It makes things more complicated.
We
> I would not say it is a "new feature". But rather that patch in this
> email fixes issue that Linux kernel did not set correct MAC address for
> DSA slave ports. I think it is something which could be backported also
> to stable releases as "ignoring" vendor/factory MAC address is not
> correct
The epoll_wait() system call wrapper is one of the remaining users of
the set_fs() infrasturcture for Arm. Changing it to not require set_fs()
is rather complex unfortunately.
The approach I'm taking here is to allow architectures to override
the code that copies the output to user space, and let
On Mon, 7 Sep 2020 15:40:46 +0200
Marco Elver wrote:
> From: Alexander Potapenko
>
> This adds the Kernel Electric-Fence (KFENCE) infrastructure. KFENCE is a
> low-overhead sampling-based memory safety error detector of heap
> use-after-free, invalid-free, and out-of-bounds access errors.
>
>
The epoll_wait() syscall has a special version for OABI compat
mode to convert the arguments to the EABI structure layout
of the kernel. However, the later epoll_pwait() syscall was
added in arch/arm in linux-2.6.32 without this conversion.
Use the same kind of handler for both.
Fixes:
Tested both original and (md->type == EFI_CONVENTIONAL_MEMORY)
versions - they fix qemu v7 boot under qemu. I think the second
version is more correct.
Regards,
Maxim.
On Mon, 7 Sep 2020 at 13:21, Maxim Uvarov wrote:
>
> On Mon, 7 Sep 2020 at 11:31, Heinrich Schuchardt wrote:
> >
> > On
This is one of the last users of get_fs(), and this is fairly easy to
change, since the infrastructure for it is already there.
The replacement here is essentially a copy of the existing fcntl64()
syscall entry function.
Signed-off-by: Arnd Bergmann
---
arch/arm/kernel/sys_oabi-compat.c | 93
These mimic the behavior of get_user and put_user, except
for domain switching, address limit checking and handling
of mismatched sizes, none of which are relevant here.
To work with pre-Armv6 kernels, this has to avoid TUSER()
inside of the new macros, the new approach passes the "t"
string
sys_oabi_semtimedop() is one of the last users of set_fs() on Arm. To
remove this one, expose the internal code of the actual implementation
that operates on a kernel pointer and call it directly after copying.
There should be no measurable impact on the normal execution of this
function, and it
[SNIP]
> >
> > > Would you be able to ftrace the interrupt handler function and see if you
> > > can see a difference in number or timing of interrupts? I'm at a bit of
> > > a loss.
> >
> > I tried ftrace but I really wasn't sure what I was looking for.
> > Capturing a "bad" case was pretty
The system call number is used in a a couple of places, in particular
ptrace, seccomp and /proc//syscall.
The last one apparently never worked reliably on ARM for tasks
that are not currently getting traced.
Storing the syscall number in the normal entry path makes it work,
as well as allowing
On Mon, Sep 7, 2020 at 3:38 PM tanhuazhong wrote:
>
>
>
> On 2020/9/7 17:22, Willem de Bruijn wrote:
> > On Sun, Sep 6, 2020 at 8:42 PM Jakub Kicinski wrote:
> >>
> >> On Sat, 5 Sep 2020 14:11:11 +0800 Huazhong Tan wrote:
> >>> There are two updates relates to UDP GSO.
> >>> #1 adds a new GSO
On machines such as ARMv5 that trap unaligned accesses, these
two functions can be slow when each access needs to be emulated,
or they might not work at all.
Change them so that each loop is only used when both the src
and dst pointers are naturally aligned.
Signed-off-by: Arnd Bergmann
---
On Mon, Sep 7, 2020 at 6:25 PM Dmitry Osipenko wrote:
> 07.09.2020 18:05, Andy Shevchenko пишет:
> > On Mon, Sep 7, 2020 at 5:32 PM Dmitry Osipenko wrote:
> >> 07.09.2020 11:10, Andy Shevchenko пишет:
...
> >> Would be great if anyone could put effort into changing the default
> >> get_sync()
(your mailer broke and forgot to keep lines shorter than 78 chars)
On Tue, Sep 01, 2020 at 12:46:41PM +0200, Frederic Weisbecker wrote:
> == TIF_NOHZ ==
>
> Need to get rid of that in order not to trigger syscall slowpath on
> CPUs that don't want nohz_full. Also we don't want to iterate all
Hello Linus,
On 8/28/20 12:55 AM, Linus Walleij wrote:
> Hi Ahmad,
>
> On Tue, Aug 4, 2020 at 11:18 AM Ahmad Fatoum wrote:
>
>> Generic GPIO consumers like gpio-keys use request_any_context_irq()
>> to request a threaded handler if irq_settings_is_nested_thread() ==
>> true or a hardirq
On Mon, Sep 7, 2020 at 3:41 PM Marco Elver wrote:
>
> Add KFENCE documentation in dev-tools/kfence.rst, and add to index.
>
> Co-developed-by: Alexander Potapenko
> Signed-off-by: Alexander Potapenko
> Signed-off-by: Marco Elver
> ---
> Documentation/dev-tools/index.rst | 1 +
>
The gpio-siox driver uses handle_nested_irq() to implement its
interrupt support. This is only capable of handling threaded irq
actions. For a hardirq action it triggers a NULL pointer oops.
(It calls action->thread_fn which is NULL then.)
Prevent registration of a hardirq action by setting
The usb_control_msg_send() and usb_control_msg_recv() calls can return
an error if a "short" write/read happens, so move the driver over to
using those calls instead, saving some logic in the wrapper functions
that were being used in this driver.
This also resolves a long-staging bug where data
New core functions to make sending/receiving USB control messages easier
and saner.
In discussions, it turns out that the large majority of users of
usb_control_msg() do so in potentially incorrect ways. The most common
issue is where a "short" message is received, yet never detected
properly
There are a few calls to usb_control_msg() that can be converted to use
usb_control_msg_send() instead, so do that in order to make the error
checking a bit simpler.
Cc: Alan Stern
Cc: "Rafael J. Wysocki"
Cc: Andy Shevchenko
Cc: linux-...@vger.kernel.org
Signed-off-by: Greg Kroah-Hartman
---
The usb_control_msg_send() call can return an error if a "short" write
happens, so move the driver over to using that call instead.
Cc: Jaroslav Kysela
Cc: alsa-de...@alsa-project.org
Reviewed-by: Takashi Iwai
Signed-off-by: Greg Kroah-Hartman
---
v2:
- Added reviewed-by from Takashi
On Fri, Sep 4, 2020 at 5:31 AM Sami Tolvanen wrote:
>
> This change adds build system support for Clang's Link Time
> Optimization (LTO). With -flto, instead of ELF object files, Clang
> produces LLVM bitcode, which is compiled into native code at link
> time, allowing the final binary to be
On Mon, Sep 07, 2020 at 01:27:17PM +0200, Pali Rohár wrote:
> Espressobin boards have 3 ethernet ports and some of them got assigned more
> then one MAC address. MAC addresses are stored in U-Boot environment.
>
> Since commit a2c7023f7075c ("net: dsa: read mac address from DT for slave
>
On Mon, Sep 7, 2020 at 4:08 PM Andy Shevchenko
wrote:
>
> On Mon, Sep 07, 2020 at 03:49:23PM +0200, Bartosz Golaszewski wrote:
> > On Mon, Sep 7, 2020 at 2:22 PM Greg Kroah-Hartman
> > wrote:
> > > On Mon, Sep 07, 2020 at 02:06:15PM +0200, Bartosz Golaszewski wrote:
>
> ...
>
> > > Yes it is.
(cc'ing in Eric Auger)
* Steven Price (steven.pr...@arm.com) wrote:
> Arm's Memory Tagging Extension (MTE) adds 4 bits of tag data to every 16
> bytes of memory in the system. This along with stashing a tag within the
> high bit of virtual addresses allows runtime checking of memory
> accesses.
>
On Mon, Sep 07, 2020 at 04:51:01PM +0200, Greg Kroah-Hartman wrote:
> There are a few calls to usb_control_msg() that can be converted to use
> usb_control_msg_send() instead, so do that in order to make the error
> checking a bit simpler and the code smaller.
>
> Cc: Alan Stern
> Signed-off-by:
On Fri, Sep 4, 2020 at 18:11 Oded Gabbay wrote:
> There is a case where the user reaches the maximum number of CS in-flight.
> In that case, the driver rejects the new CS of the user with EAGAIN. Count
> that event so the user can query the driver later to see if it happened.
>
> Signed-off-by:
07.09.2020 18:05, Andy Shevchenko пишет:
> On Mon, Sep 7, 2020 at 5:32 PM Dmitry Osipenko wrote:
>> 07.09.2020 11:10, Andy Shevchenko пишет:
>>> On Sun, Sep 6, 2020 at 9:51 PM Dmitry Osipenko wrote:
The runtime PM is guaranteed to be always available on Tegra after commit
On Fri, Sep 4, 2020 at 5:31 AM Sami Tolvanen wrote:
>
> LLD always splits sections with LTO, which increases module sizes. This
> change adds a linker script that merges the split sections in the final
> module.
>
> Suggested-by: Nick Desaulniers
> Signed-off-by: Sami Tolvanen
> ---
> Makefile
Pipe only looks at O_NONBLOCK for non-blocking operation, which means that
io_uring can't easily poll for it or attempt non-blocking issues. Check for
IOCB_NOWAIT in locking the pipe for reads and writes, and ditto when we
decide on whether or not to block or return -EAGAIN.
Signed-off-by: Jens
Hi Geert,
On Mon, Sep 7, 2020 at 8:55 AM Geert Uytterhoeven wrote:
>
> Hi Prabhakar,
>
> On Fri, Sep 4, 2020 at 7:15 PM Lad, Prabhakar
> wrote:
> > On Thu, Sep 3, 2020 at 1:20 PM Geert Uytterhoeven
> > wrote:
> > > On Tue, Aug 25, 2020 at 6:28 PM Lad Prabhakar
> > > wrote:
> > > > Add
Hi Andy,
On Mon, Sep 7, 2020 at 4:14 PM Andy Shevchenko
wrote:
> On Mon, Sep 07, 2020 at 03:49:23PM +0200, Bartosz Golaszewski wrote:
> > On Mon, Sep 7, 2020 at 2:22 PM Greg Kroah-Hartman
> > wrote:
> > > On Mon, Sep 07, 2020 at 02:06:15PM +0200, Bartosz Golaszewski wrote:
>
> ...
>
> > > Yes
This patch implements the basic functions of the BMC chip for some Intel
FPGA PCIe Acceleration Cards (PAC). The BMC is implemented using the
Intel MAX 10 CPLD.
This BMC chip is connected to the FPGA by a SPI bus. To provide direct
register access from the FPGA, the "SPI slave to Avalon Master
On Fri, Sep 4, 2020 at 21:46 Oded Gabbay wrote:
> For consistency with GAUDI code, add check of the relevant flag in the
> device structure before resetting the GOYA device in case of firmware
> event.
>
> Signed-off-by: Oded Gabbay
This patch-set is:
Reviewed-by: Tomer Tayar
Hi Geliang,
On 07/09/2020 12:29, Geliang Tang wrote:
This patch set the init remote_id to zero, otherwise it will be a random
number.
Then it added the missing subflow's remote_id setting code both in
__mptcp_subflow_connect and in subflow_ulp_clone.
Thank you for this other patch!
Here as
On Mon, Sep 7, 2020 at 5:32 PM Dmitry Osipenko wrote:
> 07.09.2020 11:10, Andy Shevchenko пишет:
> > On Sun, Sep 6, 2020 at 9:51 PM Dmitry Osipenko wrote:
> >>
> >> The runtime PM is guaranteed to be always available on Tegra after commit
> >> 40b2bb1b132a ("ARM: tegra: enforce PM requirement").
Hi Geliang,
On 07/09/2020 12:29, Geliang Tang wrote:
In mptcp_pm_nl_get_local_id, skc_local is the same as msk_local, so it
always return 0. Thus every subflow's local_id is 0. It's incorrect.
This patch fixed this issue.
Also, we need to ignore the zero address here, like 0.0.0.0 in IPv4.
On Tue, Jun 23, 2020 at 09:48:51AM +0200, Flavio Suligoi wrote:
> This comment still refers to the old driver pathname,
> when all PCI drivers were located directly under the
> drivers/pci directory.
>
> Anyway the function name itself is enough, so we can
> remove the overabundant path
On Fri, Sep 04, 2020 at 01:39:06PM +0200, Joerg Roedel wrote:
> From: Joerg Roedel
>
> Fix the following warning the the SUN50I driver:
>
>drivers/iommu/sun50i-iommu.c: In function 'sun50i_iommu_irq':
>drivers/iommu/sun50i-iommu.c:890:14: warning: variable 'iova' set but not
> used
On 07/09/2020 17:08, Greg KH wrote:
On Mon, Sep 07, 2020 at 04:35:23PM +0300, Paraschiv, Andra-Irina wrote:
On 07/09/2020 12:00, Greg KH wrote:
On Fri, Sep 04, 2020 at 08:37:15PM +0300, Andra Paraschiv wrote:
Signed-off-by: Andra Paraschiv
Reviewed-by: Alexander Graf
---
Changelog
v7
On Mon, Sep 07, 2020 at 03:27:16PM +0200, Pali Rohár wrote:
> CONFIG_ARM_ARMADA_37XX_CPUFREQ is tristate option and therefore this
> cpufreq driver can be compiled as a module. This patch adds missing
> MODULE_DEVICE_TABLE which generates correct modalias for automatic
> loading of this cpufreq
On 07/09/2020 17:08, Greg KH wrote:
On Mon, Sep 07, 2020 at 04:43:11PM +0300, Paraschiv, Andra-Irina wrote:
On 07/09/2020 12:01, Greg KH wrote:
On Fri, Sep 04, 2020 at 08:37:17PM +0300, Andra Paraschiv wrote:
Signed-off-by: Andra Paraschiv
Reviewed-by: Alexander Graf
---
Changelog
v7 ->
Current implementation of the genpd support over TI SCI uses a single
genpd across the whole SoC, and attaches multiple devices to this. This
solution has its drawbacks, like it is currently impossible to attach
more than one power domain to a device; the core genpd implementation
requires one
Hi Tero/Nishanth,
This series adds USB2.0 support for the J7200 EVM.
Series is based on top of:
Faiz's MMC/SD support series
https://lore.kernel.org/lkml/20200907090520.25313-1-faiz_ab...@ti.com/
Lokesh's initial support series
https://patchwork.kernel.org/cover/11740039/
The USB controller can be connected to one of the 2 lanes
of SERDES0 using a MUX. Add a MUX controller node for that.
Signed-off-by: Roger Quadros
---
arch/arm64/boot/dts/ti/k3-j7200-main.dtsi | 6 ++
1 file changed, 6 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-j7200-main.dtsi
The SERDES lane control mux registers are present in the
CTRLMMR space.
Signed-off-by: Roger Quadros
---
arch/arm64/boot/dts/ti/k3-j7200-main.dtsi | 15 +++
1 file changed, 15 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-j7200-main.dtsi
Each SERDES lane mux can select upto 4 different IPs.
There are 4 lanes in each J7200 SERDES. Define all
the possible functions in this file.
Signed-off-by: Roger Quadros
---
include/dt-bindings/mux/mux-j7200-wiz.h | 29 +
1 file changed, 29 insertions(+)
create mode
On Mon, Sep 07, 2020 at 01:50:10AM +, Hamish Martin wrote:
> Hi Alan,
>
> Thanks for your quick feedback. My replies are inline below.
>
> On Fri, 2020-09-04 at 11:45 -0400, Alan Stern wrote:
> > On Fri, Sep 04, 2020 at 03:22:46PM +1200, Hamish Martin wrote:
> > > Some integrated OHCI
On Mon, Sep 7, 2020 at 8:03 AM Christoph Hellwig wrote:
>
> On Mon, Sep 07, 2020 at 12:14:59AM +0200, Arnd Bergmann wrote:
> > I've had a first pass at this now, see
> >
> > https://git.kernel.org/pub/scm/linux/kernel/git/arnd/playground.git/log/?h=arm-kill-set_fs
> >
> > There are a couple of
On Mon, Sep 07, 2020 at 04:51:00PM +0200, Greg Kroah-Hartman wrote:
> There are a few calls to usb_control_msg() that can be converted to use
> usb_control_msg_send() instead, so do that in order to make the error
> checking a bit simpler.
>
> Cc: Alan Stern
> Cc: "Rafael J. Wysocki"
> Cc: Andy
Hi Eric,
On 9/3/2020 5:06 PM, Auger Eric wrote:
Hi Diana,
On 8/26/20 11:33 AM, Diana Craciun wrote:
The DPRC (Data Path Resource Container) device is a bus device and has
child devices attached to it. When the vfio-fsl-mc driver is probed
the DPRC is scanned and the child devices discovered
Miquel Raynal wrote on Mon, 7 Sep 2020
15:20:25 +0200:
> Hi Murugan,
>
> A few more comments below, but I guess the driver looks better now.
>
> > +struct ebu_nand_controller {
> > + struct nand_controller controller;
> > + struct nand_chip chip;
> > + struct device *dev;
> > + void
On Mon, Sep 07, 2020 at 04:24:00PM +1000, Herbert Xu wrote:
> On Sun, Sep 06, 2020 at 04:52:24PM +0800, kernel test robot wrote:
> >
> > >> drivers/crypto/allwinner/sun4i-ss/sun4i-ss-hash.c:483:35: sparse:
> > >> sparse: incorrect type in assignment (different base types) @@
> > >> expected
On 8/4/20 3:59 PM, Frankie Chang wrote:
> +void probe_binder_txn_latency_free(void *ignore, struct binder_transaction
> *t,
> + int from_proc, int from_thread,
> + int to_proc, int to_thread)
> +{
> + struct rtc_time tm;
Add vin[1,2] data8 and vin1_clk_b pins used by iwg21d-q7-dbcm-ca board
which is based on R8A7742 SoC.
Signed-off-by: Lad Prabhakar
Reviewed-by: Biju Das
---
drivers/pinctrl/sh-pfc/pfc-r8a7790.c | 38 +++-
1 file changed, 37 insertions(+), 1 deletion(-)
diff --git
j7200 has on USB controller instance. Add that.
Signed-off-by: Roger Quadros
---
arch/arm64/boot/dts/ti/k3-j7200-main.dtsi | 30 +++
1 file changed, 30 insertions(+)
diff --git a/arch/arm64/boot/dts/ti/k3-j7200-main.dtsi
b/arch/arm64/boot/dts/ti/k3-j7200-main.dtsi
index
From: Kishon Vijay Abraham I
First two lanes of SERDES is connected to PCIe, third lane is
connected to QSGMII and the last lane is connected to USB. However,
Cadence torrent SERDES doesn't support more than 2 protocols
at the same time. Configure it only for PCIe and QSGMII.
Signed-off-by:
801 - 900 of 1482 matches
Mail list logo