01 Jul, 2020

2 commits

  • The kerneldoc tooling/parsers/validators get confused if non-
    standard formatting is used. The first line after the kerneldoc
    identifier '/**' must not be blank else the following warnings
    will be issued:

    drivers/misc/pti.c:902: warning: Cannot understand *
    on line 902 - I thought it was a doc line

    Cc: J Freyensee
    Signed-off-by: Lee Jones
    Link: https://lore.kernel.org/r/20200701085853.164358-3-lee.jones@linaro.org
    Signed-off-by: Greg Kroah-Hartman

    Lee Jones
     
  • W=1 kernel builds report a lack of descriptions for various
    function arguments. In reality they are documented, but the
    formatting was not as expected '@.*:'. Instead, '-'s were
    used as separators.

    This change fixes the following warnings:

    drivers/misc/pti.c:748: warning: Function parameter or member 'port' not described in 'pti_port_activate'
    drivers/misc/pti.c:748: warning: Function parameter or member 'tty' not described in 'pti_port_activate'
    drivers/misc/pti.c:765: warning: Function parameter or member 'port' not described in 'pti_port_shutdown'
    drivers/misc/pti.c:793: warning: Function parameter or member 'pdev' not described in 'pti_pci_probe'
    drivers/misc/pti.c:793: warning: Function parameter or member 'ent' not described in 'pti_pci_probe'

    Cc: J Freyensee
    Signed-off-by: Lee Jones
    Link: https://lore.kernel.org/r/20200701085853.164358-2-lee.jones@linaro.org
    Signed-off-by: Greg Kroah-Hartman

    Lee Jones
     

30 Jun, 2020

1 commit

  • The API has moved on since the original function header was
    authored. This changes brings the function's documentation
    back into line with reality, complete descriptions of the
    latest arguments to be used.

    Squashes the following W=1 kernel build warnings:

    drivers/misc/pti.c:510: warning: Function parameter or member 'tty' not described in 'pti_tty_driver_wr
    drivers/misc/pti.c:510: warning: Function parameter or member 'buf' not described in 'pti_tty_driver_wr
    drivers/misc/pti.c:510: warning: Excess function parameter 'filp' description in 'pti_tty_driver_write'
    drivers/misc/pti.c:510: warning: Excess function parameter 'data' description in 'pti_tty_driver_write'

    Cc: J Freyensee
    Acked-by: Arnd Bergmann
    Signed-off-by: Lee Jones
    Link: https://lore.kernel.org/r/20200626130525.389469-11-lee.jones@linaro.org
    Signed-off-by: Greg Kroah-Hartman

    Lee Jones
     

30 Jan, 2020

1 commit

  • Pull char/misc driver updates from Greg KH:
    "Here is the big char/misc/whatever driver changes for 5.6-rc1

    Included in here are loads of things from a variety of different
    driver subsystems:
    - soundwire updates
    - binder updates
    - nvmem updates
    - firmware drivers updates
    - extcon driver updates
    - various misc driver updates
    - fpga driver updates
    - interconnect subsystem and driver updates
    - bus driver updates
    - uio driver updates
    - mei driver updates
    - w1 driver cleanups
    - various other small driver updates

    All of these have been in linux-next for a while with no reported
    issues"

    * tag 'char-misc-5.6-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc: (86 commits)
    mei: me: add jasper point DID
    char: hpet: Use flexible-array member
    binder: fix log spam for existing debugfs file creation.
    mei: me: add comet point (lake) H device ids
    nvmem: add QTI SDAM driver
    dt-bindings: nvmem: add binding for QTI SPMI SDAM
    dt-bindings: imx-ocotp: Add i.MX8MP compatible
    dt-bindings: soundwire: fix example
    soundwire: cadence: fix kernel-doc parameter descriptions
    soundwire: intel: report slave_ids for each link to SOF driver
    siox: Use the correct style for SPDX License Identifier
    w1: omap-hdq: Simplify driver with PM runtime autosuspend
    firmware: stratix10-svc: Remove unneeded semicolon
    firmware: google: Probe for a GSMI handler in firmware
    firmware: google: Unregister driver_info on failure and exit in gsmi
    firmware: google: Release devices before unregistering the bus
    slimbus: qcom: add missed clk_disable_unprepare in remove
    slimbus: Use the correct style for SPDX License Identifier
    slimbus: qcom-ngd-ctrl: Use dma_request_chan() instead dma_request_slave_channel()
    dt-bindings: SLIMBus: add slim devices optional properties
    ...

    Linus Torvalds
     

