[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <6ae64f49-5ab9-0b37-ae2c-5519c21a5d73@collabora.com>
Date: Wed, 28 Sep 2022 15:35:41 +0200
From: AngeloGioacchino Del Regno
<angelogioacchino.delregno@...labora.com>
To: Chunfeng Yun <chunfeng.yun@...iatek.com>,
Vinod Koul <vkoul@...nel.org>
Cc: Kishon Vijay Abraham I <kishon@...com>,
Matthias Brugger <matthias.bgg@...il.com>,
linux-arm-kernel@...ts.infradead.org,
linux-mediatek@...ts.infradead.org, linux-phy@...ts.infradead.org,
linux-kernel@...r.kernel.org, Eddie Hung <eddie.hung@...iatek.com>,
Tianping Fang <tianping.fang@...iatek.com>
Subject: Re: [PATCH 2/2] phy: mediatek: tphy: add debugfs files
Il 28/09/22 11:30, Chunfeng Yun ha scritto:
> These debugfs files are mainly used to make eye diagram test easier,
> especially helpful to do HQA test for a new IC without efuse enabled.
>
> Signed-off-by: Chunfeng Yun <chunfeng.yun@...iatek.com>
Even though this won't be interesting for the vast majority of the people
out there (the users!), it's still nice to have it for IC testing performed
directly on upstream, as that opens new possibilities for you and ODMs/OEMs,
so I agree on getting that code upstreamed.
For that reason, I think that the best approach for this one would be to
enclose it in a configuration option like CONFIG_PHY_MTK_TPHY_DEBUGFS or
CONFIG_PHY_MTK_TPHY_DEBUG, so that this very low level debugging code
doesn't end up in end-user builds, as that may, in some cases, be even
dangerous.
Regards,
Angelo
Powered by blists - more mailing lists