[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aLlYkZWBaI5Yz6fo@ryzen>
Date: Thu, 4 Sep 2025 11:14:57 +0200
From: Niklas Cassel <cassel@...nel.org>
To: Krzysztof Kozlowski <krzk@...nel.org>
Cc: Yulin Lu <luyulin@...incomputing.com>, dlemoal@...nel.org,
robh@...nel.org, krzk+dt@...nel.org, conor+dt@...nel.org,
linux-ide@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, vkoul@...nel.org, kishon@...nel.org,
linux-phy@...ts.infradead.org, ningyu@...incomputing.com,
zhengyu@...incomputing.com, linmin@...incomputing.com,
huangyifeng@...incomputing.com, fenglin@...incomputing.com,
lianghujun@...incomputing.com
Subject: Re: [PATCH v3 1/3] dt-bindings: ata: eswin: Document for EIC7700 SoC
ahci
Hello Krzysztof, Rob,
On Thu, Sep 04, 2025 at 09:10:34AM +0200, Krzysztof Kozlowski wrote:
> > +
> > + ports-implemented:
> > + const: 1
>
> I do not see how you addressed request about firmware. Nothing changed
> here, no explanation in the commit msg.
In Yulin's defence, he did comment that when having the Ports Implemented
register initialized by firmware, the Ports Implemented register apparently
gets cleared to zero when rmmoding the driver (probably because it disables
the clocks and regulators to the controller), thus this suggestion breaks
the use case of being able to reload the driver (rmmod + insmod).
He mentioned this, and asked for advice here:
https://lore.kernel.org/linux-ide/2cc9f2ff.6a2.198e04fd36e.Coremail.luyulin@eswincomputing.com/
After no reply he asked the same question again:
https://lore.kernel.org/linux-ide/692e11ca.843.198f0337528.Coremail.luyulin@eswincomputing.com/
I assume that Rob simply missed those messages.
Anyway, I provided my 50 cents here:
https://lore.kernel.org/linux-ide/aLBUC116MdJqDGIJ@flawful.org/
(I would like to add that I think it is the disabling of clocks and
regulators that causes the register to be cleared, since we do call
ahci_platform_assert_rsts() during the first probe, so if it was the reset
that cleared the register, the first probe should also not have worked.)
Not sure if it relevant to mention this reply to Rob's review comment in the
commit message, but perhaps it should have been mentioned in the change log.
Kind regards,
Niklas
Powered by blists - more mailing lists