From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
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: Mon, 23 Jan 2023 07:58:23 +0100 [thread overview]
Message-ID: <Y84wDxiBE6CZqSO5@ninjato> (raw)
In-Reply-To: <fb2a6e85-42ad-8b17-4433-8d5e96c87a80@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 927 bytes --]
Hi Krzysztof,
> > +static const struct soc_device_attribute rpcif_info_match[] = {
> > + { .soc_id = "r8a7795", .revision = "ES1.*", .data = &rpcif_info_r8a7795_es1 },
> > + { .soc_id = "r8a7796", .revision = "ES1.*", .data = &rpcif_info_r8a7796_es1 },
>
> Why do you need soc match? Can't this be inferred from device
> compatible? Maybe the device compatible is not specific enough? Devices
> should not be interested in which SoC they are running - it does not
> matter for them, because the device difference is in the device itself,
> not in the SoC (different SoCs come with different devices).
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.
Thanks for reviewing,
Wolfram
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-01-23 6:58 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 [this message]
2023-01-23 7:55 ` Krzysztof Kozlowski
2023-01-26 9:01 ` Wolfram Sang
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=Y84wDxiBE6CZqSO5@ninjato \
--to=wsa+renesas@sang-engineering.com \
--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