Hi Kumar,
I'm using the 3.0.3 kernel on an MPC8308 and utilizing the spi_fsl_spi
driver to talk with an Cypress NvRAM device. I've gotten that working
now, but I've come across something I don't understand in the driver and
I'm not sure if it's just me or if there's a bug. My issue relates to
(This time with a subject line, sorry)
Hi,
I'm using the 3.0.3 kernel on an MPC8308 and have turned on GPIO support
(CONFIG_GPIOLIB = Y) because the SPI sub-system needed to use it for the
GPIO pin I'm using as a CS to a NvRAM part. I also have some jumpers on
the processor GPIO pins and I th
Hi,
I'm using the 3.0.3 kernel on an MPC8308 and have turned on GPIO support
(CONFIG_GPIOLIB = Y) because the SPI sub-system needed to use it for the
GPIO pin I'm using as a CS to a NvRAM part. I also have some jumpers on
the processor GPIO pins and I thought it would be really slick to use th
On Thu, 2012-01-26 at 14:30 -0800, Dave Hansen wrote:
> On 01/26/2012 01:39 PM, Benjamin Herrenschmidt wrote:
> > Can you explain to me a bit more the whole business in this patch set
> > about doing kmap_atomic() vs. manually trying to populate the PTEs ?
>
> They're compressing pages and the al
On 01/26/2012 01:39 PM, Benjamin Herrenschmidt wrote:
> Can you explain to me a bit more the whole business in this patch set
> about doing kmap_atomic() vs. manually trying to populate the PTEs ?
They're compressing pages and the allocator is trying getting very poor
packing of compressed pages
On Thu, 2012-01-26 at 08:41 -0600, Brian King wrote:
> CC'ing linuxppc-dev...
>
>
> On 01/26/2012 08:18 AM, Seth Jennings wrote:
> > Hey Dave,
> >
> > So I submitted the zsmalloc patches to lkml at the beginning
> > of the year
> >
> > https://lkml.org/lkml/2012/1/9/389
> >
> > I found there a
As we agreed during our discussion about adding DMA Engine support for RapidIO
subsystem, RapidIO and similar clients may benefit from adding an extra context
parameter to device_prep_slave_sg() callback.
See https://lkml.org/lkml/2011/10/24/275 for more details.
Adding the context parameter will
On Wed, Jan 25, 2012 at 11:51 AM, Rob Herring wrote:
> On 01/25/2012 08:13 AM, Cousson, Benoit wrote:
>> On 1/23/2012 10:53 PM, Rob Herring wrote:
>>> On 01/23/2012 03:07 PM, Grant Likely wrote:
Hey everyone,
Here's the second RFC for the irq_domain patches. I could use some
>
On Thu, 2012-01-26 at 13:00 -0800, Ira W. Snyder wrote:
>
> @@ -970,7 +984,13 @@ static ssize_t data_en_show(struct device *dev, struct
> device_attribute *attr,
> char *buf)
> {
> struct fpga_device *priv = dev_get_drvdata(dev);
> - return snprintf(buf,
When the system is under heavy load, we occasionally saw a problem where
the system would get a legitimate interrupt when they should be
disabled.
This was caused by the data_dma_cb() DMA callback unconditionally
re-enabling FPGA interrupts even when data dumping is disabled. When
data dumping was
Lockdep occasionally complains with the message:
INFO: HARDIRQ-safe -> HARDIRQ-unsafe lock order detected
This is caused by calling videobuf_dma_unmap() under spin_lock_irq(). To
fix the warning, we drop the lock before unmapping and freeing the
buffer.
Signed-off-by: Ira W. Snyder
Cc: Benjamin
The mpc8349ea has been observed to generate spurious end of segments
interrupts despite the fact that they are not enabled by this driver.
Check for them and ignore them to avoid a kernel error message.
Signed-off-by: Ira W. Snyder
Cc: Dan Williams
---
drivers/dma/fsldma.c | 10 ++
1
Norbert,
>
> ok, then I don't know.
>
> I doubt this is a spidev or FSP SPI driver problem though.
>
> Questions like:
>
> Could it be a HW problem ?
> Is the correct SPI mode used ?
> Does it work in u-boot ?
>
> Come to mind in a situation like this.
>
Thanks for the suggestions. I final
On Thu, Jan 26, 2012 at 7:50 AM, Rob Herring wrote:
> On 01/25/2012 11:59 AM, Grant Likely wrote:
>> On Tue, Jan 24, 2012 at 10:35 PM, Grant Likely
>> wrote:
>>> On Tue, Jan 24, 2012 at 6:50 PM, Rob Herring wrote:
On 01/24/2012 06:18 PM, Grant Likely wrote:
> Rather than havin
Hi Bruce,
On 01/25/12 20:49, bruce_leon...@selinc.com wrote:
.
.
.
Thanks for the reply. Yes I did find spidev_fdx.c and in fact copied it
for my tests. I still see SPICLK active only during the time the 8308 is
sending data (read cmd + address). Nothing happens with the clock after
that whe
On 01/25/2012 11:59 AM, Grant Likely wrote:
> On Tue, Jan 24, 2012 at 10:35 PM, Grant Likely
> wrote:
>> On Tue, Jan 24, 2012 at 6:50 PM, Rob Herring wrote:
>>>
>>>
>>> On 01/24/2012 06:18 PM, Grant Likely wrote:
Rather than having each interrupt controller driver creating its own barely
>>>
CC'ing linuxppc-dev...
On 01/26/2012 08:18 AM, Seth Jennings wrote:
> Hey Dave,
>
> So I submitted the zsmalloc patches to lkml at the beginning
> of the year
>
> https://lkml.org/lkml/2012/1/9/389
>
> I found there are two functions Nitin used in the mapping
> functions that are not supported
On Wed, Jan 25, 2012 at 3:53 PM, Mark Salter wrote:
> On Mon, 2012-01-23 at 14:07 -0700, Grant Likely wrote:
>> Hey everyone,
>>
>> Here's the second RFC for the irq_domain patches. I could use some
>> help testing now. I still expect there will be a few bugs. The
>> series is based on v3.3-rc1
2012/1/10 Shi Xuelin-B29237 :
> Hello Dan Williams,
>
> Do you have any comment about this patch?
Hi, sorrry for the delay.
>
> Thanks,
> Forrest
>
> -Original Message-
> From: Shi Xuelin-B29237
> Sent: 2011年12月27日 14:31
> To: vinod.k...@intel.com; dan.j.willi...@intel.com;
> linuxppc-de
19 matches
Mail list logo