14 Jan, 2020

1 commit

  • The variable retval is assigned with a value that is never read and
    it is re-assigned a new value later on. The assignment is redundant
    and can be removed. Clean up multiple occurrances of this pattern.

    Addresses-Coverity: ("Unused value")
    Signed-off-by: Colin Ian King
    Link: https://lore.kernel.org/r/20191222222224.732340-1-colin.king@canonical.com
    Signed-off-by: Greg Kroah-Hartman

    Colin Ian King
     

06 Jan, 2020

1 commit


31 May, 2019

1 commit

  • Based on 1 normalized pattern(s):

    this program is free software you can redistribute it and or modify
    it under the terms of the gnu general public license version 2 as
    published by the free software foundation this program is
    distributed in the hope that it will be useful but without any
    warranty without even the implied warranty of merchantability or
    fitness for a particular purpose see the gnu general public license
    for more details

    extracted by the scancode license scanner the SPDX license identifier

    GPL-2.0-only

    has been chosen to replace the boilerplate/reference in 655 file(s).

    Signed-off-by: Thomas Gleixner
    Reviewed-by: Allison Randal
    Reviewed-by: Kate Stewart
    Reviewed-by: Richard Fontana
    Cc: linux-spdx@vger.kernel.org
    Link: https://lkml.kernel.org/r/20190527070034.575739538@linutronix.de
    Signed-off-by: Greg Kroah-Hartman

    Thomas Gleixner
     

17 Dec, 2017

1 commit


27 Sep, 2013

1 commit


12 Dec, 2012

1 commit

  • Pull TTY/Serial merge from Greg Kroah-Hartman:
    "Here's the big tty/serial tree set of changes for 3.8-rc1.

    Contained in here is a bunch more reworks of the tty port layer from
    Jiri and bugfixes from Alan, along with a number of other tty and
    serial driver updates by the various driver authors.

    Also, Jiri has been coerced^Wconvinced to be the co-maintainer of the
    TTY layer, which is much appreciated by me.

    All of these have been in the linux-next tree for a while.

    Signed-off-by: Greg Kroah-Hartman "

    Fixed up some trivial conflicts in the staging tree, due to the fwserial
    driver having come in both ways (but fixed up a bit in the serial tree),
    and the ioctl handling in the dgrp driver having been done slightly
    differently (staging tree got that one right, and removed both
    TIOCGSOFTCAR and TIOCSSOFTCAR).

    * tag 'tty-3.8-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty: (146 commits)
    staging: sb105x: fix potential NULL pointer dereference in mp_chars_in_buffer()
    staging/fwserial: Remove superfluous free
    staging/fwserial: Use WARN_ONCE when port table is corrupted
    staging/fwserial: Destruct embedded tty_port on teardown
    staging/fwserial: Fix build breakage when !CONFIG_BUG
    staging: fwserial: Add TTY-over-Firewire serial driver
    drivers/tty/serial/serial_core.c: clean up HIGH_BITS_OFFSET usage
    staging: dgrp: dgrp_tty.c: Audit the return values of get/put_user()
    staging: dgrp: dgrp_tty.c: Remove the TIOCSSOFTCAR ioctl handler from dgrp driver
    serial: ifx6x60: Add modem power off function in the platform reboot process
    serial: mxs-auart: unmap the scatter list before we copy the data
    serial: mxs-auart: disable the Receive Timeout Interrupt when DMA is enabled
    serial: max310x: Setup missing "can_sleep" field for GPIO
    tty/serial: fix ifx6x60.c declaration warning
    serial: samsung: add devicetree properties for non-Exynos SoCs
    serial: samsung: fix potential soft lockup during uart write
    tty: vt: Remove redundant null check before kfree.
    tty/8250 Add check for pci_ioremap_bar failure
    tty/8250 Add support for Commtech's Fastcom Async-335 and Fastcom Async-PCIe cards
    tty/8250 Add XR17D15x devices to the exar_handle_irq override
    ...

    Linus Torvalds
     

22 Nov, 2012

4 commits


16 Nov, 2012

