From: Frank Li <lznuaa@gmail.com>
To: "Lothar Waßmann" <LW@karo-electronics.de>
Cc: Frank Li <Frank.Li@freescale.com>,
netdev@vger.kernel.org, s.hauer@pengutronix.de,
shawn.guo@linaro.org, davem@davemloft.net,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 1/1 net-next] NET: FEC: dynamtic check DMA desc buff type
Date: Sun, 30 Dec 2012 09:01:31 +0800 [thread overview]
Message-ID: <CAHrpEqS42MNXF011sROJOxWE7N66Roy_Bb5TC+CM5keFMf6D+A@mail.gmail.com> (raw)
In-Reply-To: <20701.45196.361432.80622@ipc1.ka-ro>
2012/12/28 Lothar Waßmann <LW@karo-electronics.de>:
> Frank Li writes:
>> MX6 and mx28 support enhanced DMA descript buff to support 1588
>> ptp. But MX25, MX3x, MX5x can't support enhanced DMA descript buff.
>> Check fec type and choose correct DAM descript buff type.
> ^^^
> s/DAM/DMA/
> s/descript/descriptor/g
>
> [...]
>> diff --git a/drivers/net/ethernet/freescale/fec.c b/drivers/net/ethernet/freescale/fec.c
>> index 0704bca..290f91c 100644
>> --- a/drivers/net/ethernet/freescale/fec.c
>> +++ b/drivers/net/ethernet/freescale/fec.c
>> @@ -76,6 +76,8 @@
>> #define FEC_QUIRK_USE_GASKET (1 << 2)
>> /* Controller has GBIT support */
>> #define FEC_QUIRK_HAS_GBIT (1 << 3)
>> +/* Controller has extend desc buffer */
>> +#define FEC_QUICK_HAS_BUFDESC_EX (1 << 4)
> ^^^^^
> As Sascha has already pointed out, this should be 'QUIRK' rather than
> 'QUICK' (like in the preceeding lines)!
>
>> static struct platform_device_id fec_devtype[] = {
>> {
>> @@ -93,7 +95,8 @@ static struct platform_device_id fec_devtype[] = {
>> .driver_data = FEC_QUIRK_ENET_MAC | FEC_QUIRK_SWAP_FRAME,
>> }, {
>> .name = "imx6q-fec",
>> - .driver_data = FEC_QUIRK_ENET_MAC | FEC_QUIRK_HAS_GBIT,
>> + .driver_data = FEC_QUIRK_ENET_MAC | FEC_QUIRK_HAS_GBIT |
>> + FEC_QUICK_HAS_BUFDESC_EX,
> ^^^^^
> same as above.
>
> [...]
>> @@ -1574,6 +1617,8 @@ fec_probe(struct platform_device *pdev)
>> fep->pdev = pdev;
>> fep->dev_id = dev_id++;
>>
>> + fep->bufdesc_ex = 0;
>> +
>> if (!fep->hwp) {
>> ret = -ENOMEM;
>> goto failed_ioremap;
>> @@ -1628,19 +1673,19 @@ fec_probe(struct platform_device *pdev)
>> goto failed_clk;
>> }
>>
>> -#ifdef CONFIG_FEC_PTP
>> fep->clk_ptp = devm_clk_get(&pdev->dev, "ptp");
>> + fep->bufdesc_ex =
>> + pdev->id_entry->driver_data & FEC_QUICK_HAS_BUFDESC_EX;
> ^^^^^
> same as above.
Okay, I will fix it after new year holiday.
>
>
> Lothar Waßmann
> --
> ___________________________________________________________
>
> Ka-Ro electronics GmbH | Pascalstraße 22 | D - 52076 Aachen
> Phone: +49 2408 1402-0 | Fax: +49 2408 1402-10
> Geschäftsführer: Matthias Kaussen
> Handelsregistereintrag: Amtsgericht Aachen, HRB 4996
>
> www.karo-electronics.de | info@karo-electronics.de
> ___________________________________________________________
prev parent reply other threads:[~2012-12-30 1:01 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-28 6:29 [PATCH v2 1/1 net-next] NET: FEC: dynamtic check DMA desc buff type Frank Li
2012-12-28 14:45 ` Lothar Waßmann
2012-12-30 1:01 ` Frank Li [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=CAHrpEqS42MNXF011sROJOxWE7N66Roy_Bb5TC+CM5keFMf6D+A@mail.gmail.com \
--to=lznuaa@gmail.com \
--cc=Frank.Li@freescale.com \
--cc=LW@karo-electronics.de \
--cc=davem@davemloft.net \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=netdev@vger.kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawn.guo@linaro.org \
/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).