On 10/13/2015 02:01 PM, Rob Herring wrote:
On Tue, Oct 13, 2015 at 12:28 PM, Murali Karicheri wrote:
On 10/13/2015 10:42 AM, Rob Herring wrote:
On Mon, Oct 12, 2015 at 2:46 PM, Murali Karicheri
wrote:
Currently the DT bindings have details about the driver as well. This
patch moves this to
On Tue, Oct 13, 2015 at 12:28 PM, Murali Karicheri wrote:
> On 10/13/2015 10:42 AM, Rob Herring wrote:
>>
>> On Mon, Oct 12, 2015 at 2:46 PM, Murali Karicheri
>> wrote:
>>>
>>> Currently the DT bindings have details about the driver as well. This
>>> patch moves this to a separate document for kn
On 10/13/2015 10:42 AM, Rob Herring wrote:
On Mon, Oct 12, 2015 at 2:46 PM, Murali Karicheri wrote:
Currently the DT bindings have details about the driver as well. This
patch moves this to a separate document for knav qmss driver so that
driver detail update can be done as needed without pollu
On 10/13/2015 10:42 AM, Rob Herring wrote:
On Mon, Oct 12, 2015 at 2:46 PM, Murali Karicheri wrote:
Currently the DT bindings have details about the driver as well. This
patch moves this to a separate document for knav qmss driver so that
driver detail update can be done as needed without pollu
On Mon, Oct 12, 2015 at 2:46 PM, Murali Karicheri wrote:
> Currently the DT bindings have details about the driver as well. This
> patch moves this to a separate document for knav qmss driver so that
> driver detail update can be done as needed without polluting the DT
> bindings description.
>
>
Currently the DT bindings have details about the driver as well. This
patch moves this to a separate document for knav qmss driver so that
driver detail update can be done as needed without polluting the DT
bindings description.
Signed-off-by: Murali Karicheri
---
Documentation/arm/keystone/knav
6 matches
Mail list logo