1 commit

  • After commit "TTY: move tty buffers to tty_port", the tty buffers are
    not freed in some drivers. This is because tty_port_destructor is not
    called whenever a tty_port is freed. This was an assumption I counted
    with but was unfortunately untrue. So fix the drivers to fulfil this
    assumption.

    To be sure, the TTY buffers (and later some stuff) are gone along with
    the tty_port, we have to call tty_port_destroy at tear-down places.
    This is mostly where the structure containing a tty_port is freed.
    This patch does exactly that -- put tty_port_destroy at those places.

    Signed-off-by: Jiri Slaby
    Signed-off-by: Greg Kroah-Hartman

    Jiri Slaby
     

11 Aug, 2012

8 commits

  • So now we have enough of tty_ports, so we can signal the TTY layer to
    use them by tty_port_register_device.

    The upside is that we look like we can introduce tty_port_easy_open
    and put it directly as tty_operations->open to drivers doing nothing
    in open and using tty_port_register_device. Because the easy open can
    obtain a tty_port rather easily from a tty now. Heh, what a nice
    by-product.

    Signed-off-by: Jiri Slaby
    Cc: J Freyensee
    Signed-off-by: Greg Kroah-Hartman

    Jiri Slaby
     
  • We now have *one* tty_port for both TTYs. How this was supposed to
    work? Change it to have a tty_port for each of TTYs.

    Signed-off-by: Jiri Slaby
    Cc: J Freyensee
    Signed-off-by: Greg Kroah-Hartman

    Jiri Slaby
     
  • Fail paths in ->probe and pti_init are incomplete. Fix that by adding
    proper clean-up paths.

    Note that we used to leak tty_driver on module unload. This is fixed
    here too.

    tty_unregister_driver needs not retval checking, so remove that.

    Signed-off-by: Jiri Slaby
    Cc: J Freyensee
    Signed-off-by: Greg Kroah-Hartman

    Jiri Slaby
     
  • Currently, probe initializes some parts. Then, some of them are
    unwound in ->remove, some in module_exit. Let us do the opposite of
    whole ->probe in ->remove.

    Signed-off-by: Jiri Slaby
    Cc: J Freyensee
    Signed-off-by: Greg Kroah-Hartman

    Jiri Slaby
     
  • The function is lost somewhere in the forest. Move it to have it along
    with probe and other pci_driver stuff.

    Signed-off-by: Jiri Slaby
    Cc: J Freyensee
    Signed-off-by: Greg Kroah-Hartman

    Jiri Slaby
     
  • Ioremap space is different to iomap. ->probe function uses ioremap,
    but ->remove calls pci_iounmap. That one is illegal. Fix that by using
    iounmap.

    Signed-off-by: Jiri Slaby
    Cc: J Freyensee
    Signed-off-by: Greg Kroah-Hartman

    Jiri Slaby
     
  • As we set drvdata unconditionally in ->probe, we need not check if it
    is NULL. Let us remove the check.

    Signed-off-by: Jiri Slaby
    Cc: J Freyensee
    Signed-off-by: Greg Kroah-Hartman

    Jiri Slaby
     
  • It is annotated as __devinitconst. Despite the annotation is useless
    in most cases, const keyword is misssing there. So we are placing
    non-const data into rodata section. Fix that now.

    Signed-off-by: Jiri Slaby
    Cc: J Freyensee
    Signed-off-by: Greg Kroah-Hartman

    Jiri Slaby
     

19 Apr, 2012

1 commit

  • Drivers that refer to a __devexit function in an operations
    structure need to annotate that pointer with __devexit_p so it
    is replaced with a NULL pointer when the section gets discarded.

    Signed-off-by: Arnd Bergmann
    Signed-off-by: Mathieu Poirier
    Signed-off-by: Greg Kroah-Hartman

    Arnd Bergmann
     

09 Mar, 2012

2 commits

  • All num, magic and owner are set by alloc_tty_driver. No need to
    re-set them on each allocation site.

    pti driver sets something different to what it passes to
    alloc_tty_driver. It is not a bug, since we don't use the lines
    parameter in any way. Anyway this is fixed, and now we do the right
    thing.

    Signed-off-by: Jiri Slaby
    Acked-by: Tilman Schmidt
    Signed-off-by: Greg Kroah-Hartman

    Jiri Slaby
     
  • It was added back in 2004 and never used for anything real. Remove the
    only assignment in the tree as well.

    Signed-off-by: Jiri Slaby
    Signed-off-by: Greg Kroah-Hartman

    Jiri Slaby
     

03 Feb, 2012

1 commit


15 Sep, 2011

