Linux-mediatek Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Justin Swartz <justin.swartz@risingedge.co.za>
To: "Arınç ÜNAL" <arinc.unal@arinc9.com>
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 17:38:35 +0200	[thread overview]
Message-ID: <3146df060620f08a620417cfcf2b2179@risingedge.co.za> (raw)
In-Reply-To: <997db446-030b-4e6a-beea-0ae7d990e7e2@arinc9.com>

On 2024-03-13 17:04, Arınç ÜNAL wrote:
> On 13.03.2024 16:13, Justin Swartz wrote:
>> On 2024-03-13 14:06, Arınç ÜNAL wrote:
>>> 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 created and tested a patch to entertain your input about what you
>> thought could be a suitable hold period to address the problem, and it
>> appeared to work. The criteria being that the crystal frequency 
>> selection
>> was correct over 20 tests.
>> 
>> So if only the reset hold period is going to change, I'm good with 
>> what
>> you had suggested: 5000 - 5100 usec.
>> 
>> Ultimately the selection of this period should be guided by the timing
>> information provided in a datasheet or design guide from the 
>> manufacturer.
> 
> That's a good point, I agree.
> 
>> 
>> If you, or anyone else, has such a document that provides this 
>> information
>> and is able to confirm or deny speculation about any/all timing 
>> periods
>> related to reset, please do so.
> 
> These are the documents I use to program this switch family. I did not
> stumble upon a page going over this.
> 
> MT7621 Giga Switch Programming Guide v0.3:
> 
> https://github.com/vschagen/documents/blob/main/MT7621_ProgrammingGuide_GSW_v0_3.pdf
> 
> MT7531 switch chip datasheet:
> 
> https://wiki.banana-pi.org/Banana_Pi_BPI-R64#Documents

Thanks for the links.

Have you encountered this one?

MT7530 Giga Switch Programming Guide v0.1:
https://github.com/libc0607/arduino_mt7530/blob/master/MT7530_programming_guide_V00.pdf

It has some timing diagrams, but nothing I found for reset.

The HWTRAP description has some bits swapped, so I guess those were 
typos,
in the case of XTAL_SELECT.


>>> I also disagree on introducing a solution that is in addition to 
>>> another
>>> solution, both of which fix the same problem.
>> 
>> I'm not sure I understand why you say that. These patches were 
>> intended
>> to be applied exclusively, or in other words: in isolation - not 
>> together.
>> 
>> Although if they were applied together, it wouldn't really matter.
>> 
>> For the record, I've only continued to keep this thread alive in the
>> hope that some solution to this problem will make it into mainline
>> eventually.
>> 
>> I don't care if it was my original patch, the subsequent patch, or a
>> later patch provided by you or someone else. :)
> 
> I think you've missed that your patch is already applied. And it won't 
> be
> reverted for reasons explained by Paolo in this mail thread.
> 
> https://git.kernel.org/netdev/net-next/c/2920dd92b980
> 
> So if your patch here were to be applied too, the final mt7530.c would 
> have
> the LEDs disabled AND before reset deassertion delay increased.

Yes, I seem to have missed that. I thought your request for the
patch to be reverted definitely would have been performed, or at
least queued, seeing as you're the maintainer.


  reply	other threads:[~2024-03-13 15:38 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
2024-03-13 13:13                       ` Justin Swartz
2024-03-13 15:04                         ` Arınç ÜNAL
2024-03-13 15:38                           ` Justin Swartz [this message]
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=3146df060620f08a620417cfcf2b2179@risingedge.co.za \
    --to=justin.swartz@risingedge.co.za \
    --cc=andrew@lunn.ch \
    --cc=angelogioacchino.delregno@collabora.com \
    --cc=arinc.unal@arinc9.com \
    --cc=daniel@makrotopia.org \
    --cc=davem@davemloft.net \
    --cc=dqfext@gmail.com \
    --cc=edumazet@google.com \
    --cc=f.fainelli@gmail.com \
    --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