[PATCH v1 2/4] pinctrl: tegra20: Provide CDEV1/2 clock muxes

Muxing of pins MCLK1/2 determine the muxing of the corresponding clocks. Make pinctrl driver to provide clock muxes for the CDEV1/2 pingroups, so that main clk-controller driver could get an actual parent clock for the CDEV1/2 clocks. Signed-off-by: Dmitry Osipenko --- drivers/pinctrl/tegra/pinc

[PATCH v1 4/4] ARM: dts: tegra20: Revert "Fix ULPI regression on Tegra20"

Commit 4c9a27a6c66d ("ARM: tegra: Fix ULPI regression on Tegra20") changed "ulpi-link" clock from CDEV2 to PLL_P_OUT4. Turned out that PLL_P_OUT4 is the parent of CDEV2 clock and original clock setup of "ulpi-link" was correct. The reverted patch was fixing USB for one board and broke the other, no

[PATCH v1 0/4] Restore ULPI USB on Tegra20

Hello, This series of patches fixes ULPI USB on Tegra20. The original problem was reported by Marcel Ziswiler, he found that "ulpi-link" clock was incorrectly set to CDEV2 instead of PLL_P_OUT4. Marcel made a patch that changed the "ulpi-link" clock to PLL_P_OUT4 and that fixed issue with the USB

Re: Linux messages full of `random: get_random_u32 called from`

On Thu, Apr 26, 2018 at 10:47:49PM +0200, Christian Brauner wrote: > > We have observed a similiar problem with libvirt. As soon as entropy is > provided the boot finishes otherwise it hangs for a long time. > This is not happening with v4.17-rc1 afaict. For libvirt there is at least an easy wor

Re: [PATCH] bsg referencing bus driver module

Any thoughts on this? Can we really drop a reference from a child device (bsg_class_device) to a parent device (Scsi_Host) while the child device is still around at fc_bsg_remove time? If not, please consider a fix with module references. I realized that the previous version of the fix had a probl

Re: [PATCH v2 6/6] rpmsg: glink: Expose rpmsg name attr for glink

Hi Chris, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on robh/for-next] [also build test WARNING on v4.17-rc2 next-20180426] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day

[PATCH v9 06/27] ARM: davinci: da850: add new clock init using common clock framework

This adds the new board-specific clock init in mach-davinci/da850.c using the new common clock framework drivers. The #ifdefs are needed to prevent compile errors until the entire ARCH_DAVINCI is converted. Also clean up the #includes since we are adding some here. Some CFGCHIP macros were remov

[PATCH v9 24/27] dt-bindings: timer: new bindings for TI DaVinci timer

This adds new device tree bindings for the timer IP block of TI DaVinci-like SoCs. Signed-off-by: David Lechner --- v9 changes: - new patch in v9 .../bindings/timer/ti,davinci-timer.txt | 24 +++ 1 file changed, 24 insertions(+) create mode 100644 Documentation/devicetr

[PATCH v9 26/27] ARM: davinci: da8xx-dt: switch to device tree clocks

This removes all of the clock init code from da8xx-dt.c. This includes all of the OF_DEV_AUXDATA that was just used for looking up clocks. Signed-off-by: David Lechner --- v9 changes: - changes to arch/arm/mach-davinci/time.c accidentally got squashed into this commit. will drop this later. v

[PATCH v9 27/27] ARM: dts: da850: Add clocks

This adds clock provider nodes for da850 and wires them up to all of the devices. Signed-off-by: David Lechner --- v9 changes: - change mcasp and vpif nodes from clocks to power-domains v8 changes: - fix typo in clock-names property of psc0 - added power-domains properties to nodes that define

[PATCH v9 25/27] ARM: davinci: add device tree support to timer

This adds device tree support to the davinci timer so that when clocks are moved to device tree, the timer will still work. Signed-off-by: David Lechner --- v9 changes: - none (there were supposed to be changed, but apparently they got squashed into the next commit - will fix on the next round

[PATCH v9 22/27] ARM: davinci: da8xx: Remove legacy USB and SATA clock init

This removes the unused legacy USB and SATA clock init code from arch/arm/mach-davinci/{devices,usb}-da8xx}.c. Signed-off-by: David Lechner Reviewed-by: Sekhar Nori --- v9 changes: - none v8 changes: - none v7 changes: - rebased - add davinci prefix to commit message v6 changes: - rebased

[PATCH v9 21/27] ARM: davinci: dm646x: Remove legacy clock init

This removes the unused legacy clock init code from arch/arm/mach-davinci/dm646x.c. Signed-off-by: David Lechner Reviewed-by: Sekhar Nori --- v9 changes: - rebased v8 changes: - none v7 changes: - rebased - add davinci prefix to commit message v6 changes: - rebased arch/arm/mach-davinci/d

[PATCH v9 19/27] ARM: davinci: dm365: Remove legacy clock init

