From: David Miller <davem@davemloft.net>
To: Mark-MC.Lee@mediatek.com
Cc: mark.rutland@arm.com, andrew@lunn.ch,
jakub.kicinski@netronome.com, devicetree@vger.kernel.org,
netdev@vger.kernel.org, sean.wang@mediatek.com,
linux-kernel@vger.kernel.org, opensource@vdorst.com,
robh+dt@kernel.org, linux-mediatek@lists.infradead.org,
john@phrozen.org, matthias.bgg@gmail.com,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH net,v3 0/3] Rework mt762x GDM setup flow
Date: Thu, 14 Nov 2019 15:13:40 -0800 (PST) [thread overview]
Message-ID: <20191114.151340.735858877920708489.davem@davemloft.net> (raw)
In-Reply-To: <20191113023844.17800-1-Mark-MC.Lee@mediatek.com>
From: MarkLee <Mark-MC.Lee@mediatek.com>
Date: Wed, 13 Nov 2019 10:38:41 +0800
> The mt762x GDM block is mainly used to setup the HW internal
> rx path from GMAC to RX DMA engine(PDMA) and the packet
> switching engine(PSE) is responsed to do the data forward
> following the GDM configuration.
>
> This patch set have three goals :
>
> 1. Integrate GDM/PSE setup operations into single function "mtk_gdm_config"
>
> 2. Refine the timing of GDM/PSE setup, move it from mtk_hw_init
> to mtk_open
>
> 3. Enable GDM GDMA_DROP_ALL mode to drop all packet during the
> stop operation
Series applied, thanks.
_______________________________________________
Linux-mediatek mailing list
Linux-mediatek@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-mediatek
prev parent reply other threads:[~2019-11-14 23:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-13 2:38 [PATCH net,v3 0/3] Rework mt762x GDM setup flow MarkLee
2019-11-13 2:38 ` [PATCH net, v3 1/3] net: ethernet: mediatek: Integrate GDM/PSE setup operations MarkLee
2019-11-13 2:38 ` [PATCH net, v3 2/3] net: ethernet: mediatek: Refine the timing of GDM/PSE setup MarkLee
2019-11-13 2:38 ` [PATCH net, v3 3/3] net: ethernet: mediatek: Enable GDM GDMA_DROP_ALL mode MarkLee
2019-11-14 23:13 ` David Miller [this message]
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=20191114.151340.735858877920708489.davem@davemloft.net \
--to=davem@davemloft.net \
--cc=Mark-MC.Lee@mediatek.com \
--cc=andrew@lunn.ch \
--cc=devicetree@vger.kernel.org \
--cc=jakub.kicinski@netronome.com \
--cc=john@phrozen.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=mark.rutland@arm.com \
--cc=matthias.bgg@gmail.com \
--cc=netdev@vger.kernel.org \
--cc=opensource@vdorst.com \
--cc=robh+dt@kernel.org \
--cc=sean.wang@mediatek.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;
as well as URLs for NNTP newsgroup(s).