linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: hdegoede@redhat.com (Hans de Goede)
To: linux-arm-kernel@lists.infradead.org
Subject: [linux-sunxi] Re: [PATCH 5/5] ARM: sun5i: Add C.H.I.P DTS
Date: Tue, 22 Sep 2015 15:01:58 +0200	[thread overview]
Message-ID: <56015146.2070509@redhat.com> (raw)
In-Reply-To: <CAGb2v662+mhFgv1DXz5muA+xGE99R1DVKOxtVPvJmc+tRFPXzQ@mail.gmail.com>

Hi,

On 22-09-15 14:57, Chen-Yu Tsai wrote:
> On Tue, Sep 22, 2015 at 8:47 PM, Maxime Ripard
> <maxime.ripard@free-electrons.com> wrote:

<snip>

>>>> +&usb_otg {
>>>> +       dr_mode = "otg";
>>>> +       status = "okay";
>>>> +};
>>>> +
>>>> +&usbphy {
>>>> +       pinctrl-names = "default";
>>>> +       pinctrl-0 = <&chip_id_det_pin>;
>>>> +       status = "okay";
>>>> +
>>>> +       usb0_id_det-gpio = <&pio 6 2 GPIO_ACTIVE_HIGH>; /* PG2 */
>>>
>>> Better leave a comment here saying VBUS detection requires AXP209
>>> usb-power-supply support.
>>
>> Does it? It can be powered by a battery, with or without VBUS, and
>> that wouldn't be tied to the fact that the power-supply is USB or
>> something else.
>
> The AXP209 VBUS / USB power-supply also doubles for VBUS detection,
> which on most boards is done using a separate GPIO pin. Hans posted
> support for the AXP20X power-supply driver, and support in the usb
> phy driver using it for VBUS detection.

Ack.

> In short, this is not about "power supply" but VBUS detection. IIRC,
> if no VBUS detection method is provided, the phy driver just waits a
> period of time after an ID pin change and then considers VBUS invalid.

Right, but that is a hack for boards with no / broken vbus detection
(or vbus control), we really want to use vbus-det where available,
so I agree that a TODO comment here would be good.

Regards,

Hans

  reply	other threads:[~2015-09-22 13:01 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-18  8:48 [PATCH 0/5] ARM: sunxi: Introduce CHIP support Maxime Ripard
2015-09-18  8:48 ` [PATCH 1/5] ARM: sunxi: Add R8 support Maxime Ripard
2015-09-18  9:47   ` Chen-Yu Tsai
2015-09-18 12:20     ` Maxime Ripard
2015-09-30 22:38   ` Stephen Boyd
2015-10-01  6:58     ` Maxime Ripard
2015-09-18  8:48 ` [PATCH 2/5] ARM: sun5i: Add R8 DTSI Maxime Ripard
2015-09-18  9:41   ` Chen-Yu Tsai
2015-09-18 12:19     ` Maxime Ripard
2015-09-18  8:48 ` [PATCH 3/5] ARM: sun5i: dt: Move uart3 pinctrl node to common DTSI Maxime Ripard
2015-09-18  8:48 ` [PATCH 4/5] ARM: sun5i: dt: Add UART3 CTS and RTS pins Maxime Ripard
2015-09-18  8:48 ` [PATCH 5/5] ARM: sun5i: Add C.H.I.P DTS Maxime Ripard
2015-09-18 16:41   ` Chen-Yu Tsai
2015-09-22 12:47     ` Maxime Ripard
2015-09-22 12:57       ` [linux-sunxi] " Chen-Yu Tsai
2015-09-22 13:01         ` Hans de Goede [this message]
2015-09-22 13:34           ` Hans de Goede
2015-09-22 14:04           ` Maxime Ripard
2015-09-22 14:30             ` Hans de Goede
2015-09-29 19:36               ` Maxime Ripard
2015-09-18  9:02 ` [PATCH 0/5] ARM: sunxi: Introduce CHIP support Arnd Bergmann
2015-09-18 12:19   ` Maxime Ripard
2015-09-18 13:18     ` Arnd Bergmann
2015-09-18 13:55       ` Maxime Ripard
2015-09-18 13:58         ` Arnd Bergmann
2015-09-18 15:36 ` [linux-sunxi] " Hans de Goede

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=56015146.2070509@redhat.com \
    --to=hdegoede@redhat.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;
as well as URLs for NNTP newsgroup(s).