This removes the unused legacy clock init code from arch/arm/mach-davinci/dm365.c. Signed-off-by: David Lechner Reviewed-by: Sekhar Nori --- v9 changes: - rebased v8 changes: - none v7 changes: - rebased - add davinci prefix to commit message v6 changes: - rebased arch/arm/mach-davinci/dm

[PATCH v9 23/27] ARM: davinci: remove legacy clocks

This removes the unused legacy clock code from arch/arm/mach-davinci/. Signed-off-by: David Lechner Reviewed-by: Sekhar Nori --- v9 changes: - none v8 changes: - none v7 changes: - rebased - add davinci prefix to commit message v6 changes: - rebased arch/arm/mach-davinci/clock.c

[PATCH v9 16/27] ARM: davinci: da830: Remove legacy clock init

This removes the unused legacy clock init code from arch/arm/mach-davinci/da830.c. Signed-off-by: David Lechner Reviewed-by: Sekhar Nori --- v9 changes: - rebased v8 changes: - none v7 changes: - rebased - add davinci prefix to commit message v6 changes: - rebased arch/arm/mach-davinci/boa

[PATCH v9 20/27] ARM: davinci: dm644x: Remove legacy clock init

This removes the unused legacy clock init code from arch/arm/mach-davinci/dm644x.c. Signed-off-by: David Lechner Reviewed-by: Sekhar Nori --- v9 changes: - rebased v8 changes: - none v7 changes: - rebased - add davinci prefix to commit message v6 changes: - rebased arch/arm/mach-davinci/d

[PATCH 0/2] Fix fsl_ifc_nand reading ONFI parameters to meet ONFI spec

Per ONFI specification (Rev. 4.0), if the CRC of the first parameter page read is not valid, the host should read redundant parameter page copies until it finds a valid copy. If all three parameter pages have invalid CRC values, the bit-wise majority may be used to recover the contents of the para

Re: [PATCH] net/mlx5: report persistent netdev stats across ifdown/ifup commands

Thanks! Looks like Eran's patch will be available much sooner than v4.18 release time frame (since v4.16 was just released). We will wait. :-) On 04/26/2018 04:43 PM, Saeed Mahameed wrote: Before you address my comments, it looks like Eran's work is converging and we will finalize the interna

[PATCH 1/2] Fix FSL NAND driver to read all ONFI parameter pages

Signed-off-by: Jane Wan --- drivers/mtd/nand/fsl_ifc_nand.c | 10 ++ 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/drivers/mtd/nand/fsl_ifc_nand.c b/drivers/mtd/nand/fsl_ifc_nand.c index ca36b35..a3cf6ca 100644 --- a/drivers/mtd/nand/fsl_ifc_nand.c +++ b/drivers/mtd/nand

[PATCH 2/2] Use bit-wise majority to recover the contents of ONFI parameter

Signed-off-by: Jane Wan --- drivers/mtd/nand/nand_base.c | 35 +++ 1 file changed, 31 insertions(+), 4 deletions(-) diff --git a/drivers/mtd/nand/nand_base.c b/drivers/mtd/nand/nand_base.c index c2e1232..161b523 100644 --- a/drivers/mtd/nand/nand_base.c +++ b/dr

[PATCH v9 18/27] ARM: davinci: dm355: Remove legacy clock init

This removes the unused legacy clock init code from arch/arm/mach-davinci/dm355.c. Signed-off-by: David Lechner Reviewed-by: Sekhar Nori --- v9 changes: - rebased v8 changes: - none v7 changes: - rebased - add davinci prefix to commit message v6 changes: - rebased arch/arm/mach-davinci/dm

Re: [PATCH 31/61] net: dsa: simplify getting .drvdata

On 04/19/2018 07:06 AM, Wolfram Sang wrote: > We should get drvdata from struct device directly. Going via > platform_device is an unneeded step back and forth. > > Signed-off-by: Wolfram Sang > --- > > Build tested only. buildbot is happy. Please apply individually. Similar to my other comment

[PATCH v9 09/27] ARM: davinci: dm644x: add new clock init using common clock framework

This adds the new board-specific clock init in mach-davinci/dm644x.c using the new common clock framework drivers. The #ifdefs are needed to prevent compile errors until the entire ARCH_DAVINCI is converted. Also clean up the #includes since we are adding some here. Signed-off-by: David Lechner

[PATCH v9 15/27] ARM: davinci: switch to common clock framework

This switches ARCH_DAVINCI to use the common clock framework. The legacy clock code in arch/arm/mach-davinci/ is no longer used. New drivers in drivers/clk/davinci/ are used instead. A few macros had to be moved to prevent compilation errors. Signed-off-by: David Lechner --- v9 changes: - none

[PATCH v9 14/27] ARM: davinci_all_defconfig: remove CONFIG_DAVINCI_RESET_CLOCKS

