mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Christian Zigotzky <chzigotzky@xenosoft.de>
To: Marc Zyngier <maz@kernel.org>
Cc: Rob Herring <robh@kernel.org>,
	apatel@ventanamicro.com, DTML <devicetree@vger.kernel.org>,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>,
	linuxppc-dev <linuxppc-dev@lists.ozlabs.org>,
	mad skateman <madskateman@gmail.com>,
	"R.T.Dickinson" <rtd2@xtra.co.nz>,
	Matthew Leaman <matthew@a-eon.biz>,
	Darren Stevens <darren@stevens-zone.net>,
	Christian Zigotzky <info@xenosoft.de>
Subject: Re: [PowerPC] [PASEMI] Issue with the identification of ATA drives after the of/irq updates 2024-05-29
Date: Tue, 2 Jul 2024 19:55:38 +0200	[thread overview]
Message-ID: <68b7988d-eaaa-4713-99c3-525a34c5b322@xenosoft.de> (raw)
In-Reply-To: <861q4bizxc.wl-maz@kernel.org>

Hello Marc,

Thank you for your reply.

On 02.07.24 17:19, Marc Zyngier wrote:
> Christian,
>
> On Sun, 30 Jun 2024 11:21:55 +0100,
> Christian Zigotzky <chzigotzky@xenosoft.de> wrote:
>> Hello,
>>
>> There is an issue with the identification of ATA drives with our
>> P.A. Semi Nemo boards [1] after the
>> commit "of/irq: Factor out parsing of interrupt-map parent
>> phandle+args from of_irq_parse_raw()" [2].
>>
>> Error messages:
>>
>> ata2.00: failed to IDENTIFY (I/O error, err_mask=0x4)
>> ata2.00: qc timeout after 10000 mssecs (cmd 0xec)
>>
>> Screenshots [3]
>>
>> I bisected yesterday [4] and "of/irq: Factor out parsing of
>> interrupt-map parent phandle+args from of_irq_parse_raw()" [2] is the
>> first bad commit.
>>
>> Then I created a patch for reverting this first bad commit. I also
>> reverted the changes in drivers/of/property.c. [5]
>>
>> The patched kernel boots with successful detection of the ATA devices.
>>
>> Please check the of/irq updates.
> It is hard to understand what is going on with so little information.
>
> Please provide the device tree for your platform. It isn't possible to
> debug this without it, no matter how many pictures you provide. If it
> doesn't exist in source form, you can dump it using:
>
> # dtc -I dtb /sys/firmware/fdt
>
> and posting the full output.
>
> Additionally, a full dmesg of both working and non working boots would
> be useful.
>
> Thanks,
>
> 	M.
>
The device tree of the Nemo board and further information: 
https://forum.hyperion-entertainment.com/viewtopic.php?p=54406#p54406

Cheers,
Christian

  reply	other threads:[~2024-07-02 17:58 UTC|newest]

Thread overview: 33+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-30 10:21 Christian Zigotzky
2024-07-02 15:19 ` Marc Zyngier
2024-07-02 17:55   ` Christian Zigotzky [this message]
2024-07-02 19:49     ` Marc Zyngier
2024-07-03  3:11       ` Christian Zigotzky
2024-07-03  6:40         ` Marc Zyngier
2024-07-03 10:26           ` Christian Zigotzky
2024-07-03 10:41             ` Marc Zyngier
2024-07-03 16:23               ` Christian Zigotzky
2024-07-02 16:54 ` Marc Zyngier
2024-07-02 20:48   ` Rob Herring
2024-07-02 21:42     ` Marc Zyngier
2024-07-03 11:30     ` Michael Ellerman
2024-07-03 12:09       ` Marc Zyngier
2024-07-03  3:27   ` Christian Zigotzky
2024-07-03  6:41     ` Marc Zyngier
2024-07-04  4:10   ` Christian Zigotzky
2024-07-04  8:28     ` Marc Zyngier
2024-07-04 18:54       ` Christian Zigotzky
2024-07-04 11:53     ` Michael Ellerman
2024-07-04 18:27       ` Christian Zigotzky
2024-07-04 18:59         ` Christian Zigotzky
2024-07-05  1:19           ` Michael Ellerman
2024-07-05 20:45             ` Segher Boessenkool
2024-07-06  4:15             ` Christian Zigotzky
2024-07-06 15:54               ` Christian Zigotzky
2024-07-10  3:53                 ` Christian Zigotzky
2024-07-10 15:05                   ` Rob Herring
2024-07-10 15:53                     ` Christian Zigotzky
2024-07-06  4:08         ` Christian Zigotzky
2024-07-05  6:59     ` Christian Zigotzky
     [not found] <C2FBFAD0-DEEE-4906-80B1-5FA745CD9726@xenosoft.de>
2024-07-05  8:05 ` Christian Zigotzky
2024-07-05 13:01   ` Marc Zyngier

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=68b7988d-eaaa-4713-99c3-525a34c5b322@xenosoft.de \
    --to=chzigotzky@xenosoft.de \
    --cc=apatel@ventanamicro.com \
    --cc=darren@stevens-zone.net \
    --cc=devicetree@vger.kernel.org \
    --cc=info@xenosoft.de \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linuxppc-dev@lists.ozlabs.org \
    --cc=madskateman@gmail.com \
    --cc=matthew@a-eon.biz \
    --cc=maz@kernel.org \
    --cc=robh@kernel.org \
    --cc=rtd2@xtra.co.nz \
    /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

Powered by JetHome