mirror of https://lore.kernel.org/linux-amlogic/
 help / color / mirror / Atom feed
From: afaerber@suse.de (Andreas Färber)
To: linus-amlogic@lists.infradead.org
Subject: S805/S812 Device Tree upstreaming (was: Testing.)
Date: Mon, 8 May 2017 13:47:19 +0200	[thread overview]
Message-ID: <26a939cb-ae9c-36ec-fbc7-8735c3826862@suse.de> (raw)
In-Reply-To: <cdb8ce4a-a3a9-f999-67b1-ddb712df250c@yandex.ru>

Hi,

Am 08.05.2017 um 11:42 schrieb Oleg:
>> I had a quick look at the .dts files - on my Akaso M8S GPIOZ_1 is not
>> connected anywhere (at least toggling the GPIO doesn't change anything
>> in terms of USB VBUS signal).
>> however, your board has: gpio-vbus-power = "GPIOZ_1";
>> it's very likely that the GL852 hub is powered off by default and is
>> powered on by enabling GPIOZ_1
>> but since my .dts is not enabling GPIOZ_1 the hub stays powered off
>> and USB is not working for you
>> (in other words: this will require additional changes in the .dts to
>> make it work)
> I found dtb to kernel 3.14 the string
> 
> gpio-vbus-power = "GPIOZ_1";
> 
> You can simply copy it to the unit or it needs to change according to
> certain rules ?

You need to read the latest bindings documentation, for example:

https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/tree/Documentation/devicetree/bindings

Regards,
Andreas

-- 
SUSE Linux GmbH, Maxfeldstr. 5, 90409 N?rnberg, Germany
GF: Felix Imend?rffer, Jane Smithard, Graham Norton
HRB 21284 (AG N?rnberg)

  reply	other threads:[~2017-05-08 11:47 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-05-02  6:37 Testing Oleg
2017-05-07 16:38 ` Testing Martin Blumenstingl
2017-05-07 17:36   ` Testing Oleg
2017-05-07 18:05     ` Testing Martin Blumenstingl
2017-05-07 18:55       ` Testing Oleg
     [not found]       ` <e7eb7d12-8fa8-5507-5d7b-53ef9ce3e300@yandex.ru>
2017-05-07 18:59         ` Testing Martin Blumenstingl
2017-05-07 19:09           ` Testing Oleg
2017-05-07 20:22             ` Testing Martin Blumenstingl
2017-05-07 20:44               ` Testing Oleg
2017-05-07 20:46                 ` Testing Martin Blumenstingl
2017-05-07 20:53                   ` Testing Oleg
2017-05-07 20:57                   ` Testing Oleg
2017-05-07 21:08                     ` Testing Martin Blumenstingl
2017-05-07 21:23                       ` Testing Oleg
2017-05-07 21:30                         ` Testing Martin Blumenstingl
2017-05-08  9:42                           ` Testing Oleg
2017-05-08 11:47                             ` Andreas Färber [this message]
2017-05-12  7:03   ` Testing Oleg
2017-05-25 18:35   ` Testing Tobias Baumann
2017-05-27 14:15     ` Testing Martin Blumenstingl
2017-05-27 14:57       ` Testing raptorsds
2017-05-27 16:08         ` Testing Martin Blumenstingl
2017-05-27 18:06           ` Testing raptorsds
2017-05-27 18:18             ` Testing Martin Blumenstingl
2017-05-08 20:10 S805/S812 Device Tree upstreaming (was: Testing.) Martin Blumenstingl
2017-05-09 13:14 ` Oleg
2017-05-11  9:54 ` Oleg
2017-05-13  9:03   ` Martin Blumenstingl
2017-05-13 19:25     ` Oleg
2017-05-14 21:07 Martin Blumenstingl
2017-05-15 12:12 ` Oleg
2017-05-15 14:45   ` Oleg
2017-05-15 20:29     ` Martin Blumenstingl
2017-05-16  9:05       ` Oleg
2017-05-20 16:59         ` Martin Blumenstingl

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=26a939cb-ae9c-36ec-fbc7-8735c3826862@suse.de \
    --to=afaerber@suse.de \
    --cc=linus-amlogic@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

all inboxes | Powered by JetHome®