21 Apr, 2017

1 commit


02 Mar, 2017

1 commit


25 Feb, 2017

1 commit

  • ->fault(), ->page_mkwrite(), and ->pfn_mkwrite() calls do not need to
    take a vma and vmf parameter when the vma already resides in vmf.

    Remove the vma parameter to simplify things.

    [arnd@arndb.de: fix ARM build]
    Link: http://lkml.kernel.org/r/20170125223558.1451224-1-arnd@arndb.de
    Link: http://lkml.kernel.org/r/148521301778.19116.10840599906674778980.stgit@djiang5-desk3.ch.intel.com
    Signed-off-by: Dave Jiang
    Signed-off-by: Arnd Bergmann
    Reviewed-by: Ross Zwisler
    Cc: Theodore Ts'o
    Cc: Darrick J. Wong
    Cc: Matthew Wilcox
    Cc: Dave Hansen
    Cc: Christoph Hellwig
    Cc: Jan Kara
    Cc: Dan Williams
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Dave Jiang
     

21 Oct, 2016

1 commit

  • firewire-net:
    - set min/max_mtu
    - remove fwnet_change_mtu

    nes:
    - set max_mtu
    - clean up nes_netdev_change_mtu

    xpnet:
    - set min/max_mtu
    - remove xpnet_dev_change_mtu

    hippi:
    - set min/max_mtu
    - remove hippi_change_mtu

    batman-adv:
    - set max_mtu
    - remove batadv_interface_change_mtu
    - initialization is a little async, not 100% certain that max_mtu is set
    in the optimal place, don't have hardware to test with

    rionet:
    - set min/max_mtu
    - remove rionet_change_mtu

    slip:
    - set min/max_mtu
    - streamline sl_change_mtu

    um/net_kern:
    - remove pointless ndo_change_mtu

    hsi/clients/ssi_protocol:
    - use core MTU range checking
    - remove now redundant ssip_pn_set_mtu

    ipoib:
    - set a default max MTU value
    - Note: ipoib's actual max MTU can vary, depending on if the device is in
    connected mode or not, so we'll just set the max_mtu value to the max
    possible, and let the ndo_change_mtu function continue to validate any new
    MTU change requests with checks for CM or not. Note that ipoib has no
    min_mtu set, and thus, the network core's mtu > 0 check is the only lower
    bounds here.

    mptlan:
    - use net core MTU range checking
    - remove now redundant mpt_lan_change_mtu

    fddi:
    - min_mtu = 21, max_mtu = 4470
    - remove now redundant fddi_change_mtu (including export)

    fjes:
    - min_mtu = 8192, max_mtu = 65536
    - The max_mtu value is actually one over IP_MAX_MTU here, but the idea is to
    get past the core net MTU range checks so fjes_change_mtu can validate a
    new MTU against what it supports (see fjes_support_mtu in fjes_hw.c)

    hsr:
    - min_mtu = 0 (calls ether_setup, max_mtu is 1500)

    f_phonet:
    - min_mtu = 6, max_mtu = 65541

    u_ether:
    - min_mtu = 14, max_mtu = 15412

    phonet/pep-gprs:
    - min_mtu = 576, max_mtu = 65530
    - remove redundant gprs_set_mtu

    CC: netdev@vger.kernel.org
    CC: linux-rdma@vger.kernel.org
    CC: Stefan Richter
    CC: Faisal Latif
    CC: linux-rdma@vger.kernel.org
    CC: Cliff Whickman
    CC: Robin Holt
    CC: Jes Sorensen
    CC: Marek Lindner
    CC: Simon Wunderlich
    CC: Antonio Quartulli
    CC: Sathya Prakash
    CC: Chaitra P B
    CC: Suganath Prabu Subramani
    CC: MPT-FusionLinux.pdl@broadcom.com
    CC: Sebastian Reichel
    CC: Felipe Balbi
    CC: Arvid Brodin
    CC: Remi Denis-Courmont
    Signed-off-by: Jarod Wilson
    Signed-off-by: David S. Miller

    Jarod Wilson
     

28 Jun, 2016

19 commits


15 Jun, 2016

1 commit


10 Jun, 2016

