From: Mike Dunn <mikedunn@newsguy.com>
To: Marek Vasut <marex@denx.de>
Cc: linux-arm-kernel@lists.infradead.org, linux-pwm@vger.kernel.org,
devicetree@vger.kernel.org, Rob Herring <rob.herring@calxeda.com>,
Thierry Reding <thierry.reding@gmail.com>,
Haojian Zhuang <haojian.zhuang@linaro.org>,
Grant Likely <grant.likely@linaro.org>,
Robert Jarzmik <robert.jarzmik@free.fr>
Subject: Re: [PATCH] pwm: pxa: add device tree support to pwm driver
Date: Thu, 05 Sep 2013 09:07:50 -0700 [thread overview]
Message-ID: <5228AC56.6020200@newsguy.com> (raw)
In-Reply-To: <201309051734.40570.marex@denx.de>
On 09/05/2013 08:34 AM, Marek Vasut wrote:
>>>
[...]
>>> compatbile=marvell,pxa25x-pwm , no ? The lowest CPU with the block.
>>
>> Unless I am missing something, the compatible string does not need to
>> replicate any of the existing platform_device_id names, so wouldn't
>> "marvell,pxa" be better? Except for register mapping and the number of
>> units present on a particular pxa variant, the peripheral is software
>> compatible across all pxa processors. Plus there is the problem of the
>> 'x' wildcard in "pxa25x-pwm".
>
> So use pxa250 ?
>
> My concern is once marvell comes up with PXA1048576 which will have a different
> PWM unit, then what will be the name for this new one?
I see. OK then, pxa250 it is.
Thanks Marek,
Mike
WARNING: multiple messages have this Message-ID (diff)
From: mikedunn@newsguy.com (Mike Dunn)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH] pwm: pxa: add device tree support to pwm driver
Date: Thu, 05 Sep 2013 09:07:50 -0700 [thread overview]
Message-ID: <5228AC56.6020200@newsguy.com> (raw)
In-Reply-To: <201309051734.40570.marex@denx.de>
On 09/05/2013 08:34 AM, Marek Vasut wrote:
>>>
[...]
>>> compatbile=marvell,pxa25x-pwm , no ? The lowest CPU with the block.
>>
>> Unless I am missing something, the compatible string does not need to
>> replicate any of the existing platform_device_id names, so wouldn't
>> "marvell,pxa" be better? Except for register mapping and the number of
>> units present on a particular pxa variant, the peripheral is software
>> compatible across all pxa processors. Plus there is the problem of the
>> 'x' wildcard in "pxa25x-pwm".
>
> So use pxa250 ?
>
> My concern is once marvell comes up with PXA1048576 which will have a different
> PWM unit, then what will be the name for this new one?
I see. OK then, pxa250 it is.
Thanks Marek,
Mike
WARNING: multiple messages have this Message-ID (diff)
From: Mike Dunn <mikedunn@newsguy.com>
To: Marek Vasut <marex@denx.de>
Cc: linux-pwm@vger.kernel.org, devicetree@vger.kernel.org,
Rob Herring <rob.herring@calxeda.com>,
Thierry Reding <thierry.reding@gmail.com>,
Haojian Zhuang <haojian.zhuang@linaro.org>,
Grant Likely <grant.likely@linaro.org>,
Robert Jarzmik <robert.jarzmik@free.fr>,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH] pwm: pxa: add device tree support to pwm driver
Date: Thu, 05 Sep 2013 09:07:50 -0700 [thread overview]
Message-ID: <5228AC56.6020200@newsguy.com> (raw)
In-Reply-To: <201309051734.40570.marex@denx.de>
On 09/05/2013 08:34 AM, Marek Vasut wrote:
>>>
[...]
>>> compatbile=marvell,pxa25x-pwm , no ? The lowest CPU with the block.
>>
>> Unless I am missing something, the compatible string does not need to
>> replicate any of the existing platform_device_id names, so wouldn't
>> "marvell,pxa" be better? Except for register mapping and the number of
>> units present on a particular pxa variant, the peripheral is software
>> compatible across all pxa processors. Plus there is the problem of the
>> 'x' wildcard in "pxa25x-pwm".
>
> So use pxa250 ?
>
> My concern is once marvell comes up with PXA1048576 which will have a different
> PWM unit, then what will be the name for this new one?
I see. OK then, pxa250 it is.
Thanks Marek,
Mike
next prev parent reply other threads:[~2013-09-05 16:07 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-03 19:23 [PATCH] pwm: pxa: add device tree support to pwm driver Mike Dunn
2013-09-03 19:23 ` Mike Dunn
2013-09-03 19:23 ` Mike Dunn
2013-09-03 22:20 ` Marek Vasut
2013-09-03 22:20 ` Marek Vasut
2013-09-03 22:20 ` Marek Vasut
2013-09-04 14:23 ` Mike Dunn
2013-09-04 14:23 ` Mike Dunn
2013-09-04 14:23 ` Mike Dunn
2013-09-04 14:35 ` Marek Vasut
2013-09-04 14:35 ` Marek Vasut
2013-09-04 14:35 ` Marek Vasut
2013-09-04 15:41 ` Mike Dunn
2013-09-04 15:41 ` Mike Dunn
2013-09-04 15:41 ` Mike Dunn
2013-09-04 22:11 ` Marek Vasut
2013-09-04 22:11 ` Marek Vasut
2013-09-04 22:11 ` Marek Vasut
2013-09-05 15:24 ` Mike Dunn
2013-09-05 15:24 ` Mike Dunn
2013-09-05 15:24 ` Mike Dunn
2013-09-05 15:34 ` Marek Vasut
2013-09-05 15:34 ` Marek Vasut
2013-09-05 15:34 ` Marek Vasut
2013-09-05 16:07 ` Mike Dunn [this message]
2013-09-05 16:07 ` Mike Dunn
2013-09-05 16:07 ` Mike Dunn
2013-09-04 14:38 ` Sergei Shtylyov
2013-09-04 14:38 ` Sergei Shtylyov
2013-09-04 15:44 ` Mike Dunn
2013-09-04 15:44 ` Mike Dunn
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5228AC56.6020200@newsguy.com \
--to=mikedunn@newsguy.com \
--cc=devicetree@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=haojian.zhuang@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-pwm@vger.kernel.org \
--cc=marex@denx.de \
--cc=rob.herring@calxeda.com \
--cc=robert.jarzmik@free.fr \
--cc=thierry.reding@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.