From: Eric Anholt <eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org>
To: Stefan Wahren <stefan.wahren-eS4NqCHxEME@public.gmane.org>,
linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org,
Lubomir Rintel <lkundrak-NGH9Lh4a5iE@public.gmane.org>
Cc: noralf-L59+Z2yzLopAfugRpC6u6w@public.gmane.org,
devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] ARM: bcm2835: dt: Add Raspberry Pi Zero
Date: Wed, 20 Jul 2016 14:30:34 -0700 [thread overview]
Message-ID: <87a8hct2th.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <182687649.301236.37df541a-c292-4f81-b3d7-fcea47416b49.open-xchange-7tX72C7vayboQLBSYMtkGA@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 1282 bytes --]
Stefan Wahren <stefan.wahren-eS4NqCHxEME@public.gmane.org> writes:
> Hi Eric,
>
>> Eric Anholt <eric-WhKQ6XTQaPysTnJN9+BGXg@public.gmane.org> hat am 20. Juli 2016 um 21:36 geschrieben:
>>
>>
>> Stefan Wahren <stefan.wahren-eS4NqCHxEME@public.gmane.org> writes:
>>
>> > Hi Lubomir,
>> >
>> >> Lubomir Rintel <lkundrak-NGH9Lh4a5iE@public.gmane.org> hat am 4. Februar 2016 um 08:39
>> >> geschrieben:
>> >>
>> >>
>> >> Notable difference from the other Raspberry Pi boards is the lack of PWR
>> >> LED.
>> >>
>> >> Signed-off-by: Lubomir Rintel <lkundrak-NGH9Lh4a5iE@public.gmane.org>
>> >
>> > do you have any plans to submit a V2 of this patch or should i take over?
>>
>> It's been a while, so I'd love if you picked it up and resubmitted with
>> the LED changes.
>
> i also want to take care of those dwc2 warnings, which might need some
> additional DT settings:
>
> dwc2 20980000.usb: 256 invalid for host_nperio_tx_fifo_size. Check HW
> configuration.
> dwc2 20980000.usb: 512 invalid for host_perio_tx_fifo_size. Check HW
> configuration.
> dwc2 20980000.usb: Specified GNPTXFDEP=1024 > 32
>
> What LED change do you expect?
Sorry, misremembering the thread. I think it was just the bindings
documentation change that was needed.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
prev parent reply other threads:[~2016-07-20 21:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-04 7:39 [PATCH] ARM: bcm2835: dt: Add Raspberry Pi Zero Lubomir Rintel
[not found] ` <1454571546-25481-1-git-send-email-lkundrak-NGH9Lh4a5iE@public.gmane.org>
2016-02-04 8:49 ` Noralf Trønnes
2016-02-07 10:33 ` Stefan Wahren
[not found] ` <841429508.164723.e944b9b3-11a0-4dc4-8c6d-62cb30e79b12.open-xchange-7tX72C7vayboQLBSYMtkGA@public.gmane.org>
2016-02-18 3:02 ` Eric Anholt
2016-07-19 18:30 ` Stefan Wahren
[not found] ` <27632472.326220.2e5ba31c-16b8-46a6-a38b-8aa5236ec996.open-xchange-7tX72C7vayboQLBSYMtkGA@public.gmane.org>
2016-07-20 19:36 ` Eric Anholt
[not found] ` <878tww6r0v.fsf-omZaPlIz5HhaEpDpdNBo/KxOck334EZe@public.gmane.org>
2016-07-20 21:12 ` Stefan Wahren
[not found] ` <182687649.301236.37df541a-c292-4f81-b3d7-fcea47416b49.open-xchange-7tX72C7vayboQLBSYMtkGA@public.gmane.org>
2016-07-20 21:30 ` Eric Anholt [this message]
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=87a8hct2th.fsf@eliezer.anholt.net \
--to=eric-whkq6xtqapystnjn9+bgxg@public.gmane.org \
--cc=devicetree-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-rpi-kernel-IAPFreCvJWM7uuMidbF8XUB+6BGkLq7r@public.gmane.org \
--cc=lkundrak-NGH9Lh4a5iE@public.gmane.org \
--cc=noralf-L59+Z2yzLopAfugRpC6u6w@public.gmane.org \
--cc=stefan.wahren-eS4NqCHxEME@public.gmane.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).