From: Sekhar Nori <nsekhar@ti.com>
To: Philip Avinash <avinashphilip@ti.com>
Cc: thierry.reding@avionic-design.de,
linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org,
davinci-linux-open-source@linux.davincidsp.com,
prakash.pm@ti.com, devicetree-discuss@lists.ozlabs.org,
linux-doc@vger.kernel.org
Subject: Re: [PATCH 1/3] pwm: davinci: Add Kconfig support for ECAP & EHRPWM devices
Date: Thu, 14 Mar 2013 17:09:04 +0530 [thread overview]
Message-ID: <5141B6D8.2050308@ti.com> (raw)
In-Reply-To: <1363257158-11615-2-git-send-email-avinashphilip@ti.com>
On 3/14/2013 4:02 PM, Philip Avinash wrote:
> Add EHRPWM and ECAP support build support for DAVINCI_DA850 platforms.
>
> Also, since DAVINCI platforms doesn't support TI-PWM-Subsystem module,
> remove the select option for CONFIG_PWM_TIPWMSS.
>
> Also, update CONFIG_PWM_TIPWMSS compiler directive appropriately in
> pwm-tipwmss.h to fix the below compiler error upon removal of
> CONFIG_PWM_TIPWMSS for Davinci platforms.
>
> drivers/pwm/pwm-tiecap.c: In function 'ecap_pwm_probe':
> drivers/pwm/pwm-tiecap.c:263:4: error: 'PWMSS_ECAPCLK_EN' undeclared
> (first use in this function)
> drivers/pwm/pwm-tiecap.c:263:4: note: each undeclared identifier
> is reported only once for each function it appears in
> drivers/pwm/pwm-tiecap.c:264:17: error: 'PWMSS_ECAPCLK_EN_ACK'
> undeclared (first use in this function)
> drivers/pwm/pwm-tiecap.c: In function 'ecap_pwm_remove':
> drivers/pwm/pwm-tiecap.c:291:49: error: 'PWMSS_ECAPCLK_STOP_REQ'
> undeclared (first use in this function)
> make[2]: *** [drivers/pwm/pwm-tiecap.o] Error 1
> make[1]: *** [drivers/pwm] Error 2
> make: *** [drivers] Error 2
>
> Signed-off-by: Philip Avinash <avinashphilip@ti.com>
> config PWM_TIECAP
> tristate "ECAP PWM support"
> - depends on SOC_AM33XX
> - select PWM_TIPWMSS
> + depends on SOC_AM33XX || ARCH_DAVINCI_DA850
Having such narrow dependencies is wrong. The same device is present on
DaVinci DA830 too. A depends on should not be required at all since the
driver should build on all architectures. But I have seen resistance to
doing that since users don't like to see configuration options totally
irrelevant for the architecture they are building for. So may be take a
middle path and do 'depends on ARCH_ARM'?
Thanks,
Sekhar
next prev parent reply other threads:[~2013-03-14 11:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-14 10:32 [PATCH 0/3] Davinci support for EHRPWM & ECAP Philip Avinash
[not found] ` <1363257158-11615-1-git-send-email-avinashphilip-l0cyMroinI0@public.gmane.org>
2013-03-14 10:32 ` [PATCH 1/3] pwm: davinci: Add Kconfig support for ECAP & EHRPWM devices Philip Avinash
2013-03-14 11:39 ` Sekhar Nori [this message]
2013-03-14 12:54 ` Philip, Avinash
2013-03-14 15:11 ` Thierry Reding
2013-03-14 10:32 ` [PATCH 2/3] pwm: pwm-tiecap: Add device-tree binding support for da850 SOC Philip Avinash
2013-03-14 11:43 ` Sekhar Nori
2013-03-14 12:54 ` Philip, Avinash
2013-03-14 15:44 ` Peter Korsgaard
2013-03-15 4:25 ` Sekhar Nori
2013-03-14 10:32 ` [PATCH 3/3] pwm: pwm-tiehrpwm: Add device tree " Philip Avinash
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=5141B6D8.2050308@ti.com \
--to=nsekhar@ti.com \
--cc=avinashphilip@ti.com \
--cc=davinci-linux-open-source@linux.davincidsp.com \
--cc=devicetree-discuss@lists.ozlabs.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-doc@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=prakash.pm@ti.com \
--cc=thierry.reding@avionic-design.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).