All of lore.kernel.org
 help / color / mirror / Atom feed
From: patchwork-bot+netdevbpf@kernel.org
To: Justin Swartz <justin.swartz@risingedge.co.za>
Cc: arinc.unal@arinc9.com, daniel@makrotopia.org, dqfext@gmail.com,
	sean.wang@mediatek.com, andrew@lunn.ch, f.fainelli@gmail.com,
	olteanv@gmail.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, matthias.bgg@gmail.com,
	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: disable LEDs before reset
Date: Mon, 11 Mar 2024 21:10:31 +0000	[thread overview]
Message-ID: <171019143163.14853.15330891015381229970.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240305043952.21590-1-justin.swartz@risingedge.co.za>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue,  5 Mar 2024 06:39:51 +0200 you wrote:
> Disable LEDs just before resetting the MT7530 to avoid
> situations where the ESW_P4_LED_0 and ESW_P3_LED_0 pin
> states may cause an unintended external crystal frequency
> to be selected.
> 
> The HT_XTAL_FSEL (External Crystal Frequency Selection)
> field of HWTRAP (the Hardware Trap register) stores a
> 2-bit value that represents the state of the ESW_P4_LED_0
> and ESW_P4_LED_0 pins (seemingly) sampled just after the
> MT7530 has been reset, as:
> 
> [...]

Here is the summary with links:
  - net: dsa: mt7530: disable LEDs before reset
    https://git.kernel.org/netdev/net-next/c/2920dd92b980

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



WARNING: multiple messages have this Message-ID (diff)
From: patchwork-bot+netdevbpf@kernel.org
To: Justin Swartz <justin.swartz@risingedge.co.za>
Cc: arinc.unal@arinc9.com, daniel@makrotopia.org, dqfext@gmail.com,
	sean.wang@mediatek.com, andrew@lunn.ch, f.fainelli@gmail.com,
	olteanv@gmail.com, davem@davemloft.net, edumazet@google.com,
	kuba@kernel.org, pabeni@redhat.com, matthias.bgg@gmail.com,
	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: disable LEDs before reset
Date: Mon, 11 Mar 2024 21:10:31 +0000	[thread overview]
Message-ID: <171019143163.14853.15330891015381229970.git-patchwork-notify@kernel.org> (raw)
In-Reply-To: <20240305043952.21590-1-justin.swartz@risingedge.co.za>

Hello:

This patch was applied to netdev/net-next.git (main)
by Jakub Kicinski <kuba@kernel.org>:

On Tue,  5 Mar 2024 06:39:51 +0200 you wrote:
> Disable LEDs just before resetting the MT7530 to avoid
> situations where the ESW_P4_LED_0 and ESW_P3_LED_0 pin
> states may cause an unintended external crystal frequency
> to be selected.
> 
> The HT_XTAL_FSEL (External Crystal Frequency Selection)
> field of HWTRAP (the Hardware Trap register) stores a
> 2-bit value that represents the state of the ESW_P4_LED_0
> and ESW_P4_LED_0 pins (seemingly) sampled just after the
> MT7530 has been reset, as:
> 
> [...]

Here is the summary with links:
  - net: dsa: mt7530: disable LEDs before reset
    https://git.kernel.org/netdev/net-next/c/2920dd92b980

You are awesome, thank you!
-- 
Deet-doot-dot, I am a bot.
https://korg.docs.kernel.org/patchwork/pwbot.html



_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel

  parent reply	other threads:[~2024-03-11 21:10 UTC|newest]

Thread overview: 44+ 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-05  4:39 ` Justin Swartz
2024-03-08  9:51 ` Arınç ÜNAL
2024-03-08 14:46   ` Daniel Golle
2024-03-08 14:46     ` Daniel Golle
2024-03-12  0:07   ` Justin Swartz
2024-03-12  0:07     ` Justin Swartz
2024-03-12  1:03     ` Andrew Lunn
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 12:01         ` Justin Swartz
2024-03-12 14:06         ` Arınç ÜNAL
2024-03-12 15:25           ` Justin Swartz
2024-03-12 15:25             ` Justin Swartz
2024-03-12 16:35             ` 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-12 19:21                 ` Justin Swartz
2024-03-13  8:59                 ` Arınç ÜNAL
2024-03-13 11:52                   ` Justin Swartz
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 13:13                         ` Justin Swartz
2024-03-13 15:04                         ` Arınç ÜNAL
2024-03-13 15:38                           ` Justin Swartz
2024-03-13 15:38                             ` Justin Swartz
2024-03-13 15:51                             ` Arınç ÜNAL
2024-03-11 21:10 ` patchwork-bot+netdevbpf [this message]
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       ` Jakub Kicinski
2024-03-11 21:58     ` Daniel Golle
2024-03-11 21:58       ` Daniel Golle
2024-03-11 23:27       ` Arınç ÜNAL
2024-03-11 23:43         ` Daniel Golle
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 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=171019143163.14853.15330891015381229970.git-patchwork-notify@kernel.org \
    --to=patchwork-bot+netdevbpf@kernel.org \
    --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=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 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.