From: Dinh Nguyen <dinguyen@kernel.org>
To: Pratyush Yadav <p.yadav@ti.com>, Dinh Nguyen <dinh.linux@gmail.com>
Cc: devicetree@vger.kernel.org, broonie@kernel.org, robh+dt@kernel.org
Subject: Re: [PATCHv2 1/3] dt-bindings: spi: cadence-quadspi: document "cdns,qspi-nor-ver-00-10"
Date: Wed, 15 Dec 2021 09:36:46 -0600 [thread overview]
Message-ID: <ad4bbd06-ef56-895c-f30c-4897420843c7@kernel.org> (raw)
In-Reply-To: <20211214200525.7tp2ovbh6vc6rks6@ti.com>
On 12/14/21 2:05 PM, Pratyush Yadav wrote:
> On 08/12/21 05:45PM, Dinh Nguyen wrote:
>> On Mon, Dec 6, 2021 at 9:51 PM Pratyush Yadav <p.yadav@ti.com> wrote:
>>>
>>> On 03/12/21 12:17PM, Dinh Nguyen wrote:
>>>> The QSPI controller on Intel's SoCFPGA platform does not implement the
>>>> CQSPI_REG_WR_COMPLETION_CTRL register, thus a write to this register
>>>> results in a crash.
>>>>
>>>> The module/revision ID is written in the MODULE_ID register. For this
>>>> variance, bits 23-8 is 0x0010.
>>>
>>> When I looked at your original patches I was under the impression that
>>> this was a SoCFPGA specific thing and did not apply to other
>>> implementation of the IP in general.
>>>
>>> If this is indeed a generic thing and we can detect it via the MODULE_ID
>>> register [0], then why not just read that register at probe time and
>>> apply this quirk based on the ID? Why then do we need a separate
>>> compatible at all?
>>>
>>> [0] I would like to see it stated explicitly somewhere that version
>>> 0x0010 does not support the WR_COMPLETION_CTRL register.
>>>
>>
>> I cannot for sure confirm that this condition applies to only 0x0010
>> version of the
>> IP. I can verify that the IP that is in all 3 generations of SoCFPGA
>> devices, all have
>> MODULE_ID value of 0x0010 and all do not have the WR_COMPLETION_CTRL
>> register implemented.
>
> I agree with Rob here. If you are not sure that this is a generic IP
> thing then you should not use a generic compatible.
>
I think using the binding of "intel,socfpga-qspi" should be fine? If we
go by the MODULE_ID value as a indicator of versions, then the version
hasn't changed for all revisions of the SoCFPGA, dating back to the
original Cyclone5, which was introduced in 2012.
Thanks,
Dinh
next prev parent reply other threads:[~2021-12-15 16:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-03 18:17 [PATCHv2 1/3] dt-bindings: spi: cadence-quadspi: document "cdns,qspi-nor-ver-00-10" Dinh Nguyen
2021-12-03 18:17 ` [PATCHv2 2/3] ARM: dts: socfpga: change qspi to "cdns,qspi-nor-ver-00-10" Dinh Nguyen
2021-12-03 18:17 ` [PATCH 3/3] spi: cadence-quadspi: change socfpga-qspi " Dinh Nguyen
2021-12-03 18:18 ` [PATCHv2 1/3] dt-bindings: spi: cadence-quadspi: document "cdns,qspi-nor-ver-00-10" Mark Brown
2021-12-03 19:05 ` Dinh Nguyen
2021-12-06 10:22 ` Pratyush Yadav
2021-12-08 23:45 ` Dinh Nguyen
2021-12-13 20:48 ` Rob Herring
2021-12-13 21:21 ` Dinh Nguyen
2021-12-14 20:05 ` Pratyush Yadav
2021-12-15 15:36 ` Dinh Nguyen [this message]
2021-12-16 18:58 ` Pratyush Yadav
-- strict thread matches above, loose matches on Subject: below --
2021-12-03 17:32 Dinh Nguyen
2021-12-03 14:01 Dinh Nguyen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=ad4bbd06-ef56-895c-f30c-4897420843c7@kernel.org \
--to=dinguyen@kernel.org \
--cc=broonie@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dinh.linux@gmail.com \
--cc=p.yadav@ti.com \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox