From: nsekhar@ti.com (Sekhar Nori)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND PATCH 2/3] ARM: davinci: hawk: Remove vbus and over current gpios
Date: Wed, 23 Nov 2016 10:42:18 +0530 [thread overview]
Message-ID: <788edcf1-e8bf-6cbf-ad46-981db6b0ded7@ti.com> (raw)
In-Reply-To: <CAKXjFTMLt0j4yfHUww6k6FMu4=Z+mhZJCKi-tqmqdaOUs0fJ9Q@mail.gmail.com>
On Tuesday 22 November 2016 09:11 PM, Axel Haslam wrote:
> Hi Sekhar
>
> On Tue, Nov 22, 2016 at 11:37 AM, Sekhar Nori <nsekhar@ti.com> wrote:
>> On Monday 21 November 2016 10:23 PM, Axel Haslam wrote:
>>> The hawk board VBUS is fixed to a 5v source, and the over
>>> current pin is actually not connected to the SoC.
>>>
>>> Do not reseve these gpios for OHCI as they are not related
>>> to usb.
>>>
>>> Signed-off-by: Axel Haslam <ahaslam@baylibre.com>
>>
>> As discussed over the MMC/SD patches, this patch should be based off the
>> hawkboard schematic, not the LCDK schematic.
>>
>
> I looked at the hawkboard schematics and they are the same
> as the lcdk as far as usb i concerned:
>
> The ohci vbus is fixed to 5v, and the over current pins of the
> TPS are not connected. so this patch should be ok for
> both the hawk and the lcdk.
Alright! Thanks for checking.
Regards,
Sekhar
next prev parent reply other threads:[~2016-11-23 5:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-21 16:53 [RESEND PATCH 0/3] ARM: davinci: OHCI: Use a regulator instead of callbacks Axel Haslam
2016-11-21 16:53 ` [RESEND PATCH 1/3] ARM: davinci: da830: Handle vbus with a regulator Axel Haslam
2016-11-22 10:35 ` Sekhar Nori
2016-11-21 16:53 ` [RESEND PATCH 2/3] ARM: davinci: hawk: Remove vbus and over current gpios Axel Haslam
2016-11-22 10:37 ` Sekhar Nori
2016-11-22 15:41 ` Axel Haslam
2016-11-23 5:12 ` Sekhar Nori [this message]
2016-11-21 16:53 ` [RESEND PATCH 3/3] ARM: davinci: remove ohci platform usage Axel Haslam
2016-11-22 10:42 ` Sekhar Nori
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=788edcf1-e8bf-6cbf-ad46-981db6b0ded7@ti.com \
--to=nsekhar@ti.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox