On 12/10/2013 01:09 AM, Kumar Gala wrote:
>
> On Nov 26, 2013, at 10:27 AM, Grygorii Strashko
> wrote:
>
>> On 11/22/2013 11:04 PM, Kumar Gala wrote:
>>>
>>> On Nov 20, 2013, at 9:46 AM, Ivan Khoronzhuk wrote:
>>>
Add bindings for AEMIF controller drivers/memory/ti-aemif.c
>>>
>>>
On 12/10/2013 01:09 AM, Kumar Gala wrote:
On Nov 26, 2013, at 10:27 AM, Grygorii Strashko grygorii.stras...@ti.com
wrote:
On 11/22/2013 11:04 PM, Kumar Gala wrote:
On Nov 20, 2013, at 9:46 AM, Ivan Khoronzhuk ivan.khoronz...@ti.com wrote:
Add bindings for AEMIF controller
On Nov 26, 2013, at 10:27 AM, Grygorii Strashko
wrote:
> On 11/22/2013 11:04 PM, Kumar Gala wrote:
>>
>> On Nov 20, 2013, at 9:46 AM, Ivan Khoronzhuk wrote:
>>
>>> Add bindings for AEMIF controller drivers/memory/ti-aemif.c
>>>
>>
>> Binding shouldn’t normally refer to code.
>>
>> Just
Kumar,
On Tuesday 26 November 2013 11:27 AM, Grygorii Strashko wrote:
> On 11/22/2013 11:04 PM, Kumar Gala wrote:
>>
>> On Nov 20, 2013, at 9:46 AM, Ivan Khoronzhuk wrote:
>>
>>> Add bindings for AEMIF controller drivers/memory/ti-aemif.c
>>>
>>
>> Binding shouldn’t normally refer to code.
>>
>>
Kumar,
On Tuesday 26 November 2013 11:27 AM, Grygorii Strashko wrote:
On 11/22/2013 11:04 PM, Kumar Gala wrote:
On Nov 20, 2013, at 9:46 AM, Ivan Khoronzhuk ivan.khoronz...@ti.com wrote:
Add bindings for AEMIF controller drivers/memory/ti-aemif.c
Binding shouldn’t normally refer to code.
On Nov 26, 2013, at 10:27 AM, Grygorii Strashko grygorii.stras...@ti.com
wrote:
On 11/22/2013 11:04 PM, Kumar Gala wrote:
On Nov 20, 2013, at 9:46 AM, Ivan Khoronzhuk ivan.khoronz...@ti.com wrote:
Add bindings for AEMIF controller drivers/memory/ti-aemif.c
Binding shouldn’t normally
On 11/29/2013 05:10 PM, Santosh Shilimkar wrote:
On Friday 29 November 2013 10:00 AM, Grygorii Strashko wrote:
Hi Kumar Gala,
On 11/22/2013 11:06 PM, Kumar Gala wrote:
On Nov 20, 2013, at 1:03 PM, ivan.khoronzhuk wrote:
On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
+
On 11/29/2013 05:10 PM, Santosh Shilimkar wrote:
On Friday 29 November 2013 10:00 AM, Grygorii Strashko wrote:
Hi Kumar Gala,
On 11/22/2013 11:06 PM, Kumar Gala wrote:
On Nov 20, 2013, at 1:03 PM, ivan.khoronzhuk ivan.khoronz...@ti.com wrote:
On 11/20/2013 08:21 PM, Jean-Christophe
On Friday 29 November 2013 10:00 AM, Grygorii Strashko wrote:
> Hi Kumar Gala,
>
> On 11/22/2013 11:06 PM, Kumar Gala wrote:
>>
>> On Nov 20, 2013, at 1:03 PM, ivan.khoronzhuk wrote:
>>
>>> On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> + the chip
On Friday 29 November 2013 09:56 AM, Grygorii Strashko wrote:
> Hi Jean-Christophe,
>
> On 11/22/2013 08:42 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
>> On 21:03 Wed 20 Nov , ivan.khoronzhuk wrote:
>>> On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> +
Hi Kumar Gala,
On 11/22/2013 11:06 PM, Kumar Gala wrote:
>
> On Nov 20, 2013, at 1:03 PM, ivan.khoronzhuk wrote:
>
>> On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
+ the chip select signal.
+ Minimum value is 1 (0
Hi Jean-Christophe,
On 11/22/2013 08:42 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 21:03 Wed 20 Nov , ivan.khoronzhuk wrote:
>> On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
+ the chip select signal.
+ Minimum
Hi Jean-Christophe,
On 11/22/2013 08:42 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
On 21:03 Wed 20 Nov , ivan.khoronzhuk wrote:
On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
+ the chip select signal.
+ Minimum value is 1
Hi Kumar Gala,
On 11/22/2013 11:06 PM, Kumar Gala wrote:
On Nov 20, 2013, at 1:03 PM, ivan.khoronzhuk ivan.khoronz...@ti.com wrote:
On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
+ the chip select signal.
+ Minimum value
On Friday 29 November 2013 09:56 AM, Grygorii Strashko wrote:
Hi Jean-Christophe,
On 11/22/2013 08:42 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
On 21:03 Wed 20 Nov , ivan.khoronzhuk wrote:
On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
+ the
On Friday 29 November 2013 10:00 AM, Grygorii Strashko wrote:
Hi Kumar Gala,
On 11/22/2013 11:06 PM, Kumar Gala wrote:
On Nov 20, 2013, at 1:03 PM, ivan.khoronzhuk ivan.khoronz...@ti.com wrote:
On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
+ the
On 11/22/2013 11:06 PM, Kumar Gala wrote:
On Nov 20, 2013, at 1:03 PM, ivan.khoronzhuk wrote:
On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
+ the chip select signal.
+ Minimum value is 1 (0 treated as 1).
+
+-
On 11/22/2013 11:04 PM, Kumar Gala wrote:
On Nov 20, 2013, at 9:46 AM, Ivan Khoronzhuk wrote:
Add bindings for AEMIF controller drivers/memory/ti-aemif.c
Binding shouldn’t normally refer to code.
Just saying something like:
Adding binging for TI Async External Memory Interface (AEMIF)
On 11/22/2013 11:04 PM, Kumar Gala wrote:
>
> On Nov 20, 2013, at 9:46 AM, Ivan Khoronzhuk wrote:
>
>> Add bindings for AEMIF controller drivers/memory/ti-aemif.c
>>
>
> Binding shouldn’t normally refer to code.
>
> Just saying something like:
>
> Adding binging for TI Async External Memory
On 11/22/2013 11:04 PM, Kumar Gala wrote:
On Nov 20, 2013, at 9:46 AM, Ivan Khoronzhuk ivan.khoronz...@ti.com wrote:
Add bindings for AEMIF controller drivers/memory/ti-aemif.c
Binding shouldn’t normally refer to code.
Just saying something like:
Adding binging for TI Async
On 11/22/2013 11:04 PM, Kumar Gala wrote:
On Nov 20, 2013, at 9:46 AM, Ivan Khoronzhuk ivan.khoronz...@ti.com wrote:
Add bindings for AEMIF controller drivers/memory/ti-aemif.c
Binding shouldn’t normally refer to code.
Just saying something like:
Adding binging for TI Async External
On 11/22/2013 11:06 PM, Kumar Gala wrote:
On Nov 20, 2013, at 1:03 PM, ivan.khoronzhuk ivan.khoronz...@ti.com wrote:
On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
+ the chip select signal.
+ Minimum value is 1 (0
On Nov 20, 2013, at 1:03 PM, ivan.khoronzhuk wrote:
> On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
>>> + the chip select signal.
>>> + Minimum value is 1 (0 treated as 1).
>>> +
>>> +- ti,cs-wsetup:write setup
On Nov 20, 2013, at 9:46 AM, Ivan Khoronzhuk wrote:
> Add bindings for AEMIF controller drivers/memory/ti-aemif.c
>
Binding shouldn’t normally refer to code.
Just saying something like:
Adding binging for TI Async External Memory Interface (AEMIF) controller.
> Signed-off-by: Ivan
On 21:03 Wed 20 Nov , ivan.khoronzhuk wrote:
> On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> >> + the chip select signal.
> >> + Minimum value is 1 (0 treated as 1).
> >> +
> >> +- ti,cs-wsetup: write setup width,
On 21:03 Wed 20 Nov , ivan.khoronzhuk wrote:
On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
+ the chip select signal.
+ Minimum value is 1 (0 treated as 1).
+
+- ti,cs-wsetup: write setup width, ns
+
On Nov 20, 2013, at 9:46 AM, Ivan Khoronzhuk ivan.khoronz...@ti.com wrote:
Add bindings for AEMIF controller drivers/memory/ti-aemif.c
Binding shouldn’t normally refer to code.
Just saying something like:
Adding binging for TI Async External Memory Interface (AEMIF) controller.
On Nov 20, 2013, at 1:03 PM, ivan.khoronzhuk ivan.khoronz...@ti.com wrote:
On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
+ the chip select signal.
+ Minimum value is 1 (0 treated as 1).
+
+- ti,cs-wsetup:write
On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
>> +the chip select signal.
>> +Minimum value is 1 (0 treated as 1).
>> +
>> +- ti,cs-wsetup: write setup width, ns
>> +Time between the
> + the chip select signal.
> + Minimum value is 1 (0 treated as 1).
> +
> +- ti,cs-wsetup: write setup width, ns
> + Time between the beginning of a memory cycle
> + and
Add bindings for AEMIF controller drivers/memory/ti-aemif.c
Signed-off-by: Ivan Khoronzhuk
---
.../bindings/memory-controllers/ti-aemif.txt | 198
1 file changed, 198 insertions(+)
create mode 100644
Documentation/devicetree/bindings/memory-controllers/ti-aemif.txt
Add bindings for AEMIF controller drivers/memory/ti-aemif.c
Signed-off-by: Ivan Khoronzhuk ivan.khoronz...@ti.com
---
.../bindings/memory-controllers/ti-aemif.txt | 198
1 file changed, 198 insertions(+)
create mode 100644
+ the chip select signal.
+ Minimum value is 1 (0 treated as 1).
+
+- ti,cs-wsetup: write setup width, ns
+ Time between the beginning of a memory cycle
+ and the
On 11/20/2013 08:21 PM, Jean-Christophe PLAGNIOL-VILLARD wrote:
+the chip select signal.
+Minimum value is 1 (0 treated as 1).
+
+- ti,cs-wsetup: write setup width, ns
+Time between the beginning
34 matches
Mail list logo