[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <e55dd89f-e2a6-284e-1905-bd8dc92a042d@phrozen.org>
Date: Thu, 23 Mar 2017 15:25:39 +0100
From: John Crispin <john@...ozen.org>
To: Felix Fietkau <nbd@....name>, Sean Wang <sean.wang@...iatek.com>,
Andrew Lunn <andrew@...n.ch>
Cc: mark.rutland@....com, devicetree@...r.kernel.org,
Landen.Chao@...iatek.com, f.fainelli@...il.com, keyhaede@...il.com,
vivien.didelot@...oirfairelinux.com, netdev@...r.kernel.org,
linux-kernel@...r.kernel.org, robh+dt@...nel.org,
linux-mediatek@...ts.infradead.org, objelf@...il.com,
matthias.bgg@...il.com, davem@...emloft.net
Subject: Re: [PATCH net-next v2 5/5] net-next: dsa: add dsa support for
Mediatek MT7530 switch
On 23/03/17 15:09, Felix Fietkau wrote:
> On 2017-03-23 09:06, Sean Wang wrote:
>> Hi Andrew,
>>
>> The purpose for the regmap table registered is to
>>
>> provide a way which helps us to look up a specific
>>
>> register on the switch through regmap-debugfs.
>>
>>
>> And not all ranges of register is defined
>>
>> so I only include the meaningful ones in a sparse way
>>
>> for the table.
> I think in that case it might be nice to make regmap support optional in
> order to avoid pulling in bloat on platforms that don't need it.
>
> - Felix
>
The 2 relevant platforms are mips/ralink and arm/mediatek. both require
regmap for the eth_sysctl syscon if they want to utilize the mtk_soc_eth
driver which is a prereq for mt7530. so regmap cannot be optional here.
John
>
> _______________________________________________
> Linux-mediatek mailing list
> Linux-mediatek@...ts.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-mediatek
Powered by blists - more mailing lists