27 May, 2020

1 commit


16 May, 2020

1 commit


22 Apr, 2020

1 commit


10 Apr, 2020

1 commit


09 Apr, 2020

2 commits


31 Mar, 2020

2 commits


26 Mar, 2020

1 commit


18 Mar, 2020

2 commits


14 Mar, 2020

1 commit


12 Mar, 2020

2 commits


08 Mar, 2020

1 commit

  • Merge Linux stable release v5.4.24 into imx_5.4.y

    * tag 'v5.4.24': (3306 commits)
    Linux 5.4.24
    blktrace: Protect q->blk_trace with RCU
    kvm: nVMX: VMWRITE checks unsupported field before read-only field
    ...

    Signed-off-by: Jason Liu

    Conflicts:
    arch/arm/boot/dts/imx6sll-evk.dts
    arch/arm/boot/dts/imx7ulp.dtsi
    arch/arm64/boot/dts/freescale/fsl-ls1028a.dtsi
    drivers/clk/imx/clk-composite-8m.c
    drivers/gpio/gpio-mxc.c
    drivers/irqchip/Kconfig
    drivers/mmc/host/sdhci-of-esdhc.c
    drivers/mtd/nand/raw/gpmi-nand/gpmi-nand.c
    drivers/net/can/flexcan.c
    drivers/net/ethernet/freescale/dpaa/dpaa_eth.c
    drivers/net/ethernet/mscc/ocelot.c
    drivers/net/ethernet/stmicro/stmmac/stmmac_main.c
    drivers/net/ethernet/stmicro/stmmac/stmmac_platform.c
    drivers/net/phy/realtek.c
    drivers/pci/controller/mobiveil/pcie-mobiveil-host.c
    drivers/perf/fsl_imx8_ddr_perf.c
    drivers/tee/optee/shm_pool.c
    drivers/usb/cdns3/gadget.c
    kernel/sched/cpufreq.c
    net/core/xdp.c
    sound/soc/fsl/fsl_esai.c
    sound/soc/fsl/fsl_sai.c
    sound/soc/sof/core.c
    sound/soc/sof/imx/Kconfig
    sound/soc/sof/loader.c

    Jason Liu
     

05 Mar, 2020

