linux-kernel - Re: [PATCH anybus v1 2/4] dt-bindings: anybus-bridge: document devicetree binding.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite for Android: free password hash cracker in your pocket

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <CACRpkdaprWOr9rpsanLNZUHouWKJDkWAC1si+80zFp423eA3SQ@mail.gmail.com>
Date:   Fri, 26 Oct 2018 13:28:39 +0200
From:   Linus Walleij <linus.walleij@...aro.org>
To:     thesven73@...il.com
Cc:     svendev@...x.com, Lee Jones <lee.jones@...aro.org>,
        Rob Herring <robh+dt@...nel.org>,
        Mark Rutland <mark.rutland@....com>,
        Andreas Färber <afaerber@...e.de>,
        Thierry Reding <treding@...dia.com>,
        David Lechner <david@...hnology.com>,
        Noralf Trønnes <noralf@...nnes.org>,
        Johan Hovold <johan@...nel.org>,
        Michal Simek <monstr@...str.eu>, michal.vokac@...ft.com,
        Arnd Bergmann <arnd@...db.de>,
        Greg KH <gregkh@...uxfoundation.org>, john.garry@...wei.com,
        Geert Uytterhoeven <geert+renesas@...der.be>,
        Robin Murphy <robin.murphy@....com>,
        Paul Gortmaker <paul.gortmaker@...driver.com>,
        Sebastien Bourdelin <sebastien.bourdelin@...oirfairelinux.com>,
        Icenowy Zheng <icenowy@...c.io>, yuanzhichang@...ilicon.com,
        Stuart Yoder <stuyoder@...il.com>,
        Maxime Ripard <maxime.ripard@...tlin.com>,
        bogdan.purcareata@....com,
        "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
        "open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS" 
        <devicetree@...r.kernel.org>
Subject: Re: [PATCH anybus v1 2/4] dt-bindings: anybus-bridge: document
 devicetree binding.

On Thu, Oct 25, 2018 at 3:55 PM <thesven73@...il.com> wrote:

> >> +               fsl,weim-cs-timing = <0x024400b1 0x00001010 0x20081100
> >> +                               0x00000000 0xa0000240 0x00000000>;
> >
> > Is it just a copy/paste from
> > Documentation/devicetree/bindings/bus/imx-weim.txt
> > leftover?
>
> No. We attach the bridge to the i.MX WEIM bus. Every fdt WEIM child node
> requires a fsl,weim-cs-timing property, which provides the bus timing for
> that particular chip select. It's the weim driver that requires this,
> I'm only following its instructions.
>
> Should I just leave this out in the example? In theory, the bridge can be
> connected to any parallel bus, so fsl,weim-cs-timing is Too Much Information
> for the example?

No it's fine, I understand it now.

Whay you can do is write before the example that this example node
is using the WEIM bindings and reference that binding document.

Yours,
Linus Walleij