Because the latest shdma driver changed, it caused build error in
the spi-rspi driver. This patch fixed the build error.
Signed-off-by: Yoshihiro Shimoda
---
drivers/spi/spi-rspi.c | 56 +--
1 files changed, 34 insertions(+), 22 deletions(-)
diff --
On Wednesday 01 August 2012 08:37 PM, Guenter Roeck wrote:
> On Wed, Aug 01, 2012 at 03:06:28PM +0530, Shubhrajyoti D wrote:
>> The kfree() is taken care of by the spi core (spi_master_release() function)
>> that is called once the last reference to the underlying struct device has
>> been released
The kfree() is taken care of by the spi core (spi_master_release() function)
that is called once the last reference to the underlying struct device has
been released. So the driver need not call kfree.
Also the put was missed in some of the error handling fix the same.
There by fixing the missing
On Thu, Aug 02, 2012 at 03:37:13PM +0530, Shubhrajyoti wrote:
> On Wednesday 01 August 2012 08:37 PM, Guenter Roeck wrote:
> > On Wed, Aug 01, 2012 at 03:06:28PM +0530, Shubhrajyoti D wrote:
> >> The kfree() is taken care of by the spi core (spi_master_release()
> >> function)
> >> that is called
Dear Mark Brown,
Thanks for the review!
> On Mon, Jul 23, 2012 at 10:40:48PM +0200, Marek Vasut wrote:
> > This is slightly reworked version of the SPI driver.
> > Support for DT has been added and it's been converted
> > to queued API.
>
> Looks reasonable overall.
>
> > + bits_per_word = de
Dear Mark Brown,
> On Mon, Jul 23, 2012 at 10:40:50PM +0200, Marek Vasut wrote:
> > + /*
> > +* Small blocks can be transfered via PIO.
> > +* Measured by empiric means:
> > +*
> > +* dd if=/dev/mtdblock0 of=/dev/null bs=1024k count=1
> > +
On Thu, Aug 02, 2012 at 04:58:38PM +0200, Marek Vasut wrote:
> > It'd be nice to only keep the clocks enabled while doing transfers but
> > again totally non-essential.
> Hm, this is spread across mxs. Shawn, is there any plan for PM implementation
> for MXS ?
Take a look at s3c64xx - I did som
Dear Mark Brown,
> On Thu, Aug 02, 2012 at 04:58:38PM +0200, Marek Vasut wrote:
> > > It'd be nice to only keep the clocks enabled while doing transfers but
> > > again totally non-essential.
> >
> > Hm, this is spread across mxs. Shawn, is there any plan for PM
> > implementation for MXS ?
>
>
This reverts commit 9fdca9dfe093c76fe1ac1a09888ba9679d46996a.
Changing omap2_mcspi_init() from subsys_initcall to device_initcall broke
the display initialization on N900 when all the drivers are compiled
built-in. Display subsystem drivers need a certain initialization order
and having all of the
On Thu, Aug 2, 2012 at 5:08 PM, Aaro Koskinen wrote:
> This reverts commit 9fdca9dfe093c76fe1ac1a09888ba9679d46996a.
>
> Changing omap2_mcspi_init() from subsys_initcall to device_initcall broke
> the display initialization on N900 when all the drivers are compiled
> built-in. Display subsystem dr
On Thu, Aug 02, 2012 at 04:58:38PM +0200, Marek Vasut wrote:
> Hm, this is spread across mxs. Shawn, is there any plan for PM implementation
> for MXS ?
>
Near term, no. Long term, yes.
--
Regards,
Shawn
--
Live Secu
å大ä¼ä¸å
¬å¸æ¨ä»¬å¥½ï¼
森èå®ä¸å
¬å¸æç«äº1996å¹´ï¼æ¯ä¸å®¶éå¢å
¬å¸ãæ¬éå¢å
±æ¥æåä½å®¶ä¸å±ä¼ä¸ï¼éå广ä¸ãæ±èãä¸æµ·ãå京ãå±±ä¸çå°åºï¼æå¸å¨ä¸ææé¿è¿ç¨ä¸æ³¨é人æçå¸æ¶åå¹å
»ï¼æ¥æä¸æ¹é«ç´ è´¨çç»è¥ç®¡çå
Silences the following sparse warnings:
drivers/spi/spi-s3c64xx.c:1482:32: warning:
symbol 's3c2443_spi_port_config' was not declared. Should it be static?
drivers/spi/spi-s3c64xx.c:1489:32: warning:
symbol 's3c6410_spi_port_config' was not declared. Should it be static?
drivers/spi/spi-s3c64xx.c:1
13 matches
Mail list logo
