public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: Alexander Sverdlin <alexander.sverdlin@gmail.com>
To: Judith Mendez <jm@ti.com>,
	Francesco Dolcini <francesco@dolcini.it>,
	 Vitor Soares <ivitro@gmail.com>
Cc: Markus Schneider-Pargmann <msp@baylibre.com>,
	Vishal Mahaveer	 <vishalm@ti.com>,
	Kevin Hilman <khilman@baylibre.com>, Dhruva Gole <d-gole@ti.com>,
	 Sebin Francis <sebin.francis@ti.com>,
	Kendall Willis <k-willis@ti.com>, Akashdeep Kaur <a-kaur@ti.com>,
	 linux-arm-kernel@lists.infradead.org,
	devicetree@vger.kernel.org,  linux-kernel@vger.kernel.org,
	Nishanth Menon <nm@ti.com>,
	Vignesh Raghavendra	 <vigneshr@ti.com>,
	Tero Kristo <kristo@kernel.org>,
	 alexander.sverdlin@siemens.com
Subject: Re: [PATCH] arm64: dts: ti: k3-am62a7-sk: Disable mmc Schmitt Trigger
Date: Thu, 05 Feb 2026 18:57:28 +0100	[thread overview]
Message-ID: <abb8fa81c3fc7caec0b232e204af4bce71a7a667.camel@gmail.com> (raw)
In-Reply-To: <fcfcd3fb-2eac-4865-98f3-ef2ae24381bb@ti.com>

Hi Judith,

On Thu, 2026-02-05 at 11:07 -0600, Judith Mendez wrote:
> > Verdin is now booting fine. The boot failure was related to other U-Boot
> > bugs (as Nishanth mentioned) that are now fixed.
> 
> Good to know, that isolates the issue to only one board.

not really, as I mentioned, I had observed some issues with one of our
internal development boards, but I can only provide the data after couple of
weeks, after my vacation.

-- 
Alexander Sverdlin.


  reply	other threads:[~2026-02-05 17:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06 16:22 [PATCH] arm64: dts: ti: k3-am62a7-sk: Disable mmc Schmitt Trigger Markus Schneider-Pargmann (TI.com)
2026-01-06 17:25 ` Alexander Sverdlin
2026-01-06 20:25   ` Markus Schneider-Pargmann
2026-01-07 14:23     ` Alexander Sverdlin
2026-01-07 22:57     ` Alexander Sverdlin
2026-01-08 16:40       ` Nishanth Menon
2026-01-08 17:54         ` Sverdlin, Alexander
2026-01-07 14:49   ` Alexander Sverdlin
2026-01-08 19:04     ` Markus Schneider-Pargmann
2026-01-08 14:07 ` Vitor Soares
2026-01-08 14:23   ` Alexander Sverdlin
2026-01-08 16:42   ` Nishanth Menon
2026-01-13  0:29 ` Judith Mendez
     [not found]   ` <DFO764ES0FNP.1SUQK9R0EUUDQ@baylibre.com>
2026-01-14 22:04     ` Judith Mendez
     [not found]       ` <DG59D7WGM35A.1WNIIMNCQ8U3C@baylibre.com>
2026-02-05  2:03         ` Judith Mendez
2026-02-05  7:24           ` Francesco Dolcini
2026-02-05 17:07             ` Judith Mendez
2026-02-05 17:57               ` Alexander Sverdlin [this message]
2026-02-17 12:57           ` Sverdlin, Alexander
2026-02-17 13:19             ` Sverdlin, Alexander
2026-02-17 13:23             ` Sverdlin, Alexander
2026-02-20  0:10               ` Judith Mendez
2026-02-20  0:42                 ` Judith Mendez
2026-03-16 12:22                   ` Sverdlin, Alexander

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=abb8fa81c3fc7caec0b232e204af4bce71a7a667.camel@gmail.com \
    --to=alexander.sverdlin@gmail.com \
    --cc=a-kaur@ti.com \
    --cc=alexander.sverdlin@siemens.com \
    --cc=d-gole@ti.com \
    --cc=devicetree@vger.kernel.org \
    --cc=francesco@dolcini.it \
    --cc=ivitro@gmail.com \
    --cc=jm@ti.com \
    --cc=k-willis@ti.com \
    --cc=khilman@baylibre.com \
    --cc=kristo@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=msp@baylibre.com \
    --cc=nm@ti.com \
    --cc=sebin.francis@ti.com \
    --cc=vigneshr@ti.com \
    --cc=vishalm@ti.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