public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: John.Youn@synopsys.com (John Youn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH V2 RFC 6/6] ARM: dts: bcm2835: Add Raspberry Pi Zero
Date: Thu, 18 Aug 2016 12:34:27 -0700	[thread overview]
Message-ID: <e40cdc61-16ea-c86d-0039-7c24a123c058@synopsys.com> (raw)
In-Reply-To: <1882785986.365355.5a20a815-9153-4587-9aeb-f2a7fc5a4ff5.open-xchange@email.1und1.de>

On 8/18/2016 12:04 PM, Stefan Wahren wrote:
> Hi John,
> 
>> John Youn <John.Youn@synopsys.com> hat am 18. August 2016 um 20:03
>> geschrieben:
>>
>>
>> On 8/17/2016 3:17 PM, Stefan Wahren wrote:
>>> Hi John,
>>>
>>>> John Youn <John.Youn@synopsys.com> hat am 17. August 2016 um 23:21
>>>> geschrieben:
>>>>
>>>>
>>>> ...
>>>> Ok, yeah, that seems better.
>>>>
>>>> Can you check if applying just patch 2 and 3 solves the issue? If so I
>>>> think we can send those upstream.
>>>
>>> unfortunately not:
>>
>> Ok. I'll see if I can come up with a more conservative version of
>> patch 4 until I can look at it properly. I'll try to get to this
>> sometime next week but I may not be able to get to it until later.
> 
> Great
> 
>>
>> In the meantime, specifying the fifo sizes as you've done can serve as
>> a workaround.
> 
> Beside of this workaround, do you see any benefit of patch 2/6 from my series?
> 
> I don't want to introduce DT properties which are only useful for workarounds?

Does everything work fine if you don't set any parameters, and use my
patches from before? If so, and if you're willing to wait for the fix
to those patches then I don't see a need for it.

They would be useful beyond a workaround, if only for our internal
test platform, but we don't need it right away.

Regards,
John

  reply	other threads:[~2016-08-18 19:34 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 [this message]
2016-08-18 18:14 ` [PATCH V2 RFC 0/6] " Eric Anholt
2016-08-18 18:57   ` 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=e40cdc61-16ea-c86d-0039-7c24a123c058@synopsys.com \
    --to=john.youn@synopsys.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