From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
Geert Uytterhoeven <geert+renesas@glider.be>
Cc: linux-renesas-soc@vger.kernel.org,
Prabhakar <prabhakar.csengg@gmail.com>,
Sergey Shtylyov <s.shtylyov@omp.ru>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] memory: renesas-rpc-if: Fix PHYCNT.STRTIM setting
Date: Thu, 26 Jan 2023 10:01:49 +0100 [thread overview]
Message-ID: <Y9JBfTVqjXZqi1r3@ninjato> (raw)
In-Reply-To: <8f9d6e07-6549-9b2e-a45b-f262b59bfe5f@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1413 bytes --]
Hi Krzysztof,
> > I need it because of ".revision". This only applies to "ES1.*",
> > there are "ES2.*" and "ES3.*" around which have the same SoC number.
> > Also, there is usually no version numbering for the IP core. We need to
> > use this scheme in a number of other places already, sadly.
>
> I did not get whether this is runtime characteristics or it can be
> customized with compatible (just you did not do it)?
We have compatibles per SoC, i.e. "r8a7795". We don't have compatibles
for ES versions, i.e. no "r8a7795-es10" or "r8a7795-es20".
The latter would not be practical. We can't know in advance how many ES
revisions there will be, so we can't prepare DTs accordingly. Updating
later would be also difficult because we are usually not notified if
there is a new ES version. Only if there are problems with it. And which
board is available with which ES version is chaotic^2.
Also, if we update DTs later, old DTBs would not work with newer kernels
(requiring a later added compaible for a new ES version). This all still
ignores that it would be a churn to update for every ES version of every
SoC. We have quite many to support. That's why we use soc_device_match()
for ES versions in many places alreday. It was never a problem so far.
That's my reasoning, probably Geert has something to add. He maintains
the Renesas DT files.
All the best,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-26 9:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-18 10:46 [PATCH v2] memory: renesas-rpc-if: Fix PHYCNT.STRTIM setting Wolfram Sang
2023-01-22 12:05 ` Krzysztof Kozlowski
2023-01-23 6:58 ` Wolfram Sang
2023-01-23 7:55 ` Krzysztof Kozlowski
2023-01-26 9:01 ` Wolfram Sang [this message]
2023-01-26 9:27 ` Geert Uytterhoeven
2023-01-26 9:51 ` Krzysztof Kozlowski
2023-01-26 9:39 ` Geert Uytterhoeven
2023-01-26 12:48 ` Wolfram Sang
2023-01-26 13:13 ` Geert Uytterhoeven
2023-01-26 13:26 ` Lad, Prabhakar
2023-01-26 16:39 ` Wolfram Sang
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=Y9JBfTVqjXZqi1r3@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=geert+renesas@glider.be \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=prabhakar.csengg@gmail.com \
--cc=s.shtylyov@omp.ru \
/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