1 commit

  • Release &hi->lock before calling `cs_hsi_control_read_error' to avoid deadlock.

    The bug was found using EBA (https://github.com/models-team/eba), which reported
    the following:

    Double lock
    first at drivers/hsi/clients/cmt_speech.c:443
    second at drivers/hsi/clients/cmt_speech.c:447
    In cs_hsi_read_on_control_complete defined at drivers/hsi/clients/cmt_speech.c:438:
    (!) drivers/hsi/clients/cmt_speech.c:443: spin_lock(& hi->lock);
    (?) drivers/hsi/clients/cmt_speech.c:445: msg->status == 4 -> true
    (!) drivers/hsi/clients/cmt_speech.c:447: cs_hsi_control_read_error(hi, msg);
    (!) drivers/hsi/clients/cmt_speech.c:407: __cs_hsi_error_pre(hi, msg, "control read",
    & hi->control_state);
    (!) drivers/hsi/clients/cmt_speech.c:382: spin_lock(& hi->lock);

    Signed-off-by: Iago Abal
    Signed-off-by: Sebastian Reichel

    Iago Abal
     

30 May, 2016

2 commits


10 May, 2016

3 commits

  • After the clk change support, the ssi omap ssi core driver
    now calls into the port driver to change fclk. This function
    was previously inside of an #ifdef, because it was only used
    when CONFIG_PM is enabled. Now it also gets used without
    power management support:

    drivers/hsi/built-in.o: In function `ssi_clk_event':
    omap_ssi_port.c:(.text+0x1bf8): undefined reference to `omap_ssi_port_update_fclk'

    This moves the function outside of the CONFIG_PM guard.

    Signed-off-by: Arnd Bergmann
    Fixes: 4bcf7414528a ("HSI: omap-ssi: add clk change support")
    Signed-off-by: Sebastian Reichel

    Arnd Bergmann
     
  • The driver now uses some pinctrl functions, but fails
    to build if PINCTRL is disabled because the respective
    header files are only included indirectly:

    drivers/hsi/controllers/omap_ssi_core.c: In function 'ssi_clk_event':
    drivers/hsi/controllers/omap_ssi_core.c:317:4: error: implicit declaration of function 'pinctrl_pm_select_idle_state' [-Werror=implicit-function-declaration]
    drivers/hsi/controllers/omap_ssi_core.c:339:4: error: implicit declaration of function 'pinctrl_pm_select_default_state' [-Werror=implicit-function-declaration]
    drivers/hsi/controllers/omap_ssi_port.c: In function 'ssi_flush':
    drivers/hsi/controllers/omap_ssi_port.c:520:2: error: implicit declaration of function 'pinctrl_pm_select_idle_state' [-Werror=implicit-function-declaration]

    This includes the headers from the files that call the functions,
    which works even if pinctrl is turned off.

    Signed-off-by: Arnd Bergmann
    Fixes: 4bcf7414528a ("HSI: omap-ssi: add clk change support")
    Signed-off-by: Sebastian Reichel

    Arnd Bergmann
     
  • Enabling the omap ssi driver without COMMON_CLK results in a build failure:

    drivers/hsi/controllers/omap_ssi_core.c: In function 'ssi_clk_event':
    drivers/hsi/controllers/omap_ssi_core.c:304:7: error: 'PRE_RATE_CHANGE' undeclared (first use in this function)

    This adds a Kconfig dependency to avoid the invalid configuration.

    Signed-off-by: Arnd Bergmann
    Fixes: 4bcf7414528a ("HSI: omap-ssi: add clk change support")
    Signed-off-by: Sebastian Reichel

    Arnd Bergmann
     

03 May, 2016

6 commits


29 Jan, 2016

2 commits

  • When using the ssi-protocol driver with the Nokia N950, the
    following error is thrown during modem powered up sequence.

    [13852.274993] port0: SSI error: 0x01
    [13852.279205] ssi-protocol ssi-protocol: RX error detected
    [13852.284820] ssi-protocol ssi-protocol: Main state: 1
    [13852.290069] ssi-protocol ssi-protocol: Recv state: 0
    [13852.295288] ssi-protocol ssi-protocol: Send state: 0
    [13852.300537] ssi-protocol ssi-protocol: CMT Offline
    [13852.305603] ssi-protocol ssi-protocol: Wake test 1
    [13852.310638] ssi-protocol ssi-protocol: Data RX id: 0
    [13852.315887] ssi-protocol ssi-protocol: Data TX id: 0
    [13856.001464] ssi-protocol ssi-protocol: Watchdog trigerred
    [13856.007293] ssi-protocol ssi-protocol: Main state: 1
    [13856.012542] ssi-protocol ssi-protocol: Recv state: 0
    [13856.017761] ssi-protocol ssi-protocol: Send state: 0
    [13856.023010] ssi-protocol ssi-protocol: CMT Offline
    [13856.028045] ssi-protocol ssi-protocol: Wake test 0
    [13856.033111] ssi-protocol ssi-protocol: Data RX id: 0
    [13856.038330] ssi-protocol ssi-protocol: Data TX id: 0

    This patch fixes the issue by using the handshake setup from
    the Nokia N950 kernel. The new handshake sequence also works
    with the N900, so there is no need to differentiate between
    both modems.

    Tested-by: Aaro Koskinen
    Signed-off-by: Sebastian Reichel

    Sebastian Reichel
     
  • The Nokia N950 and Nokia N9 also have a SSI connected
    modem, which use the same protocols as the Nokia N900,
    but with increased link speed (96000 kbps instead of
    55000 kbps) and with less GPIOs.

    Since it's unclear, if the N950 and the N9 use exactly
    the same modem, each of them gets their own compatible
    string.

    Acked-by: Rob Herring
    Tested-by: Aaro Koskinen
    Signed-off-by: Sebastian Reichel

    Sebastian Reichel
     

07 Jan, 2016

2 commits