Re: [PATCH 01/31] swim: Assert strobe with stable outputs

Laurent Vivier <[email protected]> Tue, 21 Jul 2026 08:23:50 +0200
Newsgroups org.kernel.vger.linux-m68k,org.kernel.vger.linux-block,org.kernel.vger.linux-kernel
Message-ID <[email protected]>
Le 21/07/2026 =C3=A0 07:41, Finn Thain a =C3=A9crit=C2=A0:
>=20
> On Mon, 20 Jul 2026, Laurent Vivier wrote:
>=20
>> Le 16/07/2026 =C3=A0 12:02, Finn Thain a =C3=A9crit=C2=A0:
>>
>>> Keep the four phase pin directions set to output and hold their levels
>>> constant during LSTRB signalling.
>>
>> Perhaps you can also add a short comment to describe the changes you
>> made to the defines.
>>
>=20
> Can you clarify please? I think what you're asking is, shouldn't the PH3
> pin be an input when it's not being used for LSTRB signalling?

My question is simpler:
You added the directions bits in the defines and it's not clear in the com=
mit message.
For instance, I can see you update all the defines, but at first glance I =
didn't understand why.

Thanks,
Laurent

>=20
> It would be nice if we had specs for the relevant FDD models, to show th=
at
> no FDD ever drives the phase lines. Then I could write something more
> authoritative. I don't have that information but I do have the chip spec=
s.
>=20
> The swim3.c driver never sets phase pin direction because the SWIM3 chip
> doesn't implement that i.e. the four phase pins are permanently outputs.
> Similary, the programming model for the IWM chip offers no way to use
> phase lines as inputs, AFAICT. Same for the uPD72070 FDC chip.
>=20
> I will add some of these observations to the commit log or the commentar=
y
> in the source code if you think it would help.
>=20
> Thanks for your review.