Re: [PATCH 4/5] pwm: pwm-tipwmss: Update documentation to use empty range property

2016-03-19 Thread Rob Herring
On Mon, Mar 07, 2016 at 01:51:57PM -0600, Franklin S Cooper Jr wrote: > Since the PWMSS and its subdevices (eCAP and ePWM) use the same address > space then the range property should be empty. Update the documentation > to show the correct usage. Why does it matter? An empty ranges is generally no

Re: [PATCH 4/5] pwm: pwm-tipwmss: Update documentation to use empty range property

2016-03-19 Thread Franklin S Cooper Jr.
On 03/17/2016 11:56 AM, Franklin S Cooper Jr. wrote: > > On 03/17/2016 10:01 AM, Rob Herring wrote: >> On Mon, Mar 07, 2016 at 01:51:57PM -0600, Franklin S Cooper Jr wrote: >>> Since the PWMSS and its subdevices (eCAP and ePWM) use the same address >>> space then the range property should be empt

Re: [PATCH 4/5] pwm: pwm-tipwmss: Update documentation to use empty range property

2016-03-18 Thread Franklin S Cooper Jr.
On 03/17/2016 10:01 AM, Rob Herring wrote: > On Mon, Mar 07, 2016 at 01:51:57PM -0600, Franklin S Cooper Jr wrote: >> Since the PWMSS and its subdevices (eCAP and ePWM) use the same address >> space then the range property should be empty. Update the documentation >> to show the correct usage. >

[PATCH 4/5] pwm: pwm-tipwmss: Update documentation to use empty range property

2016-03-07 Thread Franklin S Cooper Jr
Since the PWMSS and its subdevices (eCAP and ePWM) use the same address space then the range property should be empty. Update the documentation to show the correct usage. Signed-off-by: Franklin S Cooper Jr --- Documentation/devicetree/bindings/pwm/pwm-tipwmss.txt | 12 1 file chang