Re: [PATCH] MDIO: FSL_PQ_MDIO: Fix bug on incorrect offset of tbiparegister

From: Oded Gabbay
Date: Thu Jun 13 2013 - 02:45:45 EST

On 06/12/2013 09:31 PM, Scott Wood wrote:
On 06/12/2013 10:08:29 AM, Sebastian Andrzej Siewior wrote:
On 06/12/2013 02:47 PM, Oded Gabbay wrote:
> This patch fixes a bug in the fsl_pq_mdio.c module and in relevant device-tree
> files regarding the correct offset of the tbipa register in the eTSEC
> controller in some of Freescale's PQ3 and QorIQ SoC.
> The bug happens when the mdio in the device tree is configured to be compatible
> to "fsl,gianfar-tbi". Because the mdio device in the device tree points to
> addresses 25520, 26520 or 27520 (depends on the controller ID), the variable
> priv->map at function fsl_pq_mdio_probe, points to that address. However,
> later in the function there is a write to register tbipa that is actually
> located at 25030, 26030 or 27030. Because the correct address is not io mapped,
> the contents are written to a different register in the controller.
> The fix sets the address of the mdio device to start at 25000, 26000 or 27000
> and changes the mii_offset field to 0x520 in the relevant entry
> (fsl,gianfar-tbi) of the fsl_pq_mdio_match array.
> Note: This patch may break MDIO functionallity of some old Freescale's SoC
> until Freescale will fix their device tree files. Basically, every device tree
> which contains an mdio device that is compatible to "fsl,gianfar-tbi" should be
> examined.

Not as is.
Please add a check for the original address. If it has 0x520 at the end
print a warning and fix it up. Please add to the patch description
which register is modified instead if this patch is not applied.
Depending on how critical this it might has to go stable.

I'm not sure it's stable material if this is something that has never worked...

The device tree binding will also need to be fixed to note the difference in "reg" between "fsl,gianfar-mdio" and "fsl-gianfar-tbi" -- and should give an example of the latter.

I read the 2 comments and I'm not sure what should be the best way to move ahead.
I would like to describe what is the impact of not accepting this patch:
When you connect any eTSEC, except the first one, using SGMII, you must configure the TBIPA register because
the MII management configuration uses the TBIPA address as part of the SGMII initialization sequence,
as described in the P2020 Reference manual.
So, if that register is not initialized, the sequence is broken the and eTSEC is not functioning (can not send/receive
I still think the best way to fix it is what I did:
1. Point the priv->map to the start of the whole registers range of the eTSEC
2. Set mii_offset to 0x520 in the "gianfar-tbi" entry of the "fsl_pq_mdio_match" array.
3. Fix all the usages of the "gianfar-tbi" in the device tree files - change the starting address and reg range

I think this is the best way because it is stated in "fsl_pq_mdio_probe" function that:
* Some device tree nodes represent only the MII registers, and
* others represent the MAC and MII registers. The 'mii_offset' field
* contains the offset of the MII registers inside the mapped register
* space.
and that's why we have priv->map and priv->regs. So my fix goes according to the current design of the driver.

To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at
Please read the FAQ at