This removes CONFIG_DAVINCI_RESET_CLOCKS. The option has been removed from the kernel. Signed-off-by: David Lechner Reviewed-by: Sekhar Nori --- v9 changes: - none v8 changes: - none v7 changes: - none v6 changes: - none arch/arm/configs/davinci_all_defconfig | 1 - 1 file changed, 1 dele

[PATCH v9 17/27] ARM: davinci: da850: Remove legacy clock init

This removes the unused legacy clock init code from arch/arm/mach-davinci/da850.c. Signed-off-by: David Lechner Reviewed-by: Sekhar Nori --- v9 changes: - rebased v8 changes: - none v7 changes: - rebased - add davinci prefix to commit message v6 changes: - rebased arch/arm/mach-davinci/bo

[PATCH v9 11/27] ARM: davinci: da8xx: add new USB PHY clock init using common clock framework

This adds the new USB PHY clock init in mach-davinci/usb-da8xx.c using the new common clock framework drivers. The #ifdefs are needed to prevent compile errors until the entire ARCH_DAVINCI is converted. Signed-off-by: David Lechner --- v9 changes: - none v8 changes: - rebased on "ARM: davinci

[PATCH v9 13/27] ARM: davinci: remove CONFIG_DAVINCI_RESET_CLOCKS

The common clock framework will take care of disabling unused clocks when we switch from the legacy davinci clocks and having this enabled will cause compile errors after we switch, so remove it now. Signed-off-by: David Lechner Reviewed-by: Sekhar Nori --- v9 changes: - none v8 changes: - non

[PATCH v9 12/27] ARM: davinci: da8xx: add new sata_refclk init using common clock framework

This adds the new SATA REFCLK clock init in mach-davinci/devices-da8xx.c using the new common clock framework drivers. The #ifdefs are needed to prevent compile errors until the entire ARCH_DAVINCI is converted. Also, the #includes are sorted since we are adding some here. Signed-off-by: David L

[PATCH v9 10/27] ARM: davinci: dm646x: add new clock init using common clock framework

This adds the new board-specific clock init in mach-davinci/dm646x.c using the new common clock framework drivers. The #ifdefs are needed to prevent compile errors until the entire ARCH_DAVINCI is converted. Also clean up the #includes since we are adding some here. Signed-off-by: David Lechner

[PATCH v9 08/27] ARM: davinci: dm365: add new clock init using common clock framework

This adds the new board-specific clock init in mach-davinci/dm365.c using the new common clock framework drivers. The #ifdefs are needed to prevent compile errors until the entire ARCH_DAVINCI is converted. Also clean up the #includes since we are adding some here. Signed-off-by: David Lechner

[PATCH v9 04/27] ARM: davinci: pass clock as parameter to davinci_timer_init()

This changes davinci_timer_init() so that we pass the clock as a parameter instead of using clk_get(). This is done in preparation for converting to the common clock framework. It removes the requirement that we have to have a clock with con_id of "timer0", which will be good for DT bindings since

[PATCH v9 05/27] ARM: davinci: da830: add new clock init using common clock framework

This adds the new board-specific clock init in mach-davinci/da830.c using the new common clock framework drivers. The #ifdefs are needed to prevent compile errors until the entire ARCH_DAVINCI is converted. Also clean up the #includes since we are adding some here. Signed-off-by: David Lechner

[PATCH v9 01/27] clk: davinci: pll: allow dev == NULL

This modifies the TI DaVinci PLL clock driver to allow for the case when dev == NULL. On some (most) SoCs that use this driver, the PLL clock needs to be registered during early boot because it is used for clocksource/clockevent and there will be no platform device available. Signed-off-by: David

[PATCH v9 07/27] ARM: davinci: dm355: add new clock init using common clock framework

This adds the new board-specific clock init in mach-davinci/dm355.c using the new common clock framework drivers. The #ifdefs are needed to prevent compile errors until the entire ARCH_DAVINCI is converted. Also clean up the #includes since we are adding some here. Signed-off-by: David Lechner

[PATCH v9 03/27] clk: davinci: psc: allow for dev == NULL

On some davinci SoCs, we need to register the PSC clocks during early boot because they are needed for clocksource/clockevent. These changes allow for dev == NULL because in this case, we won't have a platform device for the clocks. Signed-off-by: David Lechner --- v9 changes: - new patch in v9

[PATCH v9 00/27] ARM: davinci: convert to common clock framework​

This series converts mach-davinci to use the common clock framework. The series works like this, the first 3 patches fix some issues with the clock drivers that have already been accepted into the mainline kernel. Then, starting with "ARM: davinci: pass clock as parameter to davinci_timer_init()"

[PATCH v9 02/27] clk: davinci: da850-pll: change PLL0 to CLK_OF_DECLARE

PLL0 on davinci/da850-type device needs to be registered early in boot because it is needed for clocksource/clockevent. Change the driver to use CLK_OF_DECLARE for this special case. Signed-off-by: David Lechner --- v9 changes: - new patch in v9 drivers/clk/davinci/pll-da850.c | 26 ++