1 commit

  • In drivers/misc/pti.c::pti_control_frame_built_and_sent() we assign 'comm'
    to 'thread_name_p' if (!thread_name). The problem is that 'comm' then
    goes out of scope and later we use 'thread_name_p' which now refers to an
    out-of-scope variable. To fix that, simply move 'comm' up to have
    function scope.

    Signed-off-by: Jesper Juhl
    Cc: Greg Kroah-Hartman
    Cc: J Freyensee
    Cc: Jeremy Rocher
    Cc: Sergei Trofimovich
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Jesper Juhl
     

26 Aug, 2011

1 commit

  • Found on allmodconfig build (ARCH=alpha)

    drivers/misc/pti.c: In function 'get_id':
    drivers/misc/pti.c:249: error: implicit declaration of function 'kmalloc'
    drivers/misc/pti.c: In function 'pti_char_write':
    drivers/misc/pti.c:658: error: implicit declaration of function 'copy_from_user'

    Signed-off-by: Sergei Trofimovich
    Cc: Greg Kroah-Hartman
    Cc: J Freyensee
    Cc: Jeremy Rocher
    Signed-off-by: Andrew Morton
    Signed-off-by: Linus Torvalds

    Sergei Trofimovich
     

26 Jul, 2011

2 commits

  • * 'tty-next' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/tty-2.6: (26 commits)
    amba pl011: workaround for uart registers lockup
    n_gsm: fix the wrong FCS handling
    pch_uart: add missing comment about OKI ML7223
    pch_uart: Add MSI support
    tty: fix "IRQ45: nobody cared"
    PTI feature to allow user to name and mark masterchannel request.
    0 for o PTI Makefile bug.
    tty: serial: samsung.c remove legacy PM code.
    SERIAL: SC26xx: Fix link error.
    serial: mrst_max3110: initialize waitqueue earlier
    mrst_max3110: Change max missing message priority.
    tty: s5pv210: Add delay loop on fifo reset function for UART
    tty/serial: Fix XSCALE serial ports, e.g. ce4100
    serial: bfin_5xx: fix off-by-one with resource size
    drivers/tty: use printk_ratelimited() instead of printk_ratelimit()
    tty: n_gsm: Added refcount usage to gsm_mux and gsm_dlci structs
    tty: n_gsm: Add raw-ip support
    tty: n_gsm: expose gsmtty device nodes at ldisc open time
    pch_phub: Fix register miss-setting issue
    serial: 8250, increase PASS_LIMIT
    ...

    Linus Torvalds
     
  • …/gregkh/driver-core-2.6

    * 'driver-core-next' of git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/driver-core-2.6:
    updated Documentation/ja_JP/SubmittingPatches
    debugfs: add documentation for debugfs_create_x64
    uio: uio_pdrv_genirq: Add OF support
    firmware: gsmi: remove sysfs entries when unload the module
    Documentation/zh_CN: Fix messy code file email-clients.txt
    driver core: add more help description for "path to uevent helper"
    driver-core: modify FIRMWARE_IN_KERNEL help message
    driver-core: Kconfig grammar corrections in firmware configuration
    DOCUMENTATION: Replace create_device() with device_create().
    DOCUMENTATION: Update overview.txt in Doc/driver-model.
    pti: pti_tty_install documentation mispelling.

    Linus Torvalds
     

02 Jul, 2011

1 commit

  • This feature addition provides a new parameter in
    pti_request_masterchannel() to allow the user
    to provide their own name to mark the request when
    the trace is viewed in a PTI SW trace viewer
    (like MPTA). If a name is not provided and
    NULL is provided, the 'current' process name is used.
    API function header documentation documents this.

    Signed-off-by: Jeremy Rocher
    Signed-off-by: J Freyensee
    Signed-off-by: Greg Kroah-Hartman

    J Freyensee
     

08 Jun, 2011

4 commits


14 May, 2011

1 commit

  • The PTI (Parallel Trace Interface) driver directs
    trace data routed from various parts in the system out
    through an Intel Penwell PTI port and out of the mobile
    device for analysis with a debugging tool (Lauterbach or Fido).
    Though n_tracesink and n_tracerouter line discipline drivers
    are used to extract modem tracing data to the PTI driver
    and other parts of an Intel mobile solution, the PTI driver
    can be used independent of n_tracesink and n_tracerouter.

    You should select this driver if the target kernel is meant for
    an Intel Atom (non-netbook) mobile device containing a MIPI
    P1149.7 standard implementation.

    Signed-off-by: J Freyensee
    Signed-off-by: Greg Kroah-Hartman

    J Freyensee