[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Y5iN48rA899u1++7@x1>
Date: Tue, 13 Dec 2022 09:36:19 -0500
From: Brian Masney <bmasney@...hat.com>
To: Javier Martinez Canillas <javierm@...hat.com>,
Shazad Hussain <quic_shazhuss@...cinc.com>
Cc: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>,
Mark Brown <broonie@...nel.org>, andersson@...nel.org,
krzysztof.kozlowski+dt@...aro.org, konrad.dybcio@...aro.org,
robh+dt@...nel.org, johan+linaro@...nel.org,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, ahalaney@...hat.com,
echanude@...hat.com, linux-spi@...r.kernel.org
Subject: Re: [PATCH 4/4] arm64: dts: qcom: sc8280xp: add missing spi nodes
On Tue, Dec 13, 2022 at 02:08:47PM +0100, Javier Martinez Canillas wrote:
> On 12/13/22 14:02, Krzysztof Kozlowski wrote:
> > On 13/12/2022 13:27, Brian Masney wrote:
> > qcom,spi-video-codec is still not specific enough. You need to describe
> > real device behind spidev. To be clear - you do not describe userspace,
> > but the device.
> >
>
> Agree.
>
> I believe Brian just used "qcom,spi-video-codec" as an example but is only
> a make up name to illustrate the concept. QC needs to determine what would
> be the correct <vendor,device> tuple for the IP block that the user-space
> driver will drive.
Yes, that was just an example.
Shazad: Is this thread clear about what QC needs for spidev? I'll let QC
take care of sending patch(es) to add the various compatibles since I'm
not sure what hardware will be backed by spidev.
I'll take care of making sure that sc8280xp.dtsi gets the spi controller
nodes added.
Brian
Powered by blists - more mailing lists