All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Grazvydas Ignotas <notasas@gmail.com>
Cc: linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] ARM: omap: pandora: fix usbhs platform data
Date: Mon, 5 Mar 2012 11:42:15 -0800	[thread overview]
Message-ID: <20120305194215.GN12083@atomide.com> (raw)
In-Reply-To: <1329604985-24740-1-git-send-email-notasas@gmail.com>

* Grazvydas Ignotas <notasas@gmail.com> [120218 14:11]:
> It turned out wrong OMAP HSUSB port was configured on pandora,
> but still managed to work somehow. This was noticed after enabling
> in-kernel mux, where USB muxing was causing other devices not to work,
> because hsusb1 pins (instead of hsusb2) were wrongly remuxed, which
> are used for other things on pandora.

Thanks, adding this to fixes-non-critical-part2.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] ARM: omap: pandora: fix usbhs platform data
Date: Mon, 5 Mar 2012 11:42:15 -0800	[thread overview]
Message-ID: <20120305194215.GN12083@atomide.com> (raw)
In-Reply-To: <1329604985-24740-1-git-send-email-notasas@gmail.com>

* Grazvydas Ignotas <notasas@gmail.com> [120218 14:11]:
> It turned out wrong OMAP HSUSB port was configured on pandora,
> but still managed to work somehow. This was noticed after enabling
> in-kernel mux, where USB muxing was causing other devices not to work,
> because hsusb1 pins (instead of hsusb2) were wrongly remuxed, which
> are used for other things on pandora.

Thanks, adding this to fixes-non-critical-part2.

Regards,

Tony

  reply	other threads:[~2012-03-05 19:42 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-18 22:43 [PATCH] ARM: omap: pandora: fix usbhs platform data Grazvydas Ignotas
2012-02-18 22:43 ` Grazvydas Ignotas
2012-03-05 19:42 ` Tony Lindgren [this message]
2012-03-05 19:42   ` Tony Lindgren

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=20120305194215.GN12083@atomide.com \
    --to=tony@atomide.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=notasas@gmail.com \
    /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.