On Thu, Nov 8, 2018 at 9:27 AM Arnd Bergmann wrote:
>
> We do the same thing on PCI and USB, where normally everything
> is probed through hardware access, but a device driver can look
> at dev->of_node to see if that contains any further properties.
>
This is very interesting. Spent some time tr
On Thu, Nov 8, 2018 at 3:21 PM Sven Van Asbroeck wrote:
>
> Hi Arnd, thank you for the review and the feedback !
>
> >
> > To allow describing connected devices, I think we need a #address-cells
> > and #size-cells property here, with fixed values.
>
> I'm not sure I understand. Connected devices
Hi Arnd, thank you for the review and the feedback !
>
> To allow describing connected devices, I think we need a #address-cells
> and #size-cells property here, with fixed values.
I'm not sure I understand. Connected devices aren't described in the
devicetree. The anybus specification defines an
On Sun, Nov 4, 2018 at 4:55 PM wrote:
> ---
> .../bindings/bus/arcx,anybuss-host.txt| 36 +++
> 1 file changed, 36 insertions(+)
> create mode 100644
> Documentation/devicetree/bindings/bus/arcx,anybuss-host.txt
>
> diff --git a/Documentation/devicetree/bindings/bus/ar
From: Sven Van Asbroeck
This patch adds devicetree binding documentation for the
Arcx Anybus-S host.
Signed-off-by: Sven Van Asbroeck
---
.../bindings/bus/arcx,anybuss-host.txt| 36 +++
1 file changed, 36 insertions(+)
create mode 100644 Documentation/devicetree/bindin
5 matches
Mail list logo
