Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Arınç ÜNAL" <arinc.unal@arinc9.com>
To: Justin Swartz <justin.swartz@risingedge.co.za>
Cc: Daniel Golle <daniel@makrotopia.org>,
	DENG Qingfang <dqfext@gmail.com>,
	Sean Wang <sean.wang@mediatek.com>, Andrew Lunn <andrew@lunn.ch>,
	Florian Fainelli <f.fainelli@gmail.com>,
	Vladimir Oltean <olteanv@gmail.com>,
	"David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	Matthias Brugger <matthias.bgg@gmail.com>,
	AngeloGioacchino Del Regno
	<angelogioacchino.delregno@collabora.com>,
	netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org,
	linux-mediatek@lists.infradead.org
Subject: Re: [PATCH] net: dsa: mt7530: increase reset hold time
Date: Wed, 13 Mar 2024 15:06:04 +0300	[thread overview]
Message-ID: <2640a495-97a0-4669-a53a-e367af956a78@arinc9.com> (raw)
In-Reply-To: <e6525cac666a033a5866465abb3e63f1@risingedge.co.za>

On 13.03.2024 14:52, Justin Swartz wrote:
> 
> On 2024-03-13 10:59, Arınç ÜNAL wrote:
>> This ship has sailed anyway. Now the changes the first patch did must be
>> reverted too. I will deal with this from now on, you can stop sending
>> patches regarding this.
> 
> At least if the first patch isn't reverted, the approach used is
> less likely to result in the problem occuring, IMHO.

I disagree that the previous approach is less likely to result in the
problem occurring. If you don't like the delay amount we agreed on, feel
free to express a higher amount.

I also disagree on introducing a solution that is in addition to another
solution, both of which fix the same problem.

> 
> The delay between deliberately switching the LEDs off, instead of
> only waiting on chip reset logic to handle that, and the reset
> assertion could be considered a "reset setup" period to complement
> the original reset hold period.
> 
> Increasing the hold period to what should be 5000 - 5100 usec,
> definitely made the problem go away my testing, but the previous
> approach is (if nothing else) more explicit in its intent.

I don't want any unnecessary complications on the code I'm maintaining. I
already gave a clear intent on the patch log that introduces a simpler and
more efficient approach, it doesn't need to be on the code.

Arınç


  reply	other threads:[~2024-03-13 12:06 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-03-05  4:39 [PATCH] net: dsa: mt7530: disable LEDs before reset Justin Swartz
2024-03-08  9:51 ` Arınç ÜNAL
2024-03-08 14:46   ` Daniel Golle
2024-03-12  0:07   ` Justin Swartz
2024-03-12  1:03     ` Andrew Lunn
2024-03-12  2:41     ` Arınç ÜNAL
2024-03-12 12:01       ` Justin Swartz
2024-03-12 14:06         ` Arınç ÜNAL
2024-03-12 15:25           ` Justin Swartz
2024-03-12 16:35             ` Justin Swartz
2024-03-12 19:21               ` [PATCH] net: dsa: mt7530: increase reset hold time Justin Swartz
2024-03-13  8:59                 ` Arınç ÜNAL
2024-03-13 11:52                   ` Justin Swartz
2024-03-13 12:06                     ` Arınç ÜNAL [this message]
2024-03-13 13:13                       ` Justin Swartz
2024-03-13 15:04                         ` Arınç ÜNAL
2024-03-13 15:38                           ` Justin Swartz
2024-03-13 15:51                             ` Arınç ÜNAL
2024-03-11 21:10 ` [PATCH] net: dsa: mt7530: disable LEDs before reset patchwork-bot+netdevbpf
2024-03-11 21:22   ` Arınç ÜNAL
2024-03-11 21:58     ` Jakub Kicinski
2024-03-11 21:58     ` Daniel Golle
2024-03-11 23:27       ` Arınç ÜNAL
2024-03-11 23:43         ` Daniel Golle
2024-03-12  3:17           ` Arınç ÜNAL
2024-03-12  8:38   ` Arınç ÜNAL
2024-03-12 10:46     ` Paolo Abeni
2024-03-12 11:21       ` Arınç ÜNAL

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=2640a495-97a0-4669-a53a-e367af956a78@arinc9.com \
    --to=arinc.unal@arinc9.com \
    --cc=andrew@lunn.ch \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=daniel@makrotopia.org \
    --cc=davem@davemloft.net \
    --cc=dqfext@gmail.com \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --cc=justin.swartz@risingedge.co.za \
    --cc=kuba@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mediatek@lists.infradead.org \
    --cc=matthias.bgg@gmail.com \
    --cc=netdev@vger.kernel.org \
    --cc=olteanv@gmail.com \
    --cc=pabeni@redhat.com \
    --cc=sean.wang@mediatek.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