[PATCH] staging: mt7621-eth: fix line over 80 char / extra line in mtk_set_link_ksettings()

Fix 'line over 80 characters' issue found by checkpatch.pl script in mtk_set_link_ksettings(). Fix extra line before end of function. Signed-off-by: Jefferson Capovilla --- drivers/staging/mt7621-eth/ethtool.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/drivers/stagin

Re: [PATCH net-next 1/2 v2] netns: restrict uevents

Christian Brauner writes: > On Thu, Apr 26, 2018 at 12:10:30PM -0500, Eric W. Biederman wrote: >> Christian Brauner writes: >> >> > On Thu, Apr 26, 2018 at 11:47:19AM -0500, Eric W. Biederman wrote: >> >> Christian Brauner writes: >> >> >> >> > On Tue, Apr 24, 2018 at 06:00:35PM -0500, Eric W

[PATCH 2/2] pinctrl: uniphier: add LD11 MPEG2-TS I/O pin-mux settings

The MPEG2-TS input/output core both accepts serial TS and parallel TS. The serial TS interface uses following pins: hscin0_s : HS0DOUT[0-3] hscin1_s : HS0DOUT[4-7] hscin2_s : HS1BCLKIN, HS1SYNCIN, HS1VALIN, HS1DIN0 hscout0_s: HS0DOUT[0-3] hscout1_s: HS0DOUT[4-7] And the parallel TS inte

Proposal

Hello Greetings to you today i asked before but i did't get a response please i know this might come to you as a surprise because you do not know me personally i have a business proposal for you please reply for more info. Best Regards, Esentepe Mahallesi Büyükdere Caddesi Kristal Kule B

[PATCH 1/2] pinctrl: uniphier: add LD20 MPEG2-TS I/O pin-mux settings

The MPEG2-TS input/output core both accepts serial TS and parallel TS. The serial TS interface uses following pins: hscin0_s : HS0DOUT[0-3] hscin1_s : HS0DOUT[4-7] hscin2_s : HS1BCLKIN, HS1SYNCIN, HS1VALIN, HS1DIN0 hscin3_s : HS1DIN[2-5] hscout0_s: HS0DOUT[0-3] hscout1_s: HS0DOUT[4-7]

[PATCH] clk: uniphier: add LD11/LD20 stream demux system clock

Add clock for MPEG2 transport stream I/O and demux system (HSC) on UniPhier LD11/LD20 SoCs. Signed-off-by: Katsuhiro Suzuki --- drivers/clk/uniphier/clk-uniphier-sys.c | 5 + 1 file changed, 5 insertions(+) diff --git a/drivers/clk/uniphier/clk-uniphier-sys.c b/drivers/clk/uniphier/clk-uni

[PATCH] reset: uniphier: add LD11/LD20 stream demux system reset control

Add reset lines for MPEG2 transport stream I/O and demux system (HSC) on UniPhier LD11/LD20 SoCs. Signed-off-by: Katsuhiro Suzuki --- drivers/reset/reset-uniphier.c | 2 ++ 1 file changed, 2 insertions(+) diff --git a/drivers/reset/reset-uniphier.c b/drivers/reset/reset-uniphier.c index 360e06b

Re: [RFC PATCH v3 1/3] ima: extend clone() with IMA namespace support

Stefan Berger writes: > On 04/19/2018 11:35 AM, John Johansen wrote: >> It sounds like its already decided, with ima and selinux going with an >> unshare file within their own fs. >> >> AppArmor went a different route already, splitting namespace creation (mkdir >> in the apparmorfs policy/nam

[PATCH v3] KVM: Extend MAX_IRQ_ROUTES to 4096 for all archs

From: Wanpeng Li Our virtual machines make use of device assignment by configuring 12 NVMe disks for high I/O performance. Each NVMe device has 129 MSI-X Table entries: Capabilities: [50] MSI-X: Enable+ Count=129 Masked-Vector table: BAR=0 offset=2000 The windows virtual machines fail to bo

RE: Makefile:636: arch/score/Makefile: No such file or directory

> >Please stop trying to build the removed architectures: tile, blackfin, > >metag, m32r, frv, mn10300, cris and score. > > > >https://lwn.net/Articles/748074/ has details about why this broke. > > Sorry about that! It looks the architectures removal is not thorough > enough. Hao, would you help

Re: Linux 4.17.0-rc2 - WARNING: inconsistent lock state

On Wed, Apr 25, 2018 at 08:44:04AM -0600, Shuah Khan wrote: > I am seeing the following on my system with 4.17-rc2. Probably in 4.17-rc1 > as well. > > Something to be concerned about. Is this related to > Commit: a45403b51582a87872927a3e0fc0a389c26867f1 > ext4: always initialize the crc32c checks

[PATCH 0/3] A few hist trigger fixes

Hi Steve, Here are a few patches that fix some problems found when testing the hist trigger inter-event (e.g. latency) support patches. The first fixes a problem I noticed when printing flags. The remaining two add some hist_err() calls for fields, the first reported by Masami, the second someth

[PATCH 1/3] tracing: Restore proper field flag printing when displaying triggers

The flag-printing code used when displaying hist triggers somehow got dropped during refactoring of the inter-event patchset. This restores it. Below are a couple examples - in the first case, .usecs wasn't being displayed properly for common_timestamps and the second illustrates the same for oth

[PATCH 3/3] tracing: Add field modifier parsing hist error for hist triggers

If the user specifies an invalid field modifier for a hist trigger, the current code correctly flags that as an error, but doesn't tell the user what happened. Fix this by invoking hist_err() with an appropriate message when invalid modifiers are specified. Before: # echo 'hist:keys=pid:ts0=co

[PATCH 2/3] tracing: Add field parsing hist error for hist triggers

If the user specifies a nonexistent field for a hist trigger, the current code correctly flags that as an error, but doesn't tell the user what happened. Fix this by invoking hist_err() with an appropriate message when nonexistent fields are specified. Before: # echo 'hist:keys=pid:ts0=common_

Re: [Lsf-pc] [LSF/MM TOPIC NOTES] x86 ZONE_DMA love

On Thu, 2018-04-26 at 21:54 +, Luis R. Rodriguez wrote: > Below are my notes on the ZONE_DMA discussion at LSF/MM 2018. There > were some > earlier discussion prior to my arrival to the session about moving > around > ZOME_DMA around, if someone has notes on that please share too :) We took no

