archive mirror
 help / color / mirror / Atom feed
From: Naresh Kamboju <>
	<>, Tony Lindgren <>,,
	 Linux ARM <>,
	 Linux-OMAP <>,
Cc: Benoit Cousson <>,
	Kishon Vijay Abraham I <>,
	 Vignesh Raghavendra <>,
	Viresh Kumar <>,
	 Rob Herring <>
Subject: #regzb introduced: 98feab31ac49 ("ARM: OMAP2+: Drop legacy platform data for dra7 sata")
Date: Thu, 6 May 2021 16:30:36 +0530	[thread overview]
Message-ID: <> (raw)

[If it is already reported please ignore]

LKFT test reported regression on TI BeagleBoard-X15 arm32 bit platform as
The device was not able to detect SATA drive.

dmesg short log:
jitterentropy: Initialization failed with host not compliant with
requirements: 2
ata1: SATA max UDMA/133 mmio [mem 0x4a140000-0x4a1410ff] port 0x100 irq 101
wkupaon-clkctrl:0068:0: failed to disable
ata1: SATA link down (SStatus 0 SControl 300)
ata1: softreset failed (1st FIS failed)

Our bisect script pointed this as the first bad commit on linux
mainline master branch.

Full test log:
SATA detection failed log link,

commit 98feab31ac491400f28b76a04dabd18ce21e91ba
Author: Tony Lindgren <>
Date:   Wed Mar 10 14:03:51 2021 +0200

    ARM: OMAP2+: Drop legacy platform data for dra7 sata

    We can now probe devices with ti-sysc interconnect driver and dts data.
    Let's drop the related platform data and custom ti,hwmods dts property.

    As we're just dropping data, and the early platform data init is based on
    the custom ti,hwmods property, we want to drop both the platform data and
    ti,hwmods property in a single patch.

    Signed-off-by: Tony Lindgren <>

steps to reproduce:
- Build arm zImage/dtb/modules on mainline tree and configs
- connect SATA drive and boot x15 device
- check the dmesg for failed logs
 - check to find /dev/sda

  git branch: master
  git repo:
  git commit: f0728bfeb21a24bbb7d5ad1828b67a359550fa17

Steps to build:
# TuxMake is a command line tool and Python library that provides
# portable and repeatable Linux kernel builds across a variety of
# architectures, toolchains, kernel configurations, and make targets.
# TuxMake supports the concept of runtimes.
# See, for that to work it requires
# that you install podman or docker on your system.
# To install tuxmake on your system globally:
# sudo pip3 install -U tuxmake
# See for complete documentation.

tuxmake --runtime podman --target-arch arm --toolchain gcc-9 --kconfig
defconfig --kconfig-add
--kconfig-add CONFIG_ARM_TI_CPUFREQ=y --kconfig-add
--kconfig-add CONFIG_OF=y --kconfig-add CONFIG_SYN_COOKIES=y

Linaro LKFT

             reply	other threads:[~2021-05-06 11:00 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-06 11:00 Naresh Kamboju [this message]
2021-05-06 11:53 ` #regzb introduced: 98feab31ac49 ("ARM: OMAP2+: Drop legacy platform data for dra7 sata") Tony Lindgren
2021-05-06 15:18   ` Naresh Kamboju
2021-05-07  8:02     ` Tony Lindgren
2021-05-07  8:27       ` Thorsten Leemhuis
2021-05-07  9:23         ` Tony Lindgren
2021-05-07  9:27         ` Naresh Kamboju
2021-05-07  9:35         ` Tony Lindgren
2021-05-07  9:39           ` Thorsten Leemhuis
2021-05-07  9:40             ` Tony Lindgren

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \ \ \ \ \ \

* 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;
as well as URLs for NNTP newsgroup(s).