Hi,
On Wed, Jul 12, 2017 at 10:38:38AM +0800, Chen-Yu Tsai wrote:
> On Wed, Jul 12, 2017 at 3:31 AM, Maxime Ripard
> wrote:
> > On Mon, Jul 10, 2017 at 11:48:00PM +0800, Chen-Yu Tsai wrote:
> >> On Sun, Jun 18, 2017 at 10:05 PM, Rob Herring wrote:
> >> > On Wed, Jun 14, 2017 at 02:30:16PM +0800,
On Wed, Jul 12, 2017 at 3:31 AM, Maxime Ripard
wrote:
> On Mon, Jul 10, 2017 at 11:48:00PM +0800, Chen-Yu Tsai wrote:
>> On Sun, Jun 18, 2017 at 10:05 PM, Rob Herring wrote:
>> > On Wed, Jun 14, 2017 at 02:30:16PM +0800, Chen-Yu Tsai wrote:
>> >> The explanation for the endpoint ID numbering sche
On Mon, Jul 10, 2017 at 11:48:00PM +0800, Chen-Yu Tsai wrote:
> On Sun, Jun 18, 2017 at 10:05 PM, Rob Herring wrote:
> > On Wed, Jun 14, 2017 at 02:30:16PM +0800, Chen-Yu Tsai wrote:
> >> The explanation for the endpoint ID numbering scheme is convoluted
> >> and hard to understand.
> >>
> >> This
On Sun, Jun 18, 2017 at 10:05 PM, Rob Herring wrote:
> On Wed, Jun 14, 2017 at 02:30:16PM +0800, Chen-Yu Tsai wrote:
>> The explanation for the endpoint ID numbering scheme is convoluted
>> and hard to understand.
>>
>> This patch aims to improve the readability of it by combining the
>> existing
On Wed, Jun 14, 2017 at 02:30:16PM +0800, Chen-Yu Tsai wrote:
> The explanation for the endpoint ID numbering scheme is convoluted
> and hard to understand.
>
> This patch aims to improve the readability of it by combining the
> existing two paragraphs, while also providing a diagram example,
> an
The explanation for the endpoint ID numbering scheme is convoluted
and hard to understand.
This patch aims to improve the readability of it by combining the
existing two paragraphs, while also providing a diagram example,
and how endpoints should be numbered based on that example.
Signed-off-by:
