[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20180921185106.GJ20825@sirena.org.uk>
Date: Fri, 21 Sep 2018 11:51:06 -0700
From: Mark Brown <broonie@...nel.org>
To: Stephen Boyd <swboyd@...omium.org>
Cc: Doug Anderson <dianders@...omium.org>, ryandcase@...omium.org,
boris.brezillon@...tlin.com,
linux-arm-msm <linux-arm-msm@...r.kernel.org>,
Girish Mahadevan <girishm@...eaurora.org>,
devicetree@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
linux-spi <linux-spi@...r.kernel.org>,
Rob Herring <robh+dt@...nel.org>,
Mark Rutland <mark.rutland@....com>
Subject: Re: [PATCH v2 1/2] dt-bindings: spi: Qualcomm Quad SPI(QSPI)
documentation
On Fri, Sep 21, 2018 at 11:40:24AM -0700, Stephen Boyd wrote:
> It seems that everybody has misunderstood my email. Let me try to
> clarify.
> I'm not saying to replace the sdm845 qspi compatible with a generic one.
> I'm recommending that a generic one is added in addition to the SoC
> specific one. That way, we get to put the generic compatible string in
> the driver and not need to update the driver compatible string array
> each time a new SoC comes out with a new compatible string.
> If it turns out later that we need to handle some bug in that specific
> SoC compatible string then we're good to go and we can handle it by
> matching the more specific SoC version compatible.
Right, the policy is generally not to have these strings at all. IIRC
the argument is that they tend to either become unclear as the marketing
and technology changes.
Download attachment "signature.asc" of type "application/pgp-signature" (489 bytes)
Powered by blists - more mailing lists