Re: [PATCH 3/3] pinctrl: sx150x: add a static gpio/pinctrl pin range mapping

2018-01-17 Thread Linus Walleij
On Wed, Jan 17, 2018 at 2:34 PM, Peter Rosin wrote: > Without such a range, gpiolib fails with -EPROBE_DEFER, pending the > addition of the range. So, without a range, gpiolib will keep > deferring indefinitely. > > Fixes: e10f72bf4b3e ("gpio: gpiolib: Generalise state

Re: [PATCH 3/3] pinctrl: sx150x: add a static gpio/pinctrl pin range mapping

2018-01-17 Thread Linus Walleij
On Wed, Jan 17, 2018 at 2:34 PM, Peter Rosin wrote: > Without such a range, gpiolib fails with -EPROBE_DEFER, pending the > addition of the range. So, without a range, gpiolib will keep > deferring indefinitely. > > Fixes: e10f72bf4b3e ("gpio: gpiolib: Generalise state persistence beyond >

Re: [RFC PATCH 1/2] pinctrl: add consumer variant for gpio request

2018-01-17 Thread Ludovic Desroches
On Wed, Jan 17, 2018 at 06:07:02PM +0200, Andy Shevchenko wrote: > On Wed, Jan 17, 2018 at 4:54 PM, Ludovic Desroches > wrote: > > On Tue, Jan 16, 2018 at 04:33:29PM +0200, Andy Shevchenko wrote: > > >> First of all, the main architectural issue with current pin

Re: [RFC PATCH 1/2] pinctrl: add consumer variant for gpio request

2018-01-17 Thread Ludovic Desroches
On Wed, Jan 17, 2018 at 06:07:02PM +0200, Andy Shevchenko wrote: > On Wed, Jan 17, 2018 at 4:54 PM, Ludovic Desroches > wrote: > > On Tue, Jan 16, 2018 at 04:33:29PM +0200, Andy Shevchenko wrote: > > >> First of all, the main architectural issue with current pin control > >> design is so called

Re: [PATCH v5 11/44] clk: davinci: Add platform information for TI DA830 PSC

2018-01-17 Thread Sekhar Nori
On Wednesday 17 January 2018 11:02 PM, David Lechner wrote: > +    clk_register_clkdev(clk_data->clks[3], "gpio", NULL); This is pretty bad (and no fault of yours) - having a con_id but no device name. Can you please make a pre-series which passes NULL con_id in

Re: [PATCH v5 11/44] clk: davinci: Add platform information for TI DA830 PSC

2018-01-17 Thread Sekhar Nori
On Wednesday 17 January 2018 11:02 PM, David Lechner wrote: > +    clk_register_clkdev(clk_data->clks[3], "gpio", NULL); This is pretty bad (and no fault of yours) - having a con_id but no device name. Can you please make a pre-series which passes NULL con_id in

Re: [PATCH v3 08/13] drm/sun4i: Add a driver for the display frontend

2018-01-17 Thread Chen-Yu Tsai
On Thu, Jan 18, 2018 at 3:22 PM, Maxime Ripard wrote: > Hi, > > On Wed, Jan 17, 2018 at 09:43:31PM +0800, Chen-Yu Tsai wrote: >> > if (sun4i_drv_node_is_connector(node)) >> > return 0; >> > >> > - if

Re: [PATCH v3 08/13] drm/sun4i: Add a driver for the display frontend

2018-01-17 Thread Chen-Yu Tsai
On Thu, Jan 18, 2018 at 3:22 PM, Maxime Ripard wrote: > Hi, > > On Wed, Jan 17, 2018 at 09:43:31PM +0800, Chen-Yu Tsai wrote: >> > if (sun4i_drv_node_is_connector(node)) >> > return 0; >> > >> > - if (!sun4i_drv_node_is_frontend(node)) { >> > + /* >> > +

Re: [PATCH 1/3] pinctrl: sx150x: unregister the pinctrl on release

2018-01-17 Thread Linus Walleij
On Wed, Jan 17, 2018 at 2:34 PM, Peter Rosin wrote: > There is no matching call to pinctrl_unregister, so switch to the > managed devm_pinctrl_register to clean up properly when done. > > Fixes: 9e80f9064e73 ("pinctrl: Add SX150X GPIO Extender Pinctrl Driver") > Signed-off-by:

Re: [PATCH 1/3] pinctrl: sx150x: unregister the pinctrl on release

2018-01-17 Thread Linus Walleij
On Wed, Jan 17, 2018 at 2:34 PM, Peter Rosin wrote: > There is no matching call to pinctrl_unregister, so switch to the > managed devm_pinctrl_register to clean up properly when done. > > Fixes: 9e80f9064e73 ("pinctrl: Add SX150X GPIO Extender Pinctrl Driver") > Signed-off-by: Peter Rosin

[GIT PULL] GPIO fix for v4.15

2018-01-17 Thread Linus Walleij
Hi Linus, this is the (hopefully) last GPIO fix for v4.15. Again the especially endowed screwer-upper who has been open coding bit fiddling is yours truly. Please pull it in! Yours, Linus Walleij The following changes since commit a8750ddca918032d6349adbf9a4b6555e7db20da: Linux 4.15-rc8

[GIT PULL] GPIO fix for v4.15

2018-01-17 Thread Linus Walleij
Hi Linus, this is the (hopefully) last GPIO fix for v4.15. Again the especially endowed screwer-upper who has been open coding bit fiddling is yours truly. Please pull it in! Yours, Linus Walleij The following changes since commit a8750ddca918032d6349adbf9a4b6555e7db20da: Linux 4.15-rc8

Re: [RFC PATCH] e1000e: Remove Other from EIAC.

2018-01-17 Thread Benjamin Poirier
On 2018/01/18 15:50, Benjamin Poirier wrote: > It was reported that emulated e1000e devices in vmware esxi 6.5 Build > 7526125 do not link up after commit 4aea7a5c5e94 ("e1000e: Avoid receiver > overrun interrupt bursts", v4.15-rc1). Some tracing shows that after > e1000e_trigger_lsc() is called,

Re: [RFC PATCH] e1000e: Remove Other from EIAC.

2018-01-17 Thread Benjamin Poirier
On 2018/01/18 15:50, Benjamin Poirier wrote: > It was reported that emulated e1000e devices in vmware esxi 6.5 Build > 7526125 do not link up after commit 4aea7a5c5e94 ("e1000e: Avoid receiver > overrun interrupt bursts", v4.15-rc1). Some tracing shows that after > e1000e_trigger_lsc() is called,

Re: [RFC PATCH] e1000e: Remove Other from EIAC.

2018-01-17 Thread Benjamin Poirier
On 2018/01/18 15:50, Benjamin Poirier wrote: > It was reported that emulated e1000e devices in vmware esxi 6.5 Build > 7526125 do not link up after commit 4aea7a5c5e94 ("e1000e: Avoid receiver > overrun interrupt bursts", v4.15-rc1). Some tracing shows that after > e1000e_trigger_lsc() is called,

Re: [RFC PATCH] e1000e: Remove Other from EIAC.

2018-01-17 Thread Benjamin Poirier
On 2018/01/18 15:50, Benjamin Poirier wrote: > It was reported that emulated e1000e devices in vmware esxi 6.5 Build > 7526125 do not link up after commit 4aea7a5c5e94 ("e1000e: Avoid receiver > overrun interrupt bursts", v4.15-rc1). Some tracing shows that after > e1000e_trigger_lsc() is called,

Re: AIO operation and CMSG

2018-01-17 Thread Stephan Mueller
Am Mittwoch, 17. Januar 2018, 20:22:13 CET schrieb Christoph Hellwig: Hi Christoph, > On Sun, Jan 14, 2018 at 09:01:00AM +0100, Stephan Müller wrote: > > The syscall io_submit sends data to the kernel and invokes the respective > > handler function in the kernel such as the recvmsg handler. What

Re: AIO operation and CMSG

2018-01-17 Thread Stephan Mueller
Am Mittwoch, 17. Januar 2018, 20:22:13 CET schrieb Christoph Hellwig: Hi Christoph, > On Sun, Jan 14, 2018 at 09:01:00AM +0100, Stephan Müller wrote: > > The syscall io_submit sends data to the kernel and invokes the respective > > handler function in the kernel such as the recvmsg handler. What

Re: [PATCH v4 4/8] PCI: brcmstb: Add dma-range mapping for inbound traffic

2018-01-17 Thread Christoph Hellwig
On Wed, Jan 17, 2018 at 08:15:33PM -0600, Rob Herring wrote: > > (a) overriding/redefining the dma_to_phys() and phys_to_dma() calls > > that are used by the dma_ops routines. This is the approach of > > > > arch/mips/cavium-octeon/dma-octeon.c > > MIPS is rarely an example to follow. :)

Re: [PATCH v4 4/8] PCI: brcmstb: Add dma-range mapping for inbound traffic

2018-01-17 Thread Christoph Hellwig
On Wed, Jan 17, 2018 at 08:15:33PM -0600, Rob Herring wrote: > > (a) overriding/redefining the dma_to_phys() and phys_to_dma() calls > > that are used by the dma_ops routines. This is the approach of > > > > arch/mips/cavium-octeon/dma-octeon.c > > MIPS is rarely an example to follow. :)

Re: [PATCH V4 1/2] nvme: add NVME_CTRL_RESET_PREPARE state

2018-01-17 Thread jianchao.wang
Hi James Thanks for you detailed, kindly response and directive. That's really appreciated. On 01/18/2018 02:24 PM, James Smart wrote: >> So in the patch, RESETTING in nvme-fc/rdma is changed to RESET_PREPARE. Then >> we get: >> nvme-fc/rdma RESET_PREPARE -> RECONNECTING -> LIVE >> nvme-pci

Re: [PATCH V4 1/2] nvme: add NVME_CTRL_RESET_PREPARE state

2018-01-17 Thread jianchao.wang
Hi James Thanks for you detailed, kindly response and directive. That's really appreciated. On 01/18/2018 02:24 PM, James Smart wrote: >> So in the patch, RESETTING in nvme-fc/rdma is changed to RESET_PREPARE. Then >> we get: >> nvme-fc/rdma RESET_PREPARE -> RECONNECTING -> LIVE >> nvme-pci

Re: [PATCH v1 1/1] usb: xhci: do not create and register shared_hcd when USB3.0 is disabled

2018-01-17 Thread Tung Vuong Nguyen
On Tue, Jan 16, 2018 at 9:50 PM, Mathias Nyman wrote: > > Hi, Sorry about the delay > > > On 04.01.2018 07:17, Thang Q. Nguyen wrote: >> >> Hi, >> >> On Sat, Dec 16, 2017 at 10:45 AM, Thang Q. Nguyen wrote: >>> >>> From: Tung Nguyen

Re: [PATCH v1 1/1] usb: xhci: do not create and register shared_hcd when USB3.0 is disabled

2018-01-17 Thread Tung Vuong Nguyen
On Tue, Jan 16, 2018 at 9:50 PM, Mathias Nyman wrote: > > Hi, Sorry about the delay > > > On 04.01.2018 07:17, Thang Q. Nguyen wrote: >> >> Hi, >> >> On Sat, Dec 16, 2017 at 10:45 AM, Thang Q. Nguyen wrote: >>> >>> From: Tung Nguyen >>> >>> Currently, hcd->shared_hcd always creates and

Re: [PATCH v3 09/13] drm/sun4i: backend: Wire in the frontend

2018-01-17 Thread Maxime Ripard
Hi, On Wed, Jan 17, 2018 at 09:46:13PM +0800, Chen-Yu Tsai wrote: > > + for_each_available_child_of_node(port, ep) { > > + remote = of_graph_get_remote_port_parent(ep); > > + if (!remote) > > + continue; > > + > > + /* does

Re: [PATCH v3 09/13] drm/sun4i: backend: Wire in the frontend

2018-01-17 Thread Maxime Ripard
Hi, On Wed, Jan 17, 2018 at 09:46:13PM +0800, Chen-Yu Tsai wrote: > > + for_each_available_child_of_node(port, ep) { > > + remote = of_graph_get_remote_port_parent(ep); > > + if (!remote) > > + continue; > > + > > + /* does

Re: [PATCH v3 08/13] drm/sun4i: Add a driver for the display frontend

2018-01-17 Thread Maxime Ripard
Hi, On Wed, Jan 17, 2018 at 09:43:31PM +0800, Chen-Yu Tsai wrote: > > if (sun4i_drv_node_is_connector(node)) > > return 0; > > > > - if (!sun4i_drv_node_is_frontend(node)) { > > + /* > > +* If the device is either just a regular device, or an > > +

Re: [PATCH v3 08/13] drm/sun4i: Add a driver for the display frontend

2018-01-17 Thread Maxime Ripard
Hi, On Wed, Jan 17, 2018 at 09:43:31PM +0800, Chen-Yu Tsai wrote: > > if (sun4i_drv_node_is_connector(node)) > > return 0; > > > > - if (!sun4i_drv_node_is_frontend(node)) { > > + /* > > +* If the device is either just a regular device, or an > > +

linux-next: Tree for Jan 18

2018-01-17 Thread Stephen Rothwell
Hi all, Changes since 20180117: The powerpc tree gained a conflict against the powerpc-fixes tree. The f2fs tree gained a build failure due to an interaction with the btrfs tree for which I reverted a commit. The net-next tree gained a conflict against the net tree. Non-merge commits

linux-next: Tree for Jan 18

2018-01-17 Thread Stephen Rothwell
Hi all, Changes since 20180117: The powerpc tree gained a conflict against the powerpc-fixes tree. The f2fs tree gained a build failure due to an interaction with the btrfs tree for which I reverted a commit. The net-next tree gained a conflict against the net tree. Non-merge commits

Re: [Letux-kernel] [PATCH v5 3/5] misc serdev: Add w2sg0004 (gps receiver) power control driver

2018-01-17 Thread Johan Hovold
On Fri, Jan 12, 2018 at 07:40:35PM +0100, Andreas Kemnade wrote: > On Fri, 12 Jan 2018 15:46:47 +0100 > Johan Hovold wrote: > > > On Tue, Jan 09, 2018 at 06:43:47PM +0100, Andreas Kemnade wrote: > > > On Fri, 22 Dec 2017 13:44:27 +0100 > > > Johan Hovold

Re: [Letux-kernel] [PATCH v5 3/5] misc serdev: Add w2sg0004 (gps receiver) power control driver

2018-01-17 Thread Johan Hovold
On Fri, Jan 12, 2018 at 07:40:35PM +0100, Andreas Kemnade wrote: > On Fri, 12 Jan 2018 15:46:47 +0100 > Johan Hovold wrote: > > > On Tue, Jan 09, 2018 at 06:43:47PM +0100, Andreas Kemnade wrote: > > > On Fri, 22 Dec 2017 13:44:27 +0100 > > > Johan Hovold wrote: > > > > > > [...] > > > > I'd

[RFC PATCH] e1000e: Remove Other from EIAC.

2018-01-17 Thread Benjamin Poirier
It was reported that emulated e1000e devices in vmware esxi 6.5 Build 7526125 do not link up after commit 4aea7a5c5e94 ("e1000e: Avoid receiver overrun interrupt bursts", v4.15-rc1). Some tracing shows that after e1000e_trigger_lsc() is called, ICR reads out as 0x0 in e1000_msix_other() on

[RFC PATCH] e1000e: Remove Other from EIAC.

2018-01-17 Thread Benjamin Poirier
It was reported that emulated e1000e devices in vmware esxi 6.5 Build 7526125 do not link up after commit 4aea7a5c5e94 ("e1000e: Avoid receiver overrun interrupt bursts", v4.15-rc1). Some tracing shows that after e1000e_trigger_lsc() is called, ICR reads out as 0x0 in e1000_msix_other() on

Re: [PATCH] cfg80211: stop demanding lots of new stuff

2018-01-17 Thread Johannes Berg
On Wed, 2018-01-17 at 14:55 -0800, Hugh Dickins wrote: > "make oldconfig" from 4.14 (when CONFIG_CFG80211_CERTIFICATION_ONUS > is not set) to 4.15-rc, gets into asking lots of new questions, and > configuring in unwanted stuff: I'm unsure of my Kconfig skills, but > it looks like

Re: [PATCH] cfg80211: stop demanding lots of new stuff

2018-01-17 Thread Johannes Berg
On Wed, 2018-01-17 at 14:55 -0800, Hugh Dickins wrote: > "make oldconfig" from 4.14 (when CONFIG_CFG80211_CERTIFICATION_ONUS > is not set) to 4.15-rc, gets into asking lots of new questions, and > configuring in unwanted stuff: I'm unsure of my Kconfig skills, but > it looks like

[PATCH net-next 5/5] net: hns3: add net status led support for fiber port

2018-01-17 Thread Peng Li
From: Jian Shen Check the net status per second, include port speed, total rx/tx packets and link status. Updating the led status for fiber port. Signed-off-by: Jian Shen Signed-off-by: Peng Li ---

[PATCH net-next 0/5] add some features to hns3 driver

2018-01-17 Thread Peng Li
This patchset adds some features to hns3 driver, include the support for ethtool command -d, -p and support for manager table. [Patch 1/5] adds support for ethtool command -d, its ops is get_regs. driver will send command to command queue, and get regs number and regs value from command queue.

[PATCH net-next 5/5] net: hns3: add net status led support for fiber port

2018-01-17 Thread Peng Li
From: Jian Shen Check the net status per second, include port speed, total rx/tx packets and link status. Updating the led status for fiber port. Signed-off-by: Jian Shen Signed-off-by: Peng Li --- .../net/ethernet/hisilicon/hns3/hns3pf/hclge_cmd.h | 1 +

[PATCH net-next 0/5] add some features to hns3 driver

2018-01-17 Thread Peng Li
This patchset adds some features to hns3 driver, include the support for ethtool command -d, -p and support for manager table. [Patch 1/5] adds support for ethtool command -d, its ops is get_regs. driver will send command to command queue, and get regs number and regs value from command queue.

[PATCH net-next 1/5] net: hns3: add support for get_regs

2018-01-17 Thread Peng Li
From: Fuyun Liang This patch adds get_regs support for ethtool cmd. Signed-off-by: Fuyun Liang Signed-off-by: Peng Li --- drivers/net/ethernet/hisilicon/hns3/hnae3.h| 3 +-

[PATCH net-next 1/5] net: hns3: add support for get_regs

2018-01-17 Thread Peng Li
From: Fuyun Liang This patch adds get_regs support for ethtool cmd. Signed-off-by: Fuyun Liang Signed-off-by: Peng Li --- drivers/net/ethernet/hisilicon/hns3/hnae3.h| 3 +- drivers/net/ethernet/hisilicon/hns3/hns3_ethtool.c | 23 +++

[PATCH net-next 2/5] net: hns3: add manager table initialization for hardware

2018-01-17 Thread Peng Li
From: Fuyun Liang The manager table is empty by default. If it is not initialized, the management pkgs like LLDP will be dropped by hardware. Default entries need to be added to manager table. Signed-off-by: Fuyun Liang Signed-off-by: Peng Li

[PATCH net-next 2/5] net: hns3: add manager table initialization for hardware

2018-01-17 Thread Peng Li
From: Fuyun Liang The manager table is empty by default. If it is not initialized, the management pkgs like LLDP will be dropped by hardware. Default entries need to be added to manager table. Signed-off-by: Fuyun Liang Signed-off-by: Peng Li ---

[PATCH net-next 3/5] net: hns3: add ethtool -p support for phy device

2018-01-17 Thread Peng Li
From: Jian Shen Add led location support for phy device. The led will keep blinking with frequency 2HZ when locating. Signed-off-by: Jian Shen Signed-off-by: Peng Li --- drivers/net/ethernet/hisilicon/hns3/hnae3.h|

[PATCH net-next 3/5] net: hns3: add ethtool -p support for phy device

2018-01-17 Thread Peng Li
From: Jian Shen Add led location support for phy device. The led will keep blinking with frequency 2HZ when locating. Signed-off-by: Jian Shen Signed-off-by: Peng Li --- drivers/net/ethernet/hisilicon/hns3/hnae3.h| 2 + drivers/net/ethernet/hisilicon/hns3/hns3_ethtool.c | 12 +++

[PATCH net-next 4/5] net: hns3: add ethtool -p support for fiber port

2018-01-17 Thread Peng Li
From: Jian Shen Add led location support for fiber port. The led will keep blinking when locating. Signed-off-by: Jian Shen Signed-off-by: Peng Li --- .../net/ethernet/hisilicon/hns3/hns3pf/hclge_cmd.h | 20

[PATCH net-next 4/5] net: hns3: add ethtool -p support for fiber port

2018-01-17 Thread Peng Li
From: Jian Shen Add led location support for fiber port. The led will keep blinking when locating. Signed-off-by: Jian Shen Signed-off-by: Peng Li --- .../net/ethernet/hisilicon/hns3/hns3pf/hclge_cmd.h | 20 .../ethernet/hisilicon/hns3/hns3pf/hclge_main.c| 101 -

Re: blk-mq: don't dispatch request in blk_mq_request_direct_issue if queue is busy

2018-01-17 Thread Laurence Oberman
On Wed, 2018-01-17 at 23:36 -0500, Mike Snitzer wrote: > On Wed, Jan 17 2018 at 11:06pm -0500, > Ming Lei wrote: > > > If we run into blk_mq_request_direct_issue(), when queue is busy, > > we > > don't want to dispatch this request into hctx->dispatch_list, and > > what we

Re: blk-mq: don't dispatch request in blk_mq_request_direct_issue if queue is busy

2018-01-17 Thread Laurence Oberman
On Wed, 2018-01-17 at 23:36 -0500, Mike Snitzer wrote: > On Wed, Jan 17 2018 at 11:06pm -0500, > Ming Lei wrote: > > > If we run into blk_mq_request_direct_issue(), when queue is busy, > > we > > don't want to dispatch this request into hctx->dispatch_list, and > > what we need to do is to

Re: [PATCH v5 12/44] clk: davinci: Add platform information for TI DA850 PSC

2018-01-17 Thread Sekhar Nori
On Thursday 18 January 2018 12:38 AM, David Lechner wrote: > It is looking like this: > > > static const struct davinci_psc_clkdev_info emfia_clkdev[] __initconst = { > LPSC_CLKDEV(NULL,    "ti-aemif"), > LPSC_CLKDEV("aemif",    "davinci-nand.0"), > { } > }; > > static const struct

Re: [PATCH v5 12/44] clk: davinci: Add platform information for TI DA850 PSC

2018-01-17 Thread Sekhar Nori
On Thursday 18 January 2018 12:38 AM, David Lechner wrote: > It is looking like this: > > > static const struct davinci_psc_clkdev_info emfia_clkdev[] __initconst = { > LPSC_CLKDEV(NULL,    "ti-aemif"), > LPSC_CLKDEV("aemif",    "davinci-nand.0"), > { } > }; > > static const struct

Re: [PATCH 0/7] PM /Domain/OPP: Add support to get performance state from DT

2018-01-17 Thread Viresh Kumar
On 22-12-17, 12:56, Viresh Kumar wrote: > Hi, > > Now that the DT bindings [1] are already Reviewed/Acked by respective > maintainers, here is the code to start using them. > > The first two patches provide helpers in the OPP core, [3-5]/7 update > the PM domain core to start supporting domain

Re: [PATCH 0/7] PM /Domain/OPP: Add support to get performance state from DT

2018-01-17 Thread Viresh Kumar
On 22-12-17, 12:56, Viresh Kumar wrote: > Hi, > > Now that the DT bindings [1] are already Reviewed/Acked by respective > maintainers, here is the code to start using them. > > The first two patches provide helpers in the OPP core, [3-5]/7 update > the PM domain core to start supporting domain

Re: [PATCH v2] KVM: s390: wire up bpb feature

2018-01-17 Thread Martin Schwidefsky
On Wed, 17 Jan 2018 22:43:24 +0100 Christian Borntraeger wrote: > Conny can you review and ack as well? > > Paolo, Radim, > > As the other patches need to sync on the ifetch/nospec/gmb naming I have > changed my mind. :-) > This patch is independent from the other

Re: [PATCH v2] KVM: s390: wire up bpb feature

2018-01-17 Thread Martin Schwidefsky
On Wed, 17 Jan 2018 22:43:24 +0100 Christian Borntraeger wrote: > Conny can you review and ack as well? > > Paolo, Radim, > > As the other patches need to sync on the ifetch/nospec/gmb naming I have > changed my mind. :-) > This patch is independent from the other patches (as it just provides

Re: [PATCH V4 1/2] nvme: add NVME_CTRL_RESET_PREPARE state

2018-01-17 Thread James Smart
Thanks jianchoa. This helped. On 1/17/2018 7:13 PM, jianchao.wang wrote: Actually, this patchset is to fix a issue in nvme_timeout. Please consider the following scenario. nvme_reset_ctrl -> set state to RESETTING -> queue reset_work (scheduling)

Re: [PATCH V4 1/2] nvme: add NVME_CTRL_RESET_PREPARE state

2018-01-17 Thread James Smart
Thanks jianchoa. This helped. On 1/17/2018 7:13 PM, jianchao.wang wrote: Actually, this patchset is to fix a issue in nvme_timeout. Please consider the following scenario. nvme_reset_ctrl -> set state to RESETTING -> queue reset_work (scheduling)

Re: [PATCH v5 3/5] misc serdev: Add w2sg0004 (gps receiver) power control driver

2018-01-17 Thread Johan Hovold
On Fri, Jan 12, 2018 at 06:59:59PM +0100, H. Nikolaus Schaller wrote: > Hi Johan, > > > Am 12.01.2018 um 16:39 schrieb Johan Hovold : > > > >> Let's restart this discussion and focus on the main roadblock (others > >> are minor details which can be sorted out later). > >> > >>

Re: [PATCH v5 3/5] misc serdev: Add w2sg0004 (gps receiver) power control driver

2018-01-17 Thread Johan Hovold
On Fri, Jan 12, 2018 at 06:59:59PM +0100, H. Nikolaus Schaller wrote: > Hi Johan, > > > Am 12.01.2018 um 16:39 schrieb Johan Hovold : > > > >> Let's restart this discussion and focus on the main roadblock (others > >> are minor details which can be sorted out later). > >> > >> If it feels like

Re: [PATCH v5 3/4] PCI/DPC: Unify and plumb error handling into DPC

2018-01-17 Thread poza
On 2018-01-18 10:52, p...@codeaurora.org wrote: On 2018-01-17 22:15, Sinan Kaya wrote: On 1/17/2018 5:37 AM, Oza Pawandeep wrote: + driver = pci_find_dpc_service(udev); +#endif #if IS_ENABLED(CONFIG_PCIEAER) - /* Use the aer driver of the component firstly */ -

Re: [PATCH v5 3/4] PCI/DPC: Unify and plumb error handling into DPC

2018-01-17 Thread poza
On 2018-01-18 10:52, p...@codeaurora.org wrote: On 2018-01-17 22:15, Sinan Kaya wrote: On 1/17/2018 5:37 AM, Oza Pawandeep wrote: + driver = pci_find_dpc_service(udev); +#endif #if IS_ENABLED(CONFIG_PCIEAER) - /* Use the aer driver of the component firstly */ -

Re: [PATCH v5 3/4] PCI/DPC: Unify and plumb error handling into DPC

2018-01-17 Thread poza
On 2018-01-18 10:47, p...@codeaurora.org wrote: On 2018-01-17 22:16, Sinan Kaya wrote: On 1/17/2018 5:37 AM, Oza Pawandeep wrote: +++ b/include/linux/dpc.h @@ -0,0 +1,9 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + +#ifndef _DPC_H_ +#define _DPC_H_ + +#define DPC_FATAL 4 + +#endif

Re: [PATCH v5 3/4] PCI/DPC: Unify and plumb error handling into DPC

2018-01-17 Thread poza
On 2018-01-18 10:47, p...@codeaurora.org wrote: On 2018-01-17 22:16, Sinan Kaya wrote: On 1/17/2018 5:37 AM, Oza Pawandeep wrote: +++ b/include/linux/dpc.h @@ -0,0 +1,9 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + +#ifndef _DPC_H_ +#define _DPC_H_ + +#define DPC_FATAL 4 + +#endif

Re: [PATCH 2/3] power: supply: add cros-ec USB PD charger driver.

2018-01-17 Thread Aishwarya Pant
On Wed, Jan 17, 2018 at 06:59:31PM +0100, Enric Balletbo i Serra wrote: > From: Sameer Nanda > > This driver gets various bits of information about what is connected to > USB PD ports from the EC and converts that into power_supply properties. > > Signed-off-by: Sameer

Re: [PATCH 2/3] power: supply: add cros-ec USB PD charger driver.

2018-01-17 Thread Aishwarya Pant
On Wed, Jan 17, 2018 at 06:59:31PM +0100, Enric Balletbo i Serra wrote: > From: Sameer Nanda > > This driver gets various bits of information about what is connected to > USB PD ports from the EC and converts that into power_supply properties. > > Signed-off-by: Sameer Nanda > Signed-off-by:

[ANNOUNCE] Git v2.16.0

2018-01-17 Thread Junio C Hamano
The latest feature release Git v2.16.0 is now available at the usual places. It is comprised of 509 non-merge commits since v2.15.0, contributed by 91 people, 26 of which are new faces. The tarballs are found at: https://www.kernel.org/pub/software/scm/git/ The following public

[ANNOUNCE] Git v2.16.0

2018-01-17 Thread Junio C Hamano
The latest feature release Git v2.16.0 is now available at the usual places. It is comprised of 509 non-merge commits since v2.15.0, contributed by 91 people, 26 of which are new faces. The tarballs are found at: https://www.kernel.org/pub/software/scm/git/ The following public

Re: [PATCH v5 0/2] printk: Console owner and waiter logic cleanup

2018-01-17 Thread Sergey Senozhatsky
On (01/17/18 12:05), Tejun Heo wrote: [..] > > This could very well be a great place to force offloading. If a printk > > is called from within a printk, at the same context (normal, softirq, > > irq or NMI), then we should trigger the offloading. > > I was thinking more of a timeout based

Re: [PATCH v5 0/2] printk: Console owner and waiter logic cleanup

2018-01-17 Thread Sergey Senozhatsky
On (01/17/18 12:05), Tejun Heo wrote: [..] > > This could very well be a great place to force offloading. If a printk > > is called from within a printk, at the same context (normal, softirq, > > irq or NMI), then we should trigger the offloading. > > I was thinking more of a timeout based

Re: [PATCH v5 0/2] printk: Console owner and waiter logic cleanup

2018-01-17 Thread Sergey Senozhatsky
On (01/17/18 12:12), Steven Rostedt wrote: [..] > /* > * Can we actually use the console at this time on this cpu? > @@ -2333,6 +2390,7 @@ void console_unlock(void) > > for (;;) { > struct printk_log *msg; > + bool offload; > size_t ext_len = 0; >

Re: [PATCH v5 0/2] printk: Console owner and waiter logic cleanup

2018-01-17 Thread Sergey Senozhatsky
On (01/17/18 12:12), Steven Rostedt wrote: [..] > /* > * Can we actually use the console at this time on this cpu? > @@ -2333,6 +2390,7 @@ void console_unlock(void) > > for (;;) { > struct printk_log *msg; > + bool offload; > size_t ext_len = 0; >

[PATCH 2/4] i2c: xlp9xx: Handle transactions with I2C_M_RECV_LEN properly

2018-01-17 Thread George Cherian
In case of transaction with I2C_M_RECV_LEN set, make sure the driver reads the first byte and then updates the RX fifo with the expected length. Set threshold to 1 byte so that driver gets an interrupt on receiving the first byte. After which the transfer length is updated depending on the

[PATCH 2/4] i2c: xlp9xx: Handle transactions with I2C_M_RECV_LEN properly

2018-01-17 Thread George Cherian
In case of transaction with I2C_M_RECV_LEN set, make sure the driver reads the first byte and then updates the RX fifo with the expected length. Set threshold to 1 byte so that driver gets an interrupt on receiving the first byte. After which the transfer length is updated depending on the

[PATCH 3/4] i2c: xlp9xx: report SMBus block read functionality

2018-01-17 Thread George Cherian
From: Dmitry Bazhenov Report SMBus block read functionality which is actually supported. Signed-off-by: Dmitry Bazhenov --- drivers/i2c/busses/i2c-xlp9xx.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git

[PATCH 3/4] i2c: xlp9xx: report SMBus block read functionality

2018-01-17 Thread George Cherian
From: Dmitry Bazhenov Report SMBus block read functionality which is actually supported. Signed-off-by: Dmitry Bazhenov --- drivers/i2c/busses/i2c-xlp9xx.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/i2c/busses/i2c-xlp9xx.c b/drivers/i2c/busses/i2c-xlp9xx.c

[PATCH 1/4] i2c: xlp9xx: return ENXIO on slave address NACK

2018-01-17 Thread George Cherian
From: Dmitry Bazhenov Fix the driver violation of the common practice to return ENXIO error on a slave address NACK. Signed-off-by: Dmitry Bazhenov Signed-off-by: George Cherian ---

[PATCH 4/4] i2c: xlp9xx: Check for Bus state after every transfer

2018-01-17 Thread George Cherian
I2C bus enters the STOP condition after the DATA_DONE interrupt is raised. Essentially the driver should be checking the bus state before sending the next transaction. In case the next transaction is initiated while the bus is busy, the prior transactions stop condition is not acheived. Add the

[PATCH 1/4] i2c: xlp9xx: return ENXIO on slave address NACK

2018-01-17 Thread George Cherian
From: Dmitry Bazhenov Fix the driver violation of the common practice to return ENXIO error on a slave address NACK. Signed-off-by: Dmitry Bazhenov Signed-off-by: George Cherian --- drivers/i2c/busses/i2c-xlp9xx.c | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git

[PATCH 4/4] i2c: xlp9xx: Check for Bus state after every transfer

2018-01-17 Thread George Cherian
I2C bus enters the STOP condition after the DATA_DONE interrupt is raised. Essentially the driver should be checking the bus state before sending the next transaction. In case the next transaction is initiated while the bus is busy, the prior transactions stop condition is not acheived. Add the

Re: [PATCH v5 4/4] PCI/DPC: Enumerate the devices after DPC trigger event

2018-01-17 Thread poza
On 2018-01-18 08:26, Keith Busch wrote: On Wed, Jan 17, 2018 at 08:27:39AM -0800, Sinan Kaya wrote: On 1/17/2018 5:37 AM, Oza Pawandeep wrote: > +static bool dpc_wait_link_active(struct pci_dev *pdev) > +{ I think you can also make this function common instead of making another copy here. Of

Re: [PATCH v5 4/4] PCI/DPC: Enumerate the devices after DPC trigger event

2018-01-17 Thread poza
On 2018-01-18 08:26, Keith Busch wrote: On Wed, Jan 17, 2018 at 08:27:39AM -0800, Sinan Kaya wrote: On 1/17/2018 5:37 AM, Oza Pawandeep wrote: > +static bool dpc_wait_link_active(struct pci_dev *pdev) > +{ I think you can also make this function common instead of making another copy here. Of

[PATCH v2] ASoC: use seq_file to dump the contents of dai_list,platform_list and codec_list

2018-01-17 Thread Donglin Peng
Now the debugfs files dais/platforms/codecs have a size limit PAGE_SIZE and the user can not see the whole contents of dai_list/platform_list/codec_list when they are larger than this limit. This patch uses seq_file instead to make sure dais/platforms/codecs show the full contents of

[PATCH v2] ASoC: use seq_file to dump the contents of dai_list,platform_list and codec_list

2018-01-17 Thread Donglin Peng
Now the debugfs files dais/platforms/codecs have a size limit PAGE_SIZE and the user can not see the whole contents of dai_list/platform_list/codec_list when they are larger than this limit. This patch uses seq_file instead to make sure dais/platforms/codecs show the full contents of

[PATCH v2] selftest: support run subset of selftests when running installed selftests

2018-01-17 Thread Zong Li
Simply use the first argument to specify the subset of selftests. Use comma notation to separate multiple tests. (e.g. ./run_kselftest.sh size,timers,...) Default behaviour is running all selftests installed. Each selftest be defined as function that we can run one of selftests. The function name

[PATCH v2] selftest: support run subset of selftests when running installed selftests

2018-01-17 Thread Zong Li
Simply use the first argument to specify the subset of selftests. Use comma notation to separate multiple tests. (e.g. ./run_kselftest.sh size,timers,...) Default behaviour is running all selftests installed. Each selftest be defined as function that we can run one of selftests. The function name

[PATCH v2] irqchip/gic-v3-its: Add workaround for ThunderX2 erratum #174

2018-01-17 Thread Ganapatrao Kulkarni
This erratum is observed on the ThunderX2 GICv3 ITS. When a MOVI command is used to change affinity of a LPI to a collection/cpu on another node, the LPI is not delivered to the cpu. An additional INV command is required after the MOVI to deliver the LPI to the new destination. If we add INV

[PATCH v2] irqchip/gic-v3-its: Add workaround for ThunderX2 erratum #174

2018-01-17 Thread Ganapatrao Kulkarni
This erratum is observed on the ThunderX2 GICv3 ITS. When a MOVI command is used to change affinity of a LPI to a collection/cpu on another node, the LPI is not delivered to the cpu. An additional INV command is required after the MOVI to deliver the LPI to the new destination. If we add INV

Re: [PATCH v5 4/4] PCI/DPC: Enumerate the devices after DPC trigger event

2018-01-17 Thread poza
On 2018-01-17 21:57, Sinan Kaya wrote: On 1/17/2018 5:37 AM, Oza Pawandeep wrote: +static bool dpc_wait_link_active(struct pci_dev *pdev) +{ I think you can also make this function common instead of making another copy here. Of course, this would be another patch. ok I will make a separate

Re: [PATCH v5 4/4] PCI/DPC: Enumerate the devices after DPC trigger event

2018-01-17 Thread poza
On 2018-01-17 21:57, Sinan Kaya wrote: On 1/17/2018 5:37 AM, Oza Pawandeep wrote: +static bool dpc_wait_link_active(struct pci_dev *pdev) +{ I think you can also make this function common instead of making another copy here. Of course, this would be another patch. ok I will make a separate

Re: [PATCH v5 3/4] PCI/DPC: Unify and plumb error handling into DPC

2018-01-17 Thread poza
On 2018-01-17 22:15, Sinan Kaya wrote: On 1/17/2018 5:37 AM, Oza Pawandeep wrote: + driver = pci_find_dpc_service(udev); +#endif #if IS_ENABLED(CONFIG_PCIEAER) - /* Use the aer driver of the component firstly */ - driver = pci_find_aer_service(udev); I think we need

Re: [PATCH v5 3/4] PCI/DPC: Unify and plumb error handling into DPC

2018-01-17 Thread poza
On 2018-01-17 22:15, Sinan Kaya wrote: On 1/17/2018 5:37 AM, Oza Pawandeep wrote: + driver = pci_find_dpc_service(udev); +#endif #if IS_ENABLED(CONFIG_PCIEAER) - /* Use the aer driver of the component firstly */ - driver = pci_find_aer_service(udev); I think we need

Re: [PATCH] gitignore: add *.gcda files

2018-01-17 Thread Jaejoong Kim
2018-01-17 22:07 GMT+09:00 Peter Oberparleiter : > On 09.01.2018 06:17, Jaejoong Kim wrote: >> 2017-12-20 16:09 GMT+09:00 Jaejoong Kim : >>> Ignore the *.gcda files generated by gcov >>> >>> Signed-off-by: Jaejoong Kim >>>

Re: [PATCH] gitignore: add *.gcda files

2018-01-17 Thread Jaejoong Kim
2018-01-17 22:07 GMT+09:00 Peter Oberparleiter : > On 09.01.2018 06:17, Jaejoong Kim wrote: >> 2017-12-20 16:09 GMT+09:00 Jaejoong Kim : >>> Ignore the *.gcda files generated by gcov >>> >>> Signed-off-by: Jaejoong Kim >>> --- >>> .gitignore | 1 + >>> 1 file changed, 1 insertion(+) >>> >>> diff

Re: [PATCH v5 3/4] PCI/DPC: Unify and plumb error handling into DPC

2018-01-17 Thread poza
On 2018-01-17 22:16, Sinan Kaya wrote: On 1/17/2018 5:37 AM, Oza Pawandeep wrote: +++ b/include/linux/dpc.h @@ -0,0 +1,9 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + +#ifndef _DPC_H_ +#define _DPC_H_ + +#define DPC_FATAL 4 + +#endif //_DPC_H_ + can you keep this in drivers/pci.h

Re: [PATCH v5 3/4] PCI/DPC: Unify and plumb error handling into DPC

2018-01-17 Thread poza
On 2018-01-17 22:16, Sinan Kaya wrote: On 1/17/2018 5:37 AM, Oza Pawandeep wrote: +++ b/include/linux/dpc.h @@ -0,0 +1,9 @@ +/* SPDX-License-Identifier: GPL-2.0 */ + +#ifndef _DPC_H_ +#define _DPC_H_ + +#define DPC_FATAL 4 + +#endif //_DPC_H_ + can you keep this in drivers/pci.h

Re: kexec reboot fails with extra wbinvd introduced for AME SME

2018-01-17 Thread Tom Lendacky
On 1/17/2018 8:29 PM, Dave Young wrote: > On 01/17/18 at 06:14pm, Linus Torvalds wrote: >> On Wed, Jan 17, 2018 at 5:47 PM, Dave Young wrote: >>> >>> It does not work with just once wbinvd(), and it only works with >>> removing the wbinvd() for me. Tom's new post works for me

Re: kexec reboot fails with extra wbinvd introduced for AME SME

2018-01-17 Thread Tom Lendacky
On 1/17/2018 8:29 PM, Dave Young wrote: > On 01/17/18 at 06:14pm, Linus Torvalds wrote: >> On Wed, Jan 17, 2018 at 5:47 PM, Dave Young wrote: >>> >>> It does not work with just once wbinvd(), and it only works with >>> removing the wbinvd() for me. Tom's new post works for me as well >>> since

Re: [PATCH 3/3] arm64: Add work around for Arm Cortex-A55 Erratum 1024718

2018-01-17 Thread Channa
On 2018-01-17 02:28, Suzuki K Poulose wrote: On 17/01/18 03:34, ckad...@codeaurora.org wrote: On 2018-01-16 02:23, Suzuki K Poulose wrote: Some variants of the Arm Cortex-55 cores (r0p0, r0p1, r1p0) suffer from an erratum 1024718, which causes incorrect updates when DBM/AP bits in a page table

Re: [PATCH 3/3] arm64: Add work around for Arm Cortex-A55 Erratum 1024718

2018-01-17 Thread Channa
On 2018-01-17 02:28, Suzuki K Poulose wrote: On 17/01/18 03:34, ckad...@codeaurora.org wrote: On 2018-01-16 02:23, Suzuki K Poulose wrote: Some variants of the Arm Cortex-55 cores (r0p0, r0p1, r1p0) suffer from an erratum 1024718, which causes incorrect updates when DBM/AP bits in a page table

  1   2   3   4   5   6   7   8   9   10   >