All of lore.kernel.org
 help / color / mirror / Atom feed
From: thomas.petazzoni@free-electrons.com (Thomas Petazzoni)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2] AT91 OHCI active-high vbus and overcurrent handling
Date: Wed, 13 Jul 2011 11:29:15 +0200	[thread overview]
Message-ID: <1310549358-13330-1-git-send-email-thomas.petazzoni@free-electrons.com> (raw)

Hello,

This series of patches adds two features to the AT91 OHCI driver :
 * Support for active-high vbus pin USB power switches (patch 1)
 * Support for over-current notification (patches 2 and 3)

Changes since v1 (posted July, 5th 2011) :

 * Simplify expressions in gpio_direction_output() when controlling
   the VBUS pin, as suggested by Sergei Shtylyov
   <sshtylyov@mvista.com>

 * Extend the overcurrent notification support by notifying the USB
   stack and exposing the fact that per-port power switching and
   overcurrent notification, based on ohci-da8xx.c and ohci-s3c2410.c,
   as suggested by Matthieu CASTET <matthieu.castet@parrot.com>

I haven't yet taken into account Jean-Christophe Plagniol-Villard
comment on using the named ressources, because I don't see how a board
file can define ressources with the current AT91 code structure (the
ressources are only defined at the SoC level). Input from
Jean-Christophe on this would be greatly appreciated.

Regards,

Thomas

             reply	other threads:[~2011-07-13  9:29 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-13  9:29 Thomas Petazzoni [this message]
2011-07-13  9:29 ` [PATCH 1/3] ohci-at91: add vbus_pin_inverted platform attribute Thomas Petazzoni
2011-09-07 10:47   ` Nicolas Ferre
2011-07-13  9:29 ` [PATCH 2/3] at91-ohci: support overcurrent notification Thomas Petazzoni
2011-07-13 14:28   ` Thomas Petazzoni
2011-07-13 15:54     ` Alan Stern
2011-07-13 16:43       ` Thomas Petazzoni
2011-07-13 17:17         ` Alan Stern
2011-09-07 10:47   ` Nicolas Ferre
2011-07-13  9:29 ` [PATCH 3/3] at91-ohci: configure overcurrent pins as input GPIOs Thomas Petazzoni
2011-09-07 10:51   ` Nicolas Ferre
2011-09-07 13:16     ` Nicolas Ferre

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1310549358-13330-1-git-send-email-thomas.petazzoni@free-electrons.com \
    --to=thomas.petazzoni@free-electrons.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.