28 Jun, 2016

1 commit


22 Nov, 2015

1 commit

  • The kernel-doc how to says that structure fields that are inside a
    "private:" area shouldn't be listed in the generated documentation
    but the private fields for struct hsi_client private are listed.

    This also fixes the following make htmldocs warnings:

    .//include/linux/hsi/hsi.h:150: warning: Excess struct/union/enum/typedef member 'e_handler' description in 'hsi_client'
    .//include/linux/hsi/hsi.h:150: warning: Excess struct/union/enum/typedef member 'pclaimed' description in 'hsi_client'
    .//include/linux/hsi/hsi.h:150: warning: Excess struct/union/enum/typedef member 'nb' description in 'hsi_client'

    Signed-off-by: Javier Martinez Canillas
    Signed-off-by: Sebastian Reichel

    Javier Martinez Canillas
     

28 Feb, 2015

1 commit


16 May, 2014

5 commits


19 Feb, 2014

1 commit


02 Mar, 2013

1 commit

  • Fix kernel-doc warnings in hsi files:

    Warning(include/linux/hsi/hsi.h:136): Excess struct/union/enum/typedef member 'e_handler' description in 'hsi_client'
    Warning(include/linux/hsi/hsi.h:136): Excess struct/union/enum/typedef member 'pclaimed' description in 'hsi_client'
    Warning(include/linux/hsi/hsi.h:136): Excess struct/union/enum/typedef member 'nb' description in 'hsi_client'
    Warning(drivers/hsi/hsi.c:434): No description found for parameter 'handler'
    Warning(drivers/hsi/hsi.c:434): Excess function parameter 'cb' description in 'hsi_register_port_event'

    Don't document "private:" fields with kernel-doc notation.
    If you want to leave them fully documented, that's OK, but
    then don't mark them as "private:".

    Signed-off-by: Randy Dunlap
    Cc: Carlos Chinea
    Cc: Linus Walleij
    Cc: Greg Kroah-Hartman
    Cc: linux-kernel@vger.kernel.org
    Cc: linux-omap@vger.kernel.org
    Acked-by: Nishanth Menon
    Signed-off-by: Linus Torvalds

    Randy Dunlap
     

03 Jan, 2013

1 commit


09 Oct, 2012

1 commit


23 Apr, 2012

2 commits

  • Remove custom hack and make use of the notifier chain interfaces for
    delivering events from the ports to their associated clients.
    Clients that want to receive port events need to register their callbacks
    using hsi_register_port_event(). The callbacks can be called in interrupt
    context. Use hsi_unregestier_port_event() to undo the registration.

    Signed-off-by: Carlos Chinea
    Acked-by: Greg Kroah-Hartman
    Acked-by: Linus Walleij

    Carlos Chinea
     
  • Use the proper release mechanism for hsi_controller and
    hsi_ports structures. Free the structures through their
    associated device release callbacks.

    Signed-off-by: Carlos Chinea
    Acked-by: Greg Kroah-Hartman
    Acked-by: Linus Walleij

    Carlos Chinea
     

05 Jan, 2012

3 commits