On 2/26/2024 3:55 PM, Krzysztof Kozlowski wrote:
> On 22/02/2024 13:43, Yang Xiwen via B4 Relay wrote:
>> From: Yang Xiwen <forbidden405@xxxxxxxxxxx>
>>
>> The only documented SoC Hi3516DV300 does not receive any updates from 8
>> years ago. With the recent driver changes, it unlikely works for this
>> SoC anymore. Remove the binding for this SoC.
>>
>> Also it's hard to get the version number and it's unknown how the
>> version can be used. Remove them until it's really needed.
>>
>> Signed-off-by: Yang Xiwen <forbidden405@xxxxxxxxxxx>
>> ---
>> drivers/net/ethernet/hisilicon/hisi_femac.c | 4 +---
>> 1 file changed, 1 insertion(+), 3 deletions(-)
>>
>> diff --git a/drivers/net/ethernet/hisilicon/hisi_femac.c b/drivers/net/ethernet/hisilicon/hisi_femac.c
>> index eab91e011d11..9466ca9da2bb 100644
>> --- a/drivers/net/ethernet/hisilicon/hisi_femac.c
>> +++ b/drivers/net/ethernet/hisilicon/hisi_femac.c
>> @@ -990,9 +990,7 @@ static int hisi_femac_drv_resume(struct platform_device *pdev)
>> #endif
>>
>> static const struct of_device_id hisi_femac_match[] = {
>> - {.compatible = "hisilicon,hisi-femac-v1",},
>> - {.compatible = "hisilicon,hisi-femac-v2",},
>> - {.compatible = "hisilicon,hi3516cv300-femac",},
>> + {.compatible = "hisilicon,hisi-femac",},
>
> What is happening here? Removal could be justified, but then order of
> your patches is totally wrong. But that hisi-femac is a no-go or provide
> proper rationale.
I don't understand exactly... In dts, we commonly have a SoC specific
compatible string first, generic compatible string the second. e.g.
compatible = "hisilicon,hi3798mv200-perictrl", "syscon", "simple-mfd".
So i think this is recommended. Or does it mean we only need them in
dts, not in the driver? The generic driver only needs a generic
compatible "hisilicon,hisi-femac" in all?
>
> Best regards,
> Krzysztof
>
--
Best regards,
Yang Xiwen
