From: eric@anholt.net (Eric Anholt)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 RFC 0/6] ARM: dts: bcm2835: Add Raspberry Pi Zero
Date: Thu, 18 Aug 2016 11:14:07 -0700 [thread overview]
Message-ID: <87lgzuj66o.fsf@eliezer.anholt.net> (raw)
In-Reply-To: <1469559213-16160-1-git-send-email-stefan.wahren@i2se.com>
Stefan Wahren <stefan.wahren@i2se.com> writes:
> This patch series is only a draft and not intended to be merged. Patches 1 and 2
> aren't bcm2835 specific and should be helpful for other platforms.
> The patches 2 - 4 are required for otg / gadget mode. The last patch
> based on the work of Lubomir Rintel [1] and Noralf Tr?nnes [2].
>
> Changes since V1:
> - rebase to current linux-next
> - add patches 1 - 4 for otg/gadget support
> - add patch 5 with model compatible
> - use polarity define for ACT LED
>
> [1] - http://lists.infradead.org/pipermail/linux-rpi-kernel/2016-February/003221.html
> [2] - https://github.com/raspberrypi/linux/pull/1239/
>
> Stefan Wahren (6):
> usb: dwc2: core: Avoid nonsense error in gadget mode
> usb: dwc2: Add DT properties to specify fifo size in host/otg mode
> ARM: dts: bcm283x: Add missing usb clock
> ARM: dts: bcm283x: Add generic USB PHY
> DT: bindings: bcm: Add Raspberry Pi Zero
> ARM: dts: bcm2835: Add Raspberry Pi Zero
Where are we at on these? I've been holding off waiting for the USB
bits to get settled. I can grab the bindings patch, but is there
anything else we could merge while you're working on USB?
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 818 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160818/2b308119/attachment.sig>
next prev parent reply other threads:[~2016-08-18 18:14 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-26 18:53 [PATCH V2 RFC 0/6] ARM: dts: bcm2835: Add Raspberry Pi Zero Stefan Wahren
2016-07-26 18:53 ` [PATCH V2 RFC 1/6] usb: dwc2: core: Avoid nonsense error in gadget mode Stefan Wahren
2016-08-16 1:30 ` John Youn
2016-08-16 16:22 ` Eric Anholt
2016-08-16 16:44 ` Stefan Wahren
2016-08-16 19:20 ` John Youn
2016-08-16 20:09 ` Stefan Wahren
2016-07-26 18:53 ` [PATCH V2 RFC 2/6] usb: dwc2: Add DT properties to specify fifo size in host/otg mode Stefan Wahren
2016-07-29 21:12 ` Rob Herring
2016-08-18 18:12 ` John Youn
2016-07-26 18:53 ` [PATCH V2 RFC 3/6] ARM: dts: bcm283x: Add missing usb clock Stefan Wahren
2016-07-26 18:53 ` [PATCH V2 RFC 4/6] ARM: dts: bcm283x: Add generic USB PHY Stefan Wahren
2016-07-26 18:53 ` [PATCH V2 RFC 5/6] DT: bindings: bcm: Add Raspberry Pi Zero Stefan Wahren
2016-07-29 21:13 ` Rob Herring
2016-07-26 18:53 ` [PATCH V2 RFC 6/6] ARM: dts: bcm2835: " Stefan Wahren
2016-08-02 17:19 ` Stephen Warren
2016-08-02 19:29 ` Stefan Wahren
2016-08-02 20:56 ` Stephen Warren
2016-08-16 19:30 ` John Youn
2016-08-16 19:58 ` Stefan Wahren
2016-08-16 22:07 ` John Youn
2016-08-17 19:11 ` Stefan Wahren
2016-08-17 21:21 ` John Youn
2016-08-17 22:17 ` Stefan Wahren
2016-08-18 18:03 ` John Youn
2016-08-18 19:04 ` Stefan Wahren
2016-08-18 19:34 ` John Youn
2016-08-18 18:14 ` Eric Anholt [this message]
2016-08-18 18:57 ` [PATCH V2 RFC 0/6] " Stefan Wahren
2016-08-19 0:37 ` Eric Anholt
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=87lgzuj66o.fsf@eliezer.anholt.net \
--to=eric@anholt.net \
--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