From: John Crispin <john@phrozen.org>
To: Felix Fietkau <nbd@nbd.name>, Sean Wang <sean.wang@mediatek.com>,
Andrew Lunn <andrew@lunn.ch>
Cc: mark.rutland@arm.com, devicetree@vger.kernel.org,
Landen.Chao@mediatek.com, f.fainelli@gmail.com,
keyhaede@gmail.com, vivien.didelot@savoirfairelinux.com,
netdev@vger.kernel.org, linux-kernel@vger.kernel.org,
robh+dt@kernel.org, linux-mediatek@lists.infradead.org,
objelf@gmail.com, matthias.bgg@gmail.com, davem@davemloft.net
Subject: Re: [PATCH net-next v2 5/5] net-next: dsa: add dsa support for Mediatek MT7530 switch
Date: Thu, 23 Mar 2017 15:25:39 +0100 [thread overview]
Message-ID: <e55dd89f-e2a6-284e-1905-bd8dc92a042d@phrozen.org> (raw)
In-Reply-To: <c9ffd691-b959-1e19-5bea-6386b816bac2@nbd.name>
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@lists.infradead.org
> http://lists.infradead.org/mailman/listinfo/linux-mediatek
next prev parent reply other threads:[~2017-03-23 14:26 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-21 9:35 [PATCH net-next v2 0/5] net-next: dsa: add Mediatek MT7530 support sean.wang
2017-03-21 9:35 ` [PATCH net-next v2 1/5] dt-bindings: net: dsa: add Mediatek MT7530 binding sean.wang
2017-03-24 16:16 ` Rob Herring
2017-03-21 9:35 ` [PATCH net-next v2 2/5] net-next: dsa: add Mediatek tag RX/TX handler sean.wang
2017-03-21 9:35 ` [PATCH net-next v2 3/5] net-next: ethernet: mediatek: add CDM able to recognize the tag for DSA sean.wang
2017-03-22 17:43 ` Andrew Lunn
2017-03-22 18:23 ` Florian Fainelli
2017-03-21 9:35 ` [PATCH net-next v2 4/5] net-next: ethernet: mediatek: add device_node of GMAC pointing into the netdev instance sean.wang
2017-03-22 18:18 ` Andrew Lunn
2017-03-22 18:23 ` Florian Fainelli
2017-03-21 9:35 ` [PATCH net-next v2 5/5] net-next: dsa: add dsa support for Mediatek MT7530 switch sean.wang
2017-03-22 18:30 ` Andrew Lunn
2017-03-22 18:39 ` Florian Fainelli
2017-03-28 5:51 ` Sean Wang
2017-03-23 7:22 ` Andrew Lunn
2017-03-23 8:06 ` Sean Wang
2017-03-23 14:09 ` Felix Fietkau
2017-03-23 14:25 ` John Crispin [this message]
2017-03-23 14:30 ` Felix Fietkau
2017-03-24 7:53 ` Andrew Lunn
2017-03-24 14:02 ` Andrew Lunn
2017-03-28 6:05 ` Sean Wang
2017-03-24 14:19 ` Andrew Lunn
2017-03-28 6:50 ` Sean Wang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=e55dd89f-e2a6-284e-1905-bd8dc92a042d@phrozen.org \
--to=john@phrozen.org \
--cc=Landen.Chao@mediatek.com \
--cc=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=f.fainelli@gmail.com \
--cc=keyhaede@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=nbd@nbd.name \
--cc=netdev@vger.kernel.org \
--cc=objelf@gmail.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.com \
--cc=vivien.didelot@savoirfairelinux.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome