From: timur@codeaurora.org (Timur Tabi)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 1/4] net: phy: at803x: Document RGMII RX and TX clock delay issues
Date: Fri, 21 Jul 2017 08:20:39 -0500 [thread overview]
Message-ID: <a9d3777c-1752-d79b-8302-d09c5f736a9f@codeaurora.org> (raw)
In-Reply-To: <051653a2-946f-6a0b-4cff-b403d1197038@sigmadesigns.com>
On 7/21/17 6:25 AM, Marc Gonzalez wrote:
> + * NB: This code assumes that RGMII RX clock delay is disabled
> + * at reset, but actually, RX clock delay is enabled at reset.
Could we change this to say, "RX clock delay is enabled at reset on some
systems."? Otherwise, it implies that the code is wrong 100% of the
time and should be fixed, not documented.
--
Sent by an employee of the Qualcomm Innovation Center, Inc.
The Qualcomm Innovation Center, Inc. is a member of the
Code Aurora Forum, hosted by The Linux Foundation.
next prev parent reply other threads:[~2017-07-21 13:20 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-21 11:22 [PATCH v2 0/4] RGMII RX and TX clock delays using Atheros 8035 Marc Gonzalez
2017-07-21 11:25 ` [PATCH v2 1/4] net: phy: at803x: Document RGMII RX and TX clock delay issues Marc Gonzalez
2017-07-21 13:20 ` Timur Tabi [this message]
2017-07-21 13:29 ` Marc Gonzalez
2017-07-21 14:06 ` Timur Tabi
2017-07-21 14:36 ` Marc Gonzalez
2017-07-21 11:25 ` [PATCH v2 2/4] net: ethernet: nb8800: Set RGMII_MODE for all RGMII modes Marc Gonzalez
2017-07-21 13:00 ` Måns Rullgård
2017-07-21 18:06 ` Florian Fainelli
2017-07-21 11:26 ` [PATCH v2 3/4] net: ethernet: nb8800: Fix RGMII TX clock delay setup Marc Gonzalez
2017-07-21 13:04 ` Måns Rullgård
2017-07-21 13:43 ` Marc Gonzalez
2017-07-21 13:47 ` Måns Rullgård
2017-07-21 14:18 ` Marc Gonzalez
2017-07-21 14:24 ` Måns Rullgård
2017-07-21 18:15 ` Florian Fainelli
2017-07-21 11:29 ` [PATCH v2 4/4] ARM: dts: tango4: Add RGMII RX and TX clock delays Marc Gonzalez
2017-07-21 12:47 ` [PATCH v2 0/4] RGMII RX and TX clock delays using Atheros 8035 Marc Gonzalez
2017-07-21 13:16 ` Marc Gonzalez
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=a9d3777c-1752-d79b-8302-d09c5f736a9f@codeaurora.org \
--to=timur@codeaurora.org \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).