On Thu, Dec 04, 2014 at 12:17:15PM +0100, Arnd Bergmann wrote:
> On Thursday 04 December 2014 11:07:46 Mark Brown wrote:
> > It's relatively common with newer companies - it's like UARTs, any
> > company that's been around for a long time will have a homebrew IP
> > already but places that don't (
On Thursday 04 December 2014 11:07:46 Mark Brown wrote:
> On Thu, Dec 04, 2014 at 10:55:55AM +0100, Arnd Bergmann wrote:
> > On Wednesday 03 December 2014 20:19:05 Mark Brown wrote:
>
> > > Not all the world uses DT, this is a DesignWare IP so it's likely to get
> > > deployed widely - potentially
On Thu, Dec 04, 2014 at 10:55:55AM +0100, Arnd Bergmann wrote:
> On Wednesday 03 December 2014 20:19:05 Mark Brown wrote:
> > Not all the world uses DT, this is a DesignWare IP so it's likely to get
> > deployed widely - potentially on PCI cards and things like that.
> It's not really new though,
On 12/04/14 07:43, rajeev kumar wrote:
> Sorry for the last blank mail.
>
> On Wed, Dec 3, 2014 at 10:09 PM, Andrew Jackson
> wrote:
>> Convert to driver to use either platform_data or device-tree for
>> configuration
>> of the device. When using device-tree, the I2S block's configuration is r
On Wednesday 03 December 2014 20:19:05 Mark Brown wrote:
> On Wed, Dec 03, 2014 at 09:13:18PM +0100, Arnd Bergmann wrote:
>
> > I don't think we even have to worry about the platform_data case here:
> > the only platform using this hardware in Linux is arm/mach-spear, and
> > it defines a device n
On 12/03/14 20:13, Arnd Bergmann wrote:
> On Wednesday 03 December 2014 16:39:08 Andrew Jackson wrote:
>> Convert to driver to use either platform_data or device-tree for
>> configuration
>> of the device. When using device-tree, the I2S block's configuration is read
>> from the relevant register
On 12/03/14 18:23, Mark Brown wrote:
> On Wed, Dec 03, 2014 at 04:39:08PM +, Andrew Jackson wrote:
>
>> Convert to driver to use either platform_data or device-tree for
>> configuration
>> of the device. When using device-tree, the I2S block's configuration is read
>> from the relevant regis
Sorry for the last blank mail.
On Wed, Dec 3, 2014 at 10:09 PM, Andrew Jackson wrote:
> Convert to driver to use either platform_data or device-tree for configuration
> of the device. When using device-tree, the I2S block's configuration is read
> from the relevant registers: this reduces the am
On Wed, Dec 3, 2014 at 10:09 PM, Andrew Jackson wrote:
> Convert to driver to use either platform_data or device-tree for configuration
> of the device. When using device-tree, the I2S block's configuration is read
> from the relevant registers: this reduces the amount of information required
>
On Wed, Dec 03, 2014 at 09:13:18PM +0100, Arnd Bergmann wrote:
> I don't think we even have to worry about the platform_data case here:
> the only platform using this hardware in Linux is arm/mach-spear, and
> it defines a device node with a binding that is similar to the one you
> document here b
On Wednesday 03 December 2014 16:39:08 Andrew Jackson wrote:
> Convert to driver to use either platform_data or device-tree for configuration
> of the device. When using device-tree, the I2S block's configuration is read
> from the relevant registers: this reduces the amount of information require
On Wed, Dec 03, 2014 at 04:39:08PM +, Andrew Jackson wrote:
> Convert to driver to use either platform_data or device-tree for configuration
> of the device. When using device-tree, the I2S block's configuration is read
> from the relevant registers: this reduces the amount of information req
12 matches
Mail list logo
