Re: [PATCH RFC 51/51] ARM: 7805/1: mm: change max*pfn to include the physical offset of memory

2013-08-06 Thread Russell King - ARM Linux
On Mon, Aug 05, 2013 at 10:15:11PM -0500, Rob Herring wrote: > On Thu, Aug 1, 2013 at 5:25 PM, Santosh Shilimkar > wrote: > > +/* The ARM override for dma_max_pfn() */ > > +static inline unsigned long dma_max_pfn(struct device *dev) > > +{ > > + return PHYS_PFN_OFFSET + dma_to_pfn(dev,

Re: [PATCH RFC 51/51] ARM: 7805/1: mm: change max*pfn to include the physical offset of memory

2013-08-06 Thread Russell King - ARM Linux
On Mon, Aug 05, 2013 at 10:15:11PM -0500, Rob Herring wrote: On Thu, Aug 1, 2013 at 5:25 PM, Santosh Shilimkar santosh.shilim...@ti.com wrote: +/* The ARM override for dma_max_pfn() */ +static inline unsigned long dma_max_pfn(struct device *dev) +{ + return PHYS_PFN_OFFSET +

Re: [PATCH RFC 51/51] ARM: 7805/1: mm: change max*pfn to include the physical offset of memory

2013-08-05 Thread Rob Herring
On Thu, Aug 1, 2013 at 5:25 PM, Santosh Shilimkar wrote: > Most of the kernel code assumes that max*pfn is maximum pfns because > the physical start of memory is expected to be PFN0. Since this > assumption is not true on ARM architectures, the meaning of max*pfn > is number of memory pages. This

Re: [PATCH RFC 51/51] ARM: 7805/1: mm: change max*pfn to include the physical offset of memory

2013-08-05 Thread Rob Herring
On Thu, Aug 1, 2013 at 5:25 PM, Santosh Shilimkar santosh.shilim...@ti.com wrote: Most of the kernel code assumes that max*pfn is maximum pfns because the physical start of memory is expected to be PFN0. Since this assumption is not true on ARM architectures, the meaning of max*pfn is number

[PATCH RFC 51/51] ARM: 7805/1: mm: change max*pfn to include the physical offset of memory

2013-08-01 Thread Santosh Shilimkar
Most of the kernel code assumes that max*pfn is maximum pfns because the physical start of memory is expected to be PFN0. Since this assumption is not true on ARM architectures, the meaning of max*pfn is number of memory pages. This is done to keep drivers happy which are making use of of these

[PATCH RFC 51/51] ARM: 7805/1: mm: change max*pfn to include the physical offset of memory

2013-08-01 Thread Santosh Shilimkar
Most of the kernel code assumes that max*pfn is maximum pfns because the physical start of memory is expected to be PFN0. Since this assumption is not true on ARM architectures, the meaning of max*pfn is number of memory pages. This is done to keep drivers happy which are making use of of these