netdev - Re: [PATCH 2/5] temac: dma init for Virtex4

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <fa686aa41002221423g74349c60k7602f47b9e946018@mail.gmail.com>
Date:	Mon, 22 Feb 2010 15:23:40 -0700
From:	Grant Likely <grant.likely@...retlab.ca>
To:	gfilip@...ethz.ch
Cc:	netdev@...r.kernel.org
Subject: Re: [PATCH 2/5] temac: dma init for Virtex4

On Mon, Feb 22, 2010 at 12:06 PM,  <gfilip@...ethz.ch> wrote:
> This patch belongs to a set of patches which extends the temac driver to support Virtex4-FX. It was successfully tested on the ML403 evaluation board.
>
> Signed-off-by: Filip Gospodinov <gfilip@...ethz.ch>
> ---
>  drivers/net/ll_temac.h      |    4 ++++
>  drivers/net/ll_temac_main.c |   17 ++++++++++++++++-
>  2 files changed, 20 insertions(+), 1 deletions(-)
>
> diff --git a/drivers/net/ll_temac.h b/drivers/net/ll_temac.h
> index 95dd650..51824a8 100644
> --- a/drivers/net/ll_temac.h
> +++ b/drivers/net/ll_temac.h
> @@ -383,7 +383,11 @@ struct temac_local {
>
>        /* IO registers and IRQs */
>        void __iomem *regs;
> +#ifdef CONFIG_XILINX_VIRTEX_4_FX
> +       void __iomem *dma_regs;
> +#else
>        dcr_host_t sdma_dcrs;
> +#endif

Hi Filip,

Rather than using a CONFIG symbol to select between MMIO and DCR
modes, you should look at how this patch implemented it:

http://www.gossamer-threads.com/lists/linux/kernel/1184834?page=last

John Tyner's approach is pretty good, but it needs a bit more work
before merging and he is no longer working on a virtex platform so he
isn't planning to finish it.  Basically, there is no reason for the
driver to have to choose at compile time whether DCR or MMIO will be
used.

g.

>        int tx_irq;
>        int rx_irq;
>        int emac_num;
> diff --git a/drivers/net/ll_temac_main.c b/drivers/net/ll_temac_main.c
> index a8522bd..0d4b1c5 100644
> --- a/drivers/net/ll_temac_main.c
> +++ b/drivers/net/ll_temac_main.c
> @@ -812,7 +812,6 @@ temac_of_probe(struct of_device *op, const struct of_device_id *match)
>        struct net_device *ndev;
>        const void *addr;
>        int size, rc = 0;
> -       unsigned int dcrs;
>
>        /* Init network device structure */
>        ndev = alloc_etherdev(sizeof(*lp));
> @@ -862,6 +861,21 @@ temac_of_probe(struct of_device *op, const struct of_device_id *match)
>                goto nodev;
>        }
>
> +#ifdef CONFIG_XILINX_VIRTEX_4_FX
> +       unsigned int ds;
> +       const u32 *dr = of_get_property(np, "reg", &ds);
> +       if (dr == NULL || ds & 1 || 0 >= ds ) {
> +               dev_err(&op->dev, "could not get DMA register address\n");
> +               goto nodev;
> +       }
> +       lp->dma_regs = (u32) ioremap(*dr, 4096);
> +       if (!lp->dma_regs) {
> +               dev_err(&op->dev, "could not get DMA virtual address\n");
> +               goto nodev;
> +       }
> +       dev_dbg(&op->dev, "DMA base: %x\n", lp->dma_regs);
> +#else  /*CONFIG_XILINX_VIRTEX_4_FX*/
> +       unsigned int dcrs;
>        dcrs = dcr_resource_start(np, 0);
>        if (dcrs == 0) {
>                dev_err(&op->dev, "could not get DMA register address\n");
> @@ -869,6 +883,7 @@ temac_of_probe(struct of_device *op, const struct of_device_id *match)
>        }
>        lp->sdma_dcrs = dcr_map(np, dcrs, dcr_resource_len(np, 0));
>        dev_dbg(&op->dev, "DCR base: %x\n", dcrs);
> +#endif /*CONFIG_XILINX_VIRTEX_4_FX*/'
>
>        lp->rx_irq = irq_of_parse_and_map(np, 0);
>        lp->tx_irq = irq_of_parse_and_map(np, 1);
> --
> 1.6.4.4
>
>



-- 
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html