From: Wolfram Sang <wsa@the-dreams.de>
To: Simon Horman <horms+renesas@verge.net.au>
Cc: netdev@vger.kernel.org, linux-renesas-soc@vger.kernel.org,
Magnus Damm <magnus.damm@gmail.com>,
Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>,
Wolfram Sang <wsa+renesas@sang-engineering.com>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>
Subject: Re: [PATCH/RFC net-next] ravb: Avoid unsupported internal delay mode for R-Car E3/D3
Date: Mon, 8 Apr 2019 11:01:04 +0200 [thread overview]
Message-ID: <20190408090104.GB1615@kunai> (raw)
In-Reply-To: <20190408082928.22840-1-horms+renesas@verge.net.au>
[-- Attachment #1: Type: text/plain, Size: 740 bytes --]
On Mon, Apr 08, 2019 at 10:29:28AM +0200, Simon Horman wrote:
> According to the R-Car Gen3 Hardware Manual Errata for Rev 1.00 of
> August 24, 2018, the TX clock internal delay mode isn't supported
> on R-Car E3 (r8a77990) and D3 (r8a77995).
Yes, it made it also into the revised documentation v1.50, see chapter
50.2.7., bit 14.
> +static const struct soc_device_attribute ravb_delay_mode_quirk_match[] = {
> + { .soc_id = "r8a77990", .revision = "ES1.*" },
> + { .soc_id = "r8a77995", .revision = "ES1.*" },
> + { /* sentinel */ }
> +};
I might have missed it but is there a plan to fix this in later
revisions of D3/E3? I was under the impression that it is not and then
we could base it on compatible rather than soc_device_match?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2019-04-08 9:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 8:29 [PATCH/RFC net-next] ravb: Avoid unsupported internal delay mode for R-Car E3/D3 Simon Horman
2019-04-08 9:01 ` Wolfram Sang [this message]
2019-04-08 9:48 ` Simon Horman
2019-04-08 11:12 ` Wolfram Sang
2019-04-08 13:02 ` Simon Horman
2019-04-08 13:40 ` Wolfram Sang
2019-04-08 17:39 ` Sergei Shtylyov
2019-04-08 17:49 ` Andrew Lunn
2019-04-09 10:45 ` Simon Horman
2019-04-09 15:03 ` Sergei Shtylyov
2019-04-10 9:37 ` Simon Horman
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=20190408090104.GB1615@kunai \
--to=wsa@the-dreams.de \
--cc=horms+renesas@verge.net.au \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=wsa+renesas@sang-engineering.com \
--cc=yoshihiro.shimoda.uh@renesas.com \
/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;
as well as URLs for NNTP newsgroup(s).