Re: [PATCH v2 0/3] serial: sh-sci: Add support for RZ/A2

On Thu, Jul 26, 2018 at 03:01:11PM +0200, Geert Uytterhoeven wrote: > Hi Chris, > > On Thu, Jul 26, 2018 at 2:25 PM Chris Brandt wrote: > > On Thursday, July 26, 2018, Geert Uytterhoeven wrote: > > > Thanks for your series! > > > > > > Unfortunately Greg has already applied your v1 (and my fix

Re: [PATCH -stable] pinctrl: sh-pfc: r8a77970: remove SH_PFC_PIN_CFG_DRIVE_STRENGTH flag

On Tue, Jul 17, 2018 at 05:24:17PM +0200, Niklas Söderlund wrote: > The datasheet does not document any registers to control drive strength, > and no drive strength registers are for this reason described for this > SoC. The flags indicating that drive strength can be controlled are > however set

Re: [PATCH] serial: sh-sci: prevent lockup on full TTY buffers

On Thu, Feb 15, 2018 at 01:02:27PM +0100, Ulrich Hecht wrote: > When the TTY buffers fill up to the configured maximum, a system lockup > occurs: > > [ 598.820128] INFO: rcu_preempt detected stalls on CPUs/tasks: > [ 598.825796] 0-...!: (1 GPs behind) idle=5a6/2/0 softirq=1974/1974 fqs=1 > [

Re: [PATCH 2/2] serial: sh-sci: Support for HSCIF RX sampling point adjustment

On Fri, Sep 29, 2017 at 03:08:54PM +0200, Ulrich Hecht wrote: > HSCIF has facilities that allow moving the RX sampling point by between > -8 and 7 sampling cycles (one sampling cycles equals 1/15 of a bit > by default) to improve the error margin in case of slightly mismatched > bit rates between

Re: [PATCH] usb: renesas_usbhs: fix usbhsf_fifo_clear() behavior

On Wed, Sep 27, 2017 at 05:04:05PM +0900, Yoshihiro Shimoda wrote: > This patch fixes two issues: > - the usbhsf_fifo_clear() is possible to cause 10 msec delay if >the pipe is RX direction and empty because the FRDY bit will never >be set to 1 in such case. > - sets the BCLR of

Re: [GIT PULL LTSI-4.9 v2 00/13] Second Round of Renesas SoCs and Drivers to v4.12

On Tue, Sep 05, 2017 at 10:06:35AM +0200, Simon Horman wrote: > Hi, > > This is a submission to LTSI-v4.9. > > * Backport v4.9 of the rcar-gen3-thermal driver to its as of v4.12. > * Limited backport to v4.9 of: > - usb core > - ohci-platform > - ehci-platform > - cs2000 > > There are

Re: [LTSI-dev] [GIT PULL LTSI-4.9] Second Round of Renesas SoCs and Drivers to v4.12

On Tue, Aug 29, 2017 at 09:08:53PM +0200, Simon Horman wrote: > Hi, > > This is a submission to LTSI-v4.9. > > This series is comprised of a backport v4.9 of the rcar-gen3-thermal driver > to its as of v4.12. This was unintentionally omitted from earlier work > submitted for inclusion in

Re: [LTSI-dev] [GIT PULL LTSI-4.9] Third Round of Renesas SoCs and Drivers to v4.12

On Thu, Aug 31, 2017 at 04:04:47PM +0200, Simon Horman wrote: > Hi, > > This is a submission to LTSI-v4.9. > > This series is comprised of a limited backport to v4.9 of usb core, > ohci-platform, ehci-platform and cs2000. > > These were have been suggested after examination and testing of >

Re: [PATCH 0/6] serdev multiplexing support

On Wed, Aug 16, 2017 at 03:22:22PM +0200, Ulrich Hecht wrote: > Hi! > > Here's a new version of serdev multiplexing support. Thanks to everybody who > commented; I think I have included all non-optional suggestions. :) > Changes are manifold, please refer to the changelog below. > > This version

Re: [LTSI-dev] [GIT PULL LTSI-4.9] Renesas SoCs and Drivers to v4.12

On Mon, Jul 10, 2017 at 03:33:34PM +0200, Simon Horman wrote: > Hi, > > This is a submission to LTSI-v4.9. > > This series is comprised of backports to v4.9 of the following > components to their standard as of v4.12: > > It is a follow up to early preparatory work the main difference being > a

Re: [LTSI-dev] [GIT PULL LTSI-4.9] Renesas SoCs and Drivers to v4.11

On Mon, Jul 10, 2017 at 03:30:50PM +0200, Simon Horman wrote: > Hi, > > This is a submission to LTSI-v4.9. > > This series is comprised of backports to v4.9 of the following > components to their standard as of v4.11: > > * adv7511 > * ak4642 > * clk > * cpg > * gen3 > * gpio-keys > * gpio-rcar

Re: [LTSI-dev] [GIT PULL LTSI-4.9 repost] Renesas SoCs and Drivers to v4.10

On Mon, Jul 10, 2017 at 03:26:58PM +0200, Simon Horman wrote: > [Reposting with correct tag to pull, an old revision was posted by mistake] > > Hi, > > This is a submission to LTSI-v4.9. > > This series is comprised of backports to v4.9 of the following > components to their standard as of

Re: [PATCHv5 1/4] Staging: ks7010: ks_wlan_ioctl.h: Removed mixed spaces/tabs

On Fri, Mar 17, 2017 at 03:22:57PM +0900, Greg KH wrote: > On Wed, Mar 15, 2017 at 08:18:08PM -0700, Matthew Giassa wrote: > > Removing mixed spaces/hard-tabs used to create a "column alignment" of > > macro names and macro values. > > > > Signed-off-b

Re: [PATCHv5 1/4] Staging: ks7010: ks_wlan_ioctl.h: Removed mixed spaces/tabs

On Wed, Mar 15, 2017 at 08:18:08PM -0700, Matthew Giassa wrote: > Removing mixed spaces/hard-tabs used to create a "column alignment" of > macro names and macro values. > > Signed-off-by: Matthew Giassa > --- > drivers/staging/ks7010/ks_wlan_ioctl.h | 4 ++-- > 1 file

Re: [PATCHv5 1/4] Staging: ks7010: ks_wlan_ioctl.h: Removed mixed spaces/tabs

On Tue, Mar 14, 2017 at 07:25:51PM -0700, Matthew Giassa wrote: > Removing mixed spaces/hard-tabs used to create a "column alignment" of > macro names and macro values. > > Signed-off-by: Matthew Giassa > --- > drivers/staging/ks7010/ks_wlan_ioctl.h | 4 ++-- > 1 file

Re: [PATCH 1/2] Formatting updates to remove checkpatch warnings in ks_wlan_ioctl.h.

On Sun, Mar 05, 2017 at 01:52:19PM -0800, Matthew Giassa wrote: > Implementing some minor formatting changes to remove checkpatch warnings. > Removing space-hardtab instances. Removing C++-style line comments in favor of > C-style equivalent. Re-aligning function prototype arguments to remove

Re: [PATCHv2] Checkpatch fixes for staging/drivers/ks7010.

On Wed, Feb 22, 2017 at 01:52:58PM -0800, Matthew Giassa wrote: > Wrapping complex macros with parentheses. > Adding extra spaces between macros and integer literals. > Indentation changes to remove checkpatch warnings. > Swapping out C++-style comments with C-style comments. > > Signed-off-by:

Re: [PATCH v2 4/7] serial: sh-sci: increase RX FIFO trigger defaults for (H)SCIF

On Mon, Jan 23, 2017 at 05:04:15PM +0100, Ulrich Hecht wrote: > Signed-off-by: Ulrich Hecht > --- > drivers/tty/serial/sh-sci.c | 13 - > 1 file changed, 12 insertions(+), 1 deletion(-) I will not take a patch without any changelog text, sorry...

Re: [PATCH 00/19] sh-sci: Platform data simplification

On Wed, Jan 11, 2017 at 01:06:04PM +0200, Laurent Pinchart wrote: > Hi Greg, > > On Wednesday 11 Jan 2017 11:43:30 Greg KH wrote: > > On Wed, Jan 11, 2017 at 11:38:15AM +0100, Geert Uytterhoeven wrote: > > > On Wed, Jan 11, 2017 at 9:04 AM, Greg KH <g...@kroah.com>

Re: [LTSI-dev] [GIT/RFC PULL LTSI-4.9] Renesas SoCs and Drivers to next-20161028

On Mon, Nov 14, 2016 at 10:03:44AM +0100, Simon Horman wrote: > Hi, > > ** This series is for informational purposes only! ** > > This series is comprised of backports to v4.9-rc3 of the following > components to their standard as of next-20161028: > > * gen3 (ARM64 SoC Integration) >

Re: [PATCH] [media] v4l: rcar-fcp: Don't force users to check for disabled FCP support

On Tue, Oct 18, 2016 at 04:24:20PM +0300, Laurent Pinchart wrote: > commit fd44aa9a254b18176ec3792a18e7de6977030ca8 upstream. > > The rcar_fcp_enable() function immediately returns successfully when the > FCP device pointer is NULL to avoid forcing the users to check the FCP > device manually

Re: [PATCH 00/27] staging: add driver for KS7010 based SDIO cards

On Wed, May 11, 2016 at 08:06:15AM +0200, Wolfram Sang wrote: > On Tue, May 10, 2016 at 11:05:34PM +0200, Greg KH wrote: > > On Tue, May 10, 2016 at 03:52:13PM +0200, Wolfram Sang wrote: > > > This driver can be used with later Spectec SDW-821 and all SDW-823 cards. > >

Re: [PATCH 00/27] staging: add driver for KS7010 based SDIO cards

On Tue, May 10, 2016 at 03:52:13PM +0200, Wolfram Sang wrote: > This driver can be used with later Spectec SDW-821 and all SDW-823 cards. > See patch 1 and README for more details about its origin. To have the card > working, you need another patch which is already in mmc/next: > >