Re: Moving unmaintained filesystems to staging

On Wed, Apr 25, 2018 at 11:11 PM, Pavel Machek wrote: > On Wed 2018-04-25 08:46:02, Matthew Wilcox wrote: >> Recently ncpfs got moved to staging. Also recently, we had some fuzzer >> developers report bugs in hfs, which they deem a security hole because >> Ubuntu attempts to automount an inserted

[PATCH] documentation: core-api: rearrange a few kernel-api chapters and sections

) CRC and Math Functions chapter Signed-off-by: Randy Dunlap --- Documentation/core-api/kernel-api.rst | 60 1 file changed, 30 insertions(+), 30 deletions(-) --- linux-next-20180426.orig/Documentation/core-api/kernel-api.rst +++ linux-next-20180426/Documentation/core

[PATCH] m68k: Fix calendar month regression on M68328

My earlier fix for read_persistent_clock() neglected to cover m68328_hwclk(). Correct this oversight. Cc: Geert Uytterhoeven Signed-off-by: Finn Thain --- Greg, the read_persistent_clock() change has already been queued by Geert. Should this patch be pushed together with that one (presuming your

Re: [PATCH -tip v2 0/7] kprobes: Fix %p in kprobes

On Thu, 26 Apr 2018 10:40:22 +0200 Greg KH wrote: > > > This is not the correct way to submit patches for inclusion in the > stable kernel tree. Please read: > https://www.kernel.org/doc/html/latest/process/stable-kernel-rules.html > for how to do this properly. > > Is it because he did

Re: [PATCH 7/7] clk: meson: axg: add the audio clock controller driver

Hi Jerome, I love your patch! Yet something to improve: [auto build test ERROR on clk/clk-next] [also build test ERROR on v4.17-rc2 next-20180426] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day-ci/linux

Re: [PATCH -tip v2 4/7] kprobes: Replace %p with other pointer types

On Thu, 26 Apr 2018 17:10:03 +0900 Masami Hiramatsu wrote: > Replace %p with appropriate pointer types (or just remove it) > - Use %pS if possible > - Use %px only for the function right before BUG(). > - Remove unneeded error message. I'm not sure "right before BUG()" is legitimate for using

[PATCH] mac80211: fix kernel-doc "bad line" warning

nux-next-20180426.orig/include/net/mac80211.h +++ linux-next-20180426/include/net/mac80211.h @@ -2080,7 +2080,7 @@ struct ieee80211_txq { * virtual interface might not be given air time for the transmission of * the frame, as it is not synced with the AP/P2P GO yet, and thus

Re: [PATCH v2 6/6] rpmsg: glink: Expose rpmsg name attr for glink

Hi Chris, Thank you for the patch! Perhaps something to improve: [auto build test WARNING on robh/for-next] [also build test WARNING on v4.17-rc2 next-20180426] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] url: https://github.com/0day

[PATCH 2/4] fpga: manager: change api, don't use drvdata

From: Alan Tull Change fpga_mgr_register to not set or use drvdata. This supports the case where a PCIe device has more than one manager. Add fpga_mgr_create/free functions. Change fpga_mgr_register and fpga_mgr_unregister functions to take the mgr struct as their only parameter. struct fpg

[PATCH 3/4] fpga: bridge: change api, don't use drvdata

From: Alan Tull Change fpga_bridge_register to not set drvdata. This is to support the case where a PCIe device can have more than one bridge. Add API functions to create/free the fpga bridge struct. Change fpga_bridge_register/unregister to take FPGA bridge struct as the only parameter. str

[PATCH 4/4] fpga: region: change api, add fpga_region_create/free

From: Alan Tull Add fpga_region_create/free API functions. Change fpga_region_register to take FPGA region struct as the only parameter. Change fpga_region_unregister to return void. struct fpga_region *fpga_region_create(struct device *dev, struct fpga_manager *mgr,

[PATCH 1/4] fpga: region: don't use drvdata in common fpga code

From: Alan Tull Changes to fpga_region_register function to not set drvdata. Setting drvdata is fine for DT based devices that will have one region per platform device. However PCIe based devices may have multiple FPGA regions under one PCIe device. Without these changes, the PCIe solution has

[PATCH 0/4] FPGA Manager Patches for 4.18

Hi Greg, Here's Alan's reworked patchset changing the API for creating and registering FPGA Managers, Bridges and Regions following your suggestions on the API. These go on top of Paolo and Alan's patches that you queued up the other day. Thanks, Moritz Alan Tull (4): fpga: region: don't use

[PATCH] Documentation: driver-api: fix device_connection.rst kernel-doc error

driver-api/device_connection.rst |2 +- 1 file changed, 1 insertion(+), 1 deletion(-) --- linux-next-20180426.orig/Documentation/driver-api/device_connection.rst +++ linux-next-20180426/Documentation/driver-api/device_connection.rst @@ -40,4 +40,4 @@ API --- .. kernel-doc:: drivers/bas

Re: [PATCH net-next v5 1/3] vmcore: add API to collect hardware dump in second kernel

While looking this over I found a bug in the way elf notes are being composed. Rahul Lakkireddy writes: > diff --git a/fs/proc/vmcore.c b/fs/proc/vmcore.c > index a45f0af22a60..7395462d2f86 100644 > --- a/fs/proc/vmcore.c > +++ b/fs/proc/vmcore.c > @@ -1145,6 +1150,132 @@ static int __init parse

RE: [PATCH V4 3/6] ARM: dts: imx6sx-sabreauto: add IO expander max7310 support

Anson Huang Best Regards! > -Original Message- > From: Fabio Estevam [mailto:feste...@gmail.com] > Sent: Friday, April 27, 2018 1:24 AM > To: Anson Huang > Cc: Shawn Guo ; Sascha Hauer > ; Fabio Estevam ; Rob > Herring ; Mark Rutland ; > Russell King - ARM Linux ; dl-linux-imx > ; mode

Re: [PATCH] m68k: Fix calendar month regression on M68328

Hi Finn, On 27/04/18 11:12, Finn Thain wrote: > My earlier fix for read_persistent_clock() neglected to cover > m68328_hwclk(). Correct this oversight. > > Cc: Geert Uytterhoeven > Signed-off-by: Finn Thain > --- > Greg, the read_persistent_clock() change has already been queued > by Geert. Sho

RE: [PATCH 4/5] ARM: dts: imx6sx-sabreauto: add fec support

Anson Huang Best Regards! > -Original Message- > From: Fabio Estevam [mailto:feste...@gmail.com] > Sent: Friday, April 27, 2018 1:29 AM > To: Anson Huang > Cc: Shawn Guo ; Sascha Hauer > ; Fabio Estevam ; Rob > Herring ; Mark Rutland ; > dl-linux-imx ; moderated list:ARM/FREESCALE IMX

Re: [PATCH 0/3] A few hist trigger fixes

On Thu, 26 Apr 2018 20:04:46 -0500 Tom Zanussi wrote: > Hi Steve, > > Here are a few patches that fix some problems found when testing the > hist trigger inter-event (e.g. latency) support patches. > > The first fixes a problem I noticed when printing flags. > > The remaining two add some hist

Re: [f2fs-dev] [PATCH 5/5] f2fs: enforce fsync_mode=strict for renamed directory

On 2018/4/26 23:32, Jaegeuk Kim wrote: > On 04/25, Chao Yu wrote: >> On 2018/4/25 13:46, Jaegeuk Kim wrote: >>> This is to give a option for user to be able to recover B/foo in the below >>> case. >>> >>> mkdir A >>> sync() >>> rename(A, B) >>> creat (B/foo) >>> fsync (B/foo) >>> ---crash--- >> >>

Re: [PATCH v7 00/16] tracing: probeevent: Improve fetcharg features

On Wed, 25 Apr 2018 21:16:06 +0900 Masami Hiramatsu wrote: > Hi, > > This is the 7th version of the fetch-arg improvement series. > This includes variable changes on fetcharg framework like, > > - Add fetcharg testcases (syntax, argN, symbol, string and array) > and probepoint testcase. > - R

Re: [PATCH] do not call trace_printk on non-debug build

On Wed, 25 Apr 2018 04:53:33 + Wei Wang wrote: > On Tue, Apr 24, 2018 at 12:26 PM Steven Rostedt wrote: > > A lot of kernel developers use trace_printk() and I want to make it as > > easy to use as possible. I don't want to add a config to enable it, > > because that would be something that

Re: Unable to handle kernel paging request in snd_seq_oss_readq_puts

On Thu, Apr 26, 2018 at 09:17:45AM +0200, Takashi Iwai wrote: > On Thu, 26 Apr 2018 06:52:27 +0200, > DaeRyong Jeong wrote: > > > > We report the crash: > > unable to handle kernel paging request in snd_seq_oss_readq_puts > > > > This crash has been found in v4.16 using RaceFuzzer (a modified > >

[PATCH v2 2/2] pinctrl: uniphier: add LD11 MPEG2-TS I/O pin-mux settings

The MPEG2-TS input/output core both accepts serial TS and parallel TS. The serial TS interface uses following pins: hscin0_s : HS0DOUT[0-3] hscin1_s : HS0DOUT[4-7] hscin2_s : HS1BCLKIN, HS1SYNCIN, HS1VALIN, HS1DIN0 hscout0_s: HS0DOUT[0-3] hscout1_s: HS0DOUT[4-7] And the parallel TS inte

[PATCH v2 1/2] pinctrl: uniphier: add LD20 MPEG2-TS I/O pin-mux settings

The MPEG2-TS input/output core both accepts serial TS and parallel TS. The serial TS interface uses following pins: hscin0_s : HS0DOUT[0-3] hscin1_s : HS0DOUT[4-7] hscin2_s : HS1BCLKIN, HS1SYNCIN, HS1VALIN, HS1DIN0 hscin3_s : HS1DIN[2-5] hscout0_s: HS0DOUT[0-3] hscout1_s: HS0DOUT[4-7]

Re: [PATCH v2] f2fs: avoid stucking GC due to atomic write

On 2018/4/26 23:54, Jaegeuk Kim wrote: > On 04/24, Chao Yu wrote: >> f2fs doesn't allow abuse on atomic write class interface, so except >> limiting in-mem pages' total memory usage capacity, we need to limit >> atomic-write usage as well when filesystem is seriously fragmented, >> otherwise we may

Re: [f2fs-dev] [PATCH 4/5 v2] f2fs: sanity check for total valid blocks

On 2018/4/26 23:29, Jaegeuk Kim wrote: > This patch enhances sanity check for SIT entries. > > syzbot hit the following crash on upstream commit > 83beed7b2b26f232d782127792dd0cd4362fdc41 (Fri Apr 20 17:56:32 2018 +) > Merge branch 'fixes' of > git://git.kernel.org/pub/scm/linux/kernel/git/ev

[PATCH net-next 1/3] net: dsa: mv88e6xxx: move trunk setup

Move the trunking setup out of Global 2 specific setup into the top level mv88e6xxx_setup function. Note that the 88E6390 family calls this LAG instead of Trunk and supports 32 possible ID routing vectors, with LAG ID bit 4 being placed in Global 2 register 0x1D... We don't need Trunk (or LAG) ID

[PATCH net-next 3/3] net: dsa: mv88e6xxx: remove Global 2 setup

The remaining values written to the Switch Management Register in the mv88e6xxx_g2_setup function are specific to 88E6352 and older, and are the default values anyway. Thus remove completely this function. The mv88e6xxx driver no more contains setup code to access arbitrary Global 2 registers. Si

[PATCH net-next 2/3] net: dsa: mv88e6xxx: move device mapping setup

Move the Device Mapping setup out of the specific Global 2 code, into the top level device setup function. Signed-off-by: Vivien Didelot --- drivers/net/dsa/mv88e6xxx/chip.c| 27 + drivers/net/dsa/mv88e6xxx/global2.c | 37 + drivers/net/dsa/mv8

[PATCH net-next 0/3] net: dsa: mv88e6xxx: remove Global 2 setup

Parts of the mv88e6xxx driver still write arbitrary registers of different banks at setup time, which is misleading especially when supporting multiple device models. This patchset moves two features setup into the top lovel mv88e6xxx_setup function and kills the old Global 2 register bank setup f

Re: [PATCH v2] f2fs: fix to avoid race during access gc_thread pointer

On 2018/4/27 0:03, Jaegeuk Kim wrote: > On 04/24, Chao Yu wrote: >> Thread A Thread BThread C >> - f2fs_remount >> - stop_gc_thread >> - f2fs_sbi_store >> - issue_discard_thread >>

Re: [PATCH v2] f2fs: fix to avoid race during access gc_thread pointer

On 2018/4/27 10:04, Chao Yu wrote: > On 2018/4/27 0:03, Jaegeuk Kim wrote: >> On 04/24, Chao Yu wrote: >>> Thread AThread BThread C >>> - f2fs_remount >>> - stop_gc_thread >>> - f2fs_sbi_store >>>

Re: testing io.low limit for blk-throttle

Hi Tejun and Joseph On 04/27/2018 02:32 AM, Tejun Heo wrote: > Hello, > > On Tue, Apr 24, 2018 at 02:12:51PM +0200, Paolo Valente wrote: >> +Tejun (I guess he might be interested in the results below) > > Our experiments didn't work out too well either. At this point, it > isn't clear whether i

Re: [PATCH 1/3] thermal: armada_thermal: Replace mdelay with usleep_range in armada370_init_sensor

Hey Jia-Ju, On Tue, Apr 10, 2018 at 04:13:02PM +0800, Jia-Ju Bai wrote: > armada370_init_sensor() is never called in atomic context. > > armada370_init_sensor() is set as ".init_sensor" in > struct armada_thermal_data. > ".init_sensor" is called armada_thermal_probe(). > armada_thermal_probe() i

Re: moving affs + RDB partition support to staging? (was: Re: Moving unmaintained filesystems to staging)

Hi Geert, test results at https://bugzilla.kernel.org/show_bug.cgi?id=43511 indicate the RDB parser bug is fixed by the patch given there, so if Martin now submits the patch, all should be well? (MSDOS partition support is not the only one with limitations - the SGI partition parser also uses int

Re: [PATCH 2/3] thermal: armada_thermal: Replace mdelay with msleep in armada375_init_sensor

On Tue, Apr 10, 2018 at 04:13:16PM +0800, Jia-Ju Bai wrote: > armada375_init_sensor() is never called in atomic context. > > armada375_init_sensor() is set as ".init_sensor" in > struct armada_thermal_data. > ".init_sensor" is called armada_thermal_probe(). > armada_thermal_probe() is set as ".pro

RE: [PATCH 4/5] ARM: dts: imx6sx-sabreauto: add fec support

Anson Huang Best Regards! > -Original Message- > From: Anson Huang > Sent: Friday, April 27, 2018 9:37 AM > To: 'Fabio Estevam' > Cc: Shawn Guo ; Sascha Hauer > ; Fabio Estevam ; Rob > Herring ; Mark Rutland ; > dl-linux-imx ; moderated list:ARM/FREESCALE IMX / MXC > ARM ARCHITECTURE ;

Re: [PATCH] dt-bindings: staging: remove a couple of ADC bindings

On Thu, Apr 26, 2018 at 2:42 PM, Thomas Petazzoni wrote: > Hello, > > On Thu, 26 Apr 2018 11:02:55 +0530, Viresh Kumar wrote: >> @Thomas: Do you guys use this ? >> >> On 25-04-18, 20:57, Rob Herring wrote: >> > Remove LPC32xx and SPEAr ADC bindings in staging. They have not been >> > touched since

Re: [PATCH 3/3] thermal: armada_thermal: Replace mdelay with usleep_range in armada380_init_sensor

On Tue, Apr 10, 2018 at 04:13:28PM +0800, Jia-Ju Bai wrote: > armada380_init_sensor() is never called in atomic context. > > armada380_init_sensor() is set as ".init_sensor" in > struct armada_thermal_data. > ".init_sensor" is called armada_thermal_probe(). > armada_thermal_probe() is set as ".pro

Re: [PATCH v2] of: overlay: Stop leaking resources on overlay removal

On Thu, Apr 26, 2018 at 01:00:30PM +0200, Jan Kiszka wrote: > Only the overlay notifier callbacks have a chance to potentially get > hold of references to those two resources, but they are not supposed to > store them beyond OF_OVERLAY_POST_REMOVE. > > Document the overlay notifier API, its constr

RE: [PATCH] USB: serial: option: adding support for ublox R410M

> > Option is likely the right driver for this device. > > qcaux was mainly for mobile phones that have a TTY (often cdc-acm) as the > modem port > and a secondary DIAG/DM port driven by qcaux. The DM port doesn't have an > interrupt > endpoint thus it's not a normal modem port requiring the

Re: [PATCH RFC PoC 0/2] platform: different approach to early platform drivers

On 04/26/2018 12:31 PM, Rich Felker wrote: On Thu, Apr 26, 2018 at 05:29:18PM +0200, Bartosz Golaszewski wrote: From: Bartosz Golaszewski This is a follow to my series[1] the aim of which was to introduce device tree support for early platform devices. It was received rather negatively. Aside

[PATCH v1 4/4] mhi_bus: dev: uci: add user space interface driver

This module allows user space clients to transfer data between external modem and host using standard file operations. Signed-off-by: Sujeev Dias --- drivers/bus/mhi/devices/Kconfig | 9 + drivers/bus/mhi/devices/Makefile | 1 + drivers/bus/mhi/devices/mhi_uci.c | 662

[PATCH v1 3/4] mhi_bus: dev: netdev: add network interface driver

MHI based net device driver is used for transferring IP traffic between host and modem. Driver allows clients to transfer data using standard network interface. Signed-off-by: Sujeev Dias --- Documentation/devicetree/bindings/bus/mhi.txt | 36 ++ drivers/bus/Kconfig |

<    1   2   3   4   5   6   7   8   9   10   >