[<prev] [next>] [day] [month] [year] [list]
Message-ID: <5192099B.4000203@ti.com>
Date: Tue, 14 May 2013 12:53:31 +0300
From: Illia Smyrnov <x0194613@...com>
To: Matthias Brugger <matthias.bgg@...il.com>
CC: Grant Likely <grant.likely@...retlab.ca>,
Rob Herring <rob.herring@...xeda.com>,
Rob Landley <rob@...dley.net>, Daniel Mack <zonque@...il.com>,
Enric Balletbo Serra <eballetbo@...il.com>,
Javier Martinez Canillas <martinez.javier@...il.com>,
<devicetree-discuss@...ts.ozlabs.org>, <linux-doc@...r.kernel.org>,
<linux-kernel@...r.kernel.org>,
<spi-devel-general@...ts.sourceforge.net>,
<linux-omap@...r.kernel.org>, <ezequiel.garcia@...e-electrons.com>
Subject: Re: [PATCH] spi: spi-omap2-mcspi.c: Add dts for slave device configuration.
> @@ -745,6 +781,11 @@ static int omap2_mcspi_setup_transfer(struct
> spi_device *spi,
> mcspi = spi_master_get_devdata(spi->master);
> spi_cntrl = mcspi->master;
>
> + if (!cd && spi->dev.of_node) {
> + cd = omap2_mcspi_get_slave_ctrldata(spi);
> + spi->controller_data = cd;
Here you call omap2_mcspi_get_slave_ctrldata function that allocate
memory for cd structure, but this memory never freed.
Also, why do you read DT data in omap2_mcspi_setup_transfer function?
Under certain conditions the omap2_mcspi_setup_transfer function may be
calling for each transfer and each call it will check (!cd &&
spi->dev.of_node) condition.
Consider to move DT data read code from omap2_mcspi_setup_transfer to
omap2_mcspi_setup function and free spi->controller_data pointer in
omap2_mcspi_cleanup function.
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists