[Meego-kernel] [PATCH 2/5] used id_table method to register for multiple modems instead of multiple calls to spi_register_driver

[Gorby, Russ]

If I understand correctly you're suggesting that the FW provide a "use_dma" indication to the protocol driver that it uses to determine (instead of the modem type) whether it need to allocate DMA-able buffers or not. 

I can certainly suggest that to the FW team but I have no guarantee they'll do it in any timely fashion. I'll comment a FIXME for now if that's sufficient.

>-----Original Message-----
>From: Alan Cox [mailto:alan at linux.intel.com]
>Sent: Wednesday, November 03, 2010 2:20 PM
>To: Gorby, Russ
>Cc: meego-kernel at meego.com
>Subject: Re: [Meego-kernel] [PATCH 2/5] used id_table method to register
>for multiple modems instead of multiple calls to spi_register_driver
>
>> The problem here is that the same protocol driver on different
>> platforms uses a different controller driver that has different
>> requirements. We're using the modem type to differentiate platforms.
>
>Well how about using the platform type to differentiate platforms ?
>
>Even if the SFI layer glue does it the right thing to do is to pass a
>"use dma" flag to indicate what the real condition is here.