As part of submitting the RISC-V Linux port it was suggested that we write some
documentation that describes our device tree bindings. Our port is still in
progress, but it was suggested that we start sending patches to the relevant
parties. There is one outstanding issue to resolve with the
As part of submitting the RISC-V Linux port it was suggested that we write some
documentation that describes our device tree bindings. Our port is still in
progress, but it was suggested that we start sending patches to the relevant
parties. There is one outstanding issue to resolve with the
On Tue, 23 May 2017 05:03:17 PDT (-0700), Arnd Bergmann wrote:
> On Tue, May 23, 2017 at 2:41 AM, Palmer Dabbelt wrote:
>> ---
>> .../interrupt-controller/riscv,cpu-intc.txt| 46
>> ++
>> .../bindings/interrupt-controller/riscv,plic0.txt | 44
>>
On Tue, 23 May 2017 05:03:17 PDT (-0700), Arnd Bergmann wrote:
> On Tue, May 23, 2017 at 2:41 AM, Palmer Dabbelt wrote:
>> ---
>> .../interrupt-controller/riscv,cpu-intc.txt| 46
>> ++
>> .../bindings/interrupt-controller/riscv,plic0.txt | 44
>>
On Tue, May 23, 2017 at 2:41 AM, Palmer Dabbelt wrote:
> ---
> .../interrupt-controller/riscv,cpu-intc.txt| 46
> ++
> .../bindings/interrupt-controller/riscv,plic0.txt | 44 +
The patch needs a description, and should be sent
On Tue, May 23, 2017 at 2:41 AM, Palmer Dabbelt wrote:
> ---
> .../interrupt-controller/riscv,cpu-intc.txt| 46
> ++
> .../bindings/interrupt-controller/riscv,plic0.txt | 44 +
The patch needs a description, and should be sent to the irqchip
---
.../interrupt-controller/riscv,cpu-intc.txt| 46 ++
.../bindings/interrupt-controller/riscv,plic0.txt | 44 +
2 files changed, 90 insertions(+)
create mode 100644
Documentation/devicetree/bindings/interrupt-controller/riscv,cpu-intc.txt
---
.../interrupt-controller/riscv,cpu-intc.txt| 46 ++
.../bindings/interrupt-controller/riscv,plic0.txt | 44 +
2 files changed, 90 insertions(+)
create mode 100644
Documentation/devicetree/bindings/interrupt-controller/riscv,cpu-intc.txt
8 matches
Mail list logo