From: Keerthy <j-keerthy@ti.com>
To: Suman Anna <s-anna@ti.com>,
"daniel.lezcano@linaro.org" <daniel.lezcano@linaro.org>,
"thierry.reding@gmail.com" <thierry.reding@gmail.com>,
"tony@atomide.com" <tony@atomide.com>,
"aaro.koskinen@iki.fi" <aaro.koskinen@iki.fi>
Cc: "linux-pwm@vger.kernel.org" <linux-pwm@vger.kernel.org>,
"ladis@linux-mips.org" <ladis@linux-mips.org>,
"narmstrong@baylibre.com" <narmstrong@baylibre.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Kristo, Tero" <t-kristo@ti.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"sebastian.reichel@collabora.co.uk"
<sebastian.reichel@collabora.co.uk>,
"Strashko, Grygorii" <grygorii.strashko@ti.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Claudiu.Beznea@microchip.com" <Claudiu.Beznea@microchip.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v7 5/9] dmtimer: Add timer ops to the platform data structure
Date: Wed, 14 Feb 2018 10:51:01 +0530 [thread overview]
Message-ID: <23a83979-e0d9-85b6-5a34-1c293362420e@ti.com> (raw)
In-Reply-To: <c7edf8b6-6b27-692a-813f-13c86f988831@ti.com>
On Tuesday 13 February 2018 08:16 AM, Suman Anna wrote:
> On 01/09/2018 12:23 AM, J, KEERTHY wrote:
>> Add timer ops to the platform data structure
>>
>> Signed-off-by: Keerthy <j-keerthy@ti.com>
>> Reviewed-by: Sebastian Reichel <sebastian.reichel@collabora.co.uk>
>> Tested-by: Ladislav Michl <ladis@linux-mips.org>
>> ---
>> include/linux/platform_data/dmtimer-omap.h | 38 ++++++++++++++++++++++++++++++
>> 1 file changed, 38 insertions(+)
>>
>> diff --git a/include/linux/platform_data/dmtimer-omap.h
>> b/include/linux/platform_data/dmtimer-omap.h
>> index a19b78d..a3e1794 100644
>> --- a/include/linux/platform_data/dmtimer-omap.h
>> +++ b/include/linux/platform_data/dmtimer-omap.h
>> @@ -20,12 +20,50 @@
>> #ifndef __PLATFORM_DATA_DMTIMER_OMAP_H__
>> #define __PLATFORM_DATA_DMTIMER_OMAP_H__
>>
>> +struct omap_dm_timer_ops {
>> + struct omap_dm_timer *(*request_by_node)(struct device_node *np);
>> + struct omap_dm_timer *(*request_specific)(int timer_id);
>> + struct omap_dm_timer *(*request)(void);
>> +
>> + int (*free)(struct omap_dm_timer *timer);
>> +
>> + void (*enable)(struct omap_dm_timer *timer);
>> + void (*disable)(struct omap_dm_timer *timer);
>> +
>> + int (*get_irq)(struct omap_dm_timer *timer);
>> + int (*set_int_enable)(struct omap_dm_timer *timer,
>> + unsigned int value);
>> + int (*set_int_disable)(struct omap_dm_timer *timer, u32 mask);
>> +
>> + struct clk *(*get_fclk)(struct omap_dm_timer *timer);
>> +
>> + int (*start)(struct omap_dm_timer *timer);
>> + int (*stop)(struct omap_dm_timer *timer);
>> + int (*set_source)(struct omap_dm_timer *timer, int source);
>> +
>> + int (*set_load)(struct omap_dm_timer *timer, int autoreload,
>> + unsigned int value);
>> + int (*set_match)(struct omap_dm_timer *timer, int enable,
>> + unsigned int match);
>> + int (*set_pwm)(struct omap_dm_timer *timer, int def_on,
>> + int toggle, int trigger);
>> + int (*set_prescaler)(struct omap_dm_timer *timer, int prescaler);
>> +
>> + unsigned int (*read_counter)(struct omap_dm_timer *timer);
>> + int (*write_counter)(struct omap_dm_timer *timer,
>> + unsigned int value);
>> + unsigned int (*read_status)(struct omap_dm_timer *timer);
>> + int (*write_status)(struct omap_dm_timer *timer,
>> + unsigned int value);
>> +};
>> +
>> struct dmtimer_platform_data {
>> /* set_timer_src - Only used for OMAP1 devices */
>> int (*set_timer_src)(struct platform_device *pdev, int source);
> Have you looked into collapsing this into the set_source() option above
> for OMAP1? Looks like the only reason the pdev is needed is for
> retrieving the pdev id, which is also stored in the omap_dm_timer structure?
I would prefer not to touch the mach-omap1 part as part of this
migration series. I will revisit this once the migration is done.
>
>> u32 timer_capability;
>> u32 timer_errata;
>> int (*get_context_loss_count)(struct device *);
>> + struct omap_dm_timer_ops *timer_ops;
>
> Any reason why this is not a const? We don't expect this to change right.
Yes this can be.
>
> regards
> Suman
>
>> };
>>
>> #endif /* __PLATFORM_DATA_DMTIMER_OMAP_H__ */
>> --
>> 1.9.1
>>
>>
>> _______________________________________________
>> linux-arm-kernel mailing list
>> linux-arm-kernel@lists.infradead.org
>> http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
>>
>
next prev parent reply other threads:[~2018-02-14 5:21 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-09 6:22 [PATCH v7 0/9] omap: dmtimer: Move driver out of plat-omap Keerthy
2018-01-09 6:22 ` [PATCH v7 1/9] clocksource: dmtimer: Remove all the exports Keerthy
2018-01-09 6:23 ` [PATCH v7 2/9] arm: omap: timer: Wrap the inline functions under OMAP2PLUS define Keerthy
2018-01-09 9:19 ` Sebastian Reichel
2018-01-09 6:23 ` [PATCH v7 3/9] arm: omap: Move dmtimer.h out of plat-omap Keerthy
2018-02-13 2:06 ` Suman Anna
2018-02-13 15:09 ` Tony Lindgren
2018-02-14 4:11 ` Keerthy
2018-02-14 4:50 ` Keerthy
2018-02-14 18:59 ` Tony Lindgren
2018-01-09 6:23 ` [PATCH v7 4/9] arm: OMAP: Move dmtimer driver out of plat-omap to drivers under clocksource Keerthy
2018-02-13 2:24 ` Suman Anna
2018-02-14 5:09 ` Keerthy
2018-01-09 6:23 ` [PATCH v7 5/9] dmtimer: Add timer ops to the platform data structure Keerthy
2018-02-13 2:46 ` Suman Anna
2018-02-14 5:21 ` Keerthy [this message]
2018-01-09 6:23 ` [PATCH v7 6/9] clocksource: dmtimer: Populate the timer ops to the pdata Keerthy
2018-01-09 6:23 ` [PATCH v7 7/9] clocksource: timer-dm: Hook device platform data if not already assigned Keerthy
2018-01-09 9:19 ` Sebastian Reichel
2018-01-09 6:23 ` [PATCH v7 8/9] pwm: pwm-omap-dmtimer: Adapt driver to utilize dmtimer pdata ops Keerthy
2018-01-09 6:23 ` [PATCH v7 9/9] arm: omap: pdata-quirks: Remove unused timer pdata Keerthy
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=23a83979-e0d9-85b6-5a34-1c293362420e@ti.com \
--to=j-keerthy@ti.com \
--cc=Claudiu.Beznea@microchip.com \
--cc=aaro.koskinen@iki.fi \
--cc=daniel.lezcano@linaro.org \
--cc=grygorii.strashko@ti.com \
--cc=ladis@linux-mips.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=narmstrong@baylibre.com \
--cc=robh+dt@kernel.org \
--cc=s-anna@ti.com \
--cc=sebastian.reichel@collabora.co.uk \
--cc=t-kristo@ti.com \
--cc=thierry.reding@gmail.com \
--cc=tony@atomide.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®