2 commits

  • commit 78e06cf430934fc3768c342cbebdd1013dcd6fa7 upstream.

    In the flowtable documentation there is a missing semicolon, the command
    as is would give this error:

    nftables.conf:5:27-33: Error: syntax error, unexpected devices, expecting newline or semicolon
    hook ingress priority 0 devices = { br0, pppoe-data };
    ^^^^^^^
    nftables.conf:4:12-13: Error: invalid hook (null)
    flowtable ft {
    ^^

    Fixes: 19b351f16fd9 ("netfilter: add flowtable documentation")
    Signed-off-by: Matteo Croce
    Signed-off-by: Pablo Neira Ayuso
    Signed-off-by: Greg Kroah-Hartman

    Matteo Croce
     
  • commit fcbb8461fd2376ba3782b5b8bd440c929b8e4980 upstream.

    There are both positive and negative options about this feature.
    At first, I thought it was a good idea, but actually Linus stated a
    negative opinion (https://lkml.org/lkml/2019/9/29/227). I admit it
    is ugly and annoying.

    The baseline I'd like to keep is the compile-test of uapi headers.
    (Otherwise, kernel developers have no way to ensure the correctness
    of the exported headers.)

    I will maintain a small build rule in usr/include/Makefile.
    Remove the other header test functionality.

    Signed-off-by: Masahiro Yamada
    [ added to 5.4.y due to start of build warnings from backported patches
    because of this feature - gregkh]
    Signed-off-by: Greg Kroah-Hartman

    Masahiro Yamada
     

04 Mar, 2020

4 commits


29 Feb, 2020

1 commit

  • commit dcde237319e626d1ec3c9d8b7613032f0fd4663a upstream.

    Currently the arm64 kernel ignores the top address byte passed to brk(),
    mmap() and mremap(). When the user is not aware of the 56-bit address
    limit or relies on the kernel to return an error, untagging such
    pointers has the potential to create address aliases in user-space.
    Passing a tagged address to munmap(), madvise() is permitted since the
    tagged pointer is expected to be inside an existing mapping.

    The current behaviour breaks the existing glibc malloc() implementation
    which relies on brk() with an address beyond 56-bit to be rejected by
    the kernel.

    Remove untagging in the above functions by partially reverting commit
    ce18d171cb73 ("mm: untag user pointers in mmap/munmap/mremap/brk"). In
    addition, update the arm64 tagged-address-abi.rst document accordingly.

    Link: https://bugzilla.redhat.com/1797052
    Fixes: ce18d171cb73 ("mm: untag user pointers in mmap/munmap/mremap/brk")
    Cc: # 5.4.x-
    Cc: Florian Weimer
    Reviewed-by: Andrew Morton
    Reported-by: Victor Stinner
    Acked-by: Will Deacon
    Acked-by: Andrey Konovalov
    Signed-off-by: Catalin Marinas
    Signed-off-by: Will Deacon
    Signed-off-by: Greg Kroah-Hartman

    Catalin Marinas
     

26 Feb, 2020

3 commits

  • Add documentation for a new clock 'phy_parent'. This clock is optional
    and is used to re-parent the PHY related clocks (phy_ref, tx_esc and
    rx_esc) to a valid parent. This clock is needed, in order to make the
    re-parenting in driver, since the default re-parenting in dts node
    (using assigned-clock-parents) may break the LVDS block, which has it's
    PHY shared with MIPI-DSI.

    Signed-off-by: Robert Chiras
    Signed-off-by: Dong Aisheng
    (cherry picked from commit 7ed3b8738e3103396a5f3a9268c66f11f78cab03)

    Robert Chiras
     
  • Some MAC PCS blocks are unable to provide interrupts when their status
    changes. As we already have support in phylink for polling status, use
    this to provide a hook for MACs to enable polling mode.

    The patch idea was picked up from Russell King's suggestion on the macb
    phylink patch thread here [0] but the implementation was changed.
    Instead of introducing a new phylink_start_poll() function, which would
    make the implementation cumbersome for common PHYLINK implementations
    for multiple types of devices, like DSA, just add a boolean property to
    the phylink_config structure, which is just as backwards-compatible.

    https://lkml.org/lkml/2019/12/16/603

    Suggested-by: Russell King
    Signed-off-by: Vladimir Oltean

    Conflicts:
    drivers/net/phy/phylink.c

    with upstream commit 24cf0e693bb5 ("net: phylink: split link_an_mode
    configured and current settings") submitted for net-next and merged
    during v5.5-rc1.

    (cherry picked from commit ac7420c5ede06ebe049c6bce8ba9e9d7d3a51d11)

    Vladimir Oltean
     
  • QORIQ LS1028A soc used fsl,vf610-edma, but it has a little bit different
    from others, so add new compatible to distinguish them.

    Signed-off-by: Peng Ma
    Link: https://lore.kernel.org/r/20191212033714.4090-3-peng.ma@nxp.com
    Signed-off-by: Vinod Koul
    (cherry picked from commit f8dd1f395d1fbba049900ed48c09d76df49be712)

    Peng Ma
     

24 Feb, 2020

1 commit

  • [ Upstream commit fd933c00ebe220060e66fb136a7050a242456566 ]

    Three shall be the number thou shalt count, and the number of the
    counting shall be three. Four shalt thou not count...

    One! Two! Five!

    Fixes: efb985f6b265 ("[PATCH] fbcon: Console Rotation - Add framebuffer console documentation")
    Signed-off-by: Peter Rosin
    Reviewed-by: Geert Uytterhoeven
    Cc: Jonathan Corbet
    Cc: Matthew Wilcox
    Signed-off-by: Bartlomiej Zolnierkiewicz
    Link: https://patchwork.freedesktop.org/patch/msgid/20190827110854.12574-2-peda@axentia.se
    Signed-off-by: Sasha Levin

    Peter Rosin
     

21 Feb, 2020

1 commit


18 Feb, 2020

2 commits


16 Feb, 2020

1 commit


15 Feb, 2020

1 commit

  • commit a6c4f77cb3b11f81077b53c4a38f21b92d41f21e upstream.

    This patch set the correct value for oversampling maxItems. In the
    original example, appears 3 items for oversampling while the maxItems
    is set to 1, this patch fixes those issues.

    Fixes: 416f882c3b40 ("dt-bindings: iio: adc: Migrate AD7606 documentation to yaml")
    Signed-off-by: Beniamin Bia
    Signed-off-by: Rob Herring
    Signed-off-by: Greg Kroah-Hartman

    Beniamin Bia
     

13 Feb, 2020

5 commits


11 Feb, 2020

2 commits


06 Feb, 2020

1 commit

  • commit 2fee1a7cc6b1ce6634bb0f025be2c94a58dfa34d upstream.

    The commit 4585fbcb5331 ("PM / devfreq: Modify the device name as devfreq(X) for
    sysfs") changed the node name to devfreq(x). After this commit, it is not
    possible to get the device name through /sys/class/devfreq/devfreq(X)/*.

    Add new name attribute in order to get device name.

    Cc: stable@vger.kernel.org
    Fixes: 4585fbcb5331 ("PM / devfreq: Modify the device name as devfreq(X) for sysfs")
    Signed-off-by: Chanwoo Choi
    Signed-off-by: Greg Kroah-Hartman

    Chanwoo Choi
     

29 Jan, 2020

1 commit

  • Add "clock" property (and corresponding "clock-names")
    for the CAAM SNVS node.

    This property is optional: there are cases when SNVS clock is kept
    always on (chips such as i.MX6 SX, UL).
    A good guide line is to check whether i.MX clk driver defines the clock.

    Signed-off-by: Horia Geantă
    Reviewed-by: Iuliana Prodan

    Horia Geantă