All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Lunn <andrew@lunn.ch>
To: Horatiu Vultur <horatiu.vultur@microchip.com>
Cc: netdev@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org, hkallweit1@gmail.com,
	linux@armlinux.org.uk, Divya.Koppera@microchip.com,
	davem@davemloft.net, kuba@kernel.org, richardcochran@gmail.com,
	UNGLinuxDriver@microchip.com
Subject: Re: [PATCH net 3/3] net: phy: micrel: Remove DT option lan8814,ignore-ts
Date: Fri, 1 Apr 2022 14:47:29 +0200	[thread overview]
Message-ID: <Ykb0YfymcwnPtrxL@lunn.ch> (raw)
In-Reply-To: <20220401094805.3343464-4-horatiu.vultur@microchip.com>

On Fri, Apr 01, 2022 at 11:48:05AM +0200, Horatiu Vultur wrote:
> When the PHY and the MAC are capable of doing timestamping, the PHY has
> priority. Therefore the DT option lan8814,ignore-ts was added such that
> the PHY will not expose a PHC so then the timestamping was done in the
> MAC. This is not the correct approach of doing it, therefore remove
> this.
> 
> Fixes: ece19502834d84 ("net: phy: micrel: 1588 support for LAN8814 phy")
> Signed-off-by: Horatiu Vultur <horatiu.vultur@microchip.com>

Reviewed-by: Andrew Lunn <andrew@lunn.ch>

    Andrew

      reply	other threads:[~2022-04-01 12:47 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-01  9:48 [PATCH net 0/3] net: phy: micrel: Remove latencies support lan8814 Horatiu Vultur
2022-04-01  9:48 ` [PATCH net 1/3] dt-bindings: net: micrel: Revert latency support and timestamping check Horatiu Vultur
2022-04-01 12:37   ` Andrew Lunn
2022-04-01  9:48 ` [PATCH net 2/3] net: phy: micrel: Remove latency from driver Horatiu Vultur
2022-04-01 12:47   ` Andrew Lunn
2022-04-01 13:34     ` Horatiu Vultur
2022-04-01 13:59       ` Allan W. Nielsen
2022-04-01 14:05         ` Andrew Lunn
2022-04-01 14:00       ` Andrew Lunn
2022-04-01  9:48 ` [PATCH net 3/3] net: phy: micrel: Remove DT option lan8814,ignore-ts Horatiu Vultur
2022-04-01 12:47   ` Andrew Lunn [this message]

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=Ykb0YfymcwnPtrxL@lunn.ch \
    --to=andrew@lunn.ch \
    --cc=Divya.Koppera@microchip.com \
    --cc=UNGLinuxDriver@microchip.com \
    --cc=davem@davemloft.net \
    --cc=devicetree@vger.kernel.org \
    --cc=hkallweit1@gmail.com \
    --cc=horatiu.vultur@microchip.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux@armlinux.org.uk \
    --cc=netdev@vger.kernel.org \
    --cc=richardcochran@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.