From: Thierry Reding <thierry.reding@gmail.com>
To: Lee Jones <lee.jones@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, kernel@stlinux.com,
maxime.coquelin@st.com, linux-pwm@vger.kernel.org,
ajitpal.singh@st.com
Subject: Re: [RESEND 07/11] pwm: sti: Initialise PWM Capture channel data
Date: Tue, 12 Apr 2016 12:29:26 +0200 [thread overview]
Message-ID: <20160412102926.GC18882@ulmo.ba.sec> (raw)
In-Reply-To: <1456932729-9667-8-git-send-email-lee.jones@linaro.org>
[-- Attachment #1: Type: text/plain, Size: 1797 bytes --]
On Wed, Mar 02, 2016 at 03:32:05PM +0000, Lee Jones wrote:
[...]
> +struct sti_cpt_data {
> + u32 snapshot[3];
> + int index;
> + int gpio;
On a side-note, this should probably use struct gpio_desc * instead of
an integer along with the gpiod_*() APIs for the GPIO handling.
> + struct mutex lock;
> + wait_queue_head_t wait;
> +};
> +
> struct sti_pwm_compat_data {
> const struct reg_field *reg_fields;
> - unsigned int num_chan;
> + unsigned int pwm_num_chan;
> + unsigned int cpt_num_chan;
> unsigned int max_pwm_cnt;
> unsigned int max_prescale;
> };
> @@ -77,6 +90,7 @@ struct sti_pwm_chip {
> struct clk *cpt_clk;
> struct regmap *regmap;
> struct sti_pwm_compat_data *cdata;
> + struct sti_cpt_data *cpt_data[STI_MAX_CPT_CHANS];
The PWM subsystem allows chip-specific data to be associated with each
PWM device. I'd prefer if the driver used it rather than homebrew some-
thing similar. See pwm_set_chip_data() and pwm_get_chip_data().
> @@ -389,6 +411,19 @@ static int sti_pwm_probe(struct platform_device *pdev)
> if (ret)
> return ret;
>
> + for (chan = 0; chan < cdata->cpt_num_chan; chan++) {
> + struct sti_cpt_data *data;
> +
> + data = devm_kzalloc(dev, sizeof(*data), GFP_KERNEL);
> + if (!data)
> + return -ENOMEM;
> +
> + init_waitqueue_head(&data->wait);
> + mutex_init(&data->lock);
> + data->gpio = of_get_named_gpio(np, "capture-gpios", chan);
> + pc->cpt_data[chan] = data;
Converting to per-PWM data should be as simple as turning this last line
into:
pwm_set_chip_data(pc->chip.pwms[chan], data);
Also I don't see any cleanup for this data in the driver. The memory for
the per-PWM data should be freed by devm_*() infrastructure, but how
will the GPIO be released?
Thierry
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
WARNING: multiple messages have this Message-ID (diff)
From: thierry.reding@gmail.com (Thierry Reding)
To: linux-arm-kernel@lists.infradead.org
Subject: [RESEND 07/11] pwm: sti: Initialise PWM Capture channel data
Date: Tue, 12 Apr 2016 12:29:26 +0200 [thread overview]
Message-ID: <20160412102926.GC18882@ulmo.ba.sec> (raw)
In-Reply-To: <1456932729-9667-8-git-send-email-lee.jones@linaro.org>
On Wed, Mar 02, 2016 at 03:32:05PM +0000, Lee Jones wrote:
[...]
> +struct sti_cpt_data {
> + u32 snapshot[3];
> + int index;
> + int gpio;
On a side-note, this should probably use struct gpio_desc * instead of
an integer along with the gpiod_*() APIs for the GPIO handling.
> + struct mutex lock;
> + wait_queue_head_t wait;
> +};
> +
> struct sti_pwm_compat_data {
> const struct reg_field *reg_fields;
> - unsigned int num_chan;
> + unsigned int pwm_num_chan;
> + unsigned int cpt_num_chan;
> unsigned int max_pwm_cnt;
> unsigned int max_prescale;
> };
> @@ -77,6 +90,7 @@ struct sti_pwm_chip {
> struct clk *cpt_clk;
> struct regmap *regmap;
> struct sti_pwm_compat_data *cdata;
> + struct sti_cpt_data *cpt_data[STI_MAX_CPT_CHANS];
The PWM subsystem allows chip-specific data to be associated with each
PWM device. I'd prefer if the driver used it rather than homebrew some-
thing similar. See pwm_set_chip_data() and pwm_get_chip_data().
> @@ -389,6 +411,19 @@ static int sti_pwm_probe(struct platform_device *pdev)
> if (ret)
> return ret;
>
> + for (chan = 0; chan < cdata->cpt_num_chan; chan++) {
> + struct sti_cpt_data *data;
> +
> + data = devm_kzalloc(dev, sizeof(*data), GFP_KERNEL);
> + if (!data)
> + return -ENOMEM;
> +
> + init_waitqueue_head(&data->wait);
> + mutex_init(&data->lock);
> + data->gpio = of_get_named_gpio(np, "capture-gpios", chan);
> + pc->cpt_data[chan] = data;
Converting to per-PWM data should be as simple as turning this last line
into:
pwm_set_chip_data(pc->chip.pwms[chan], data);
Also I don't see any cleanup for this data in the driver. The memory for
the per-PWM data should be freed by devm_*() infrastructure, but how
will the GPIO be released?
Thierry
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20160412/43bda11f/attachment.sig>
next prev parent reply other threads:[~2016-04-12 10:29 UTC|newest]
Thread overview: 71+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-02 15:31 [RESEND 00/11] pwm: Add support for PWM Capture Lee Jones
2016-03-02 15:31 ` Lee Jones
2016-03-02 15:31 ` [RESEND 01/11] pwm: Add PWM Capture support Lee Jones
2016-03-02 15:31 ` Lee Jones
2016-03-02 15:31 ` Lee Jones
2016-04-12 10:08 ` Thierry Reding
2016-04-12 10:08 ` Thierry Reding
2016-04-13 9:36 ` Lee Jones
2016-04-13 9:36 ` Lee Jones
2016-04-13 14:50 ` Thierry Reding
2016-04-13 14:50 ` Thierry Reding
2016-03-02 15:32 ` [RESEND 02/11] pwm: sysfs: " Lee Jones
2016-03-02 15:32 ` Lee Jones
2016-03-02 15:32 ` Lee Jones
2016-04-12 10:15 ` Thierry Reding
2016-04-12 10:15 ` Thierry Reding
2016-04-13 9:40 ` Lee Jones
2016-04-13 9:40 ` Lee Jones
2016-03-02 15:32 ` [RESEND 03/11] pwm: sti: Reorganise register names in preparation for new functionality Lee Jones
2016-03-02 15:32 ` Lee Jones
2016-03-02 15:32 ` [RESEND 04/11] pwm: sti: Only request clock rate when you need to Lee Jones
2016-03-02 15:32 ` Lee Jones
2016-03-02 15:32 ` Lee Jones
2016-03-02 15:32 ` [RESEND 05/11] pwm: sti: Supply PWM Capture register addresses and bit locations Lee Jones
2016-03-02 15:32 ` Lee Jones
2016-03-02 15:32 ` Lee Jones
2016-03-02 15:32 ` [RESEND 06/11] pwm: sti: Supply PWM Capture clock handling Lee Jones
2016-03-02 15:32 ` Lee Jones
2016-03-02 15:32 ` Lee Jones
2016-03-02 15:32 ` [RESEND 07/11] pwm: sti: Initialise PWM Capture channel data Lee Jones
2016-03-02 15:32 ` Lee Jones
2016-04-12 10:29 ` Thierry Reding [this message]
2016-04-12 10:29 ` Thierry Reding
2016-04-15 12:39 ` Lee Jones
2016-04-15 12:39 ` Lee Jones
2016-04-15 14:22 ` Thierry Reding
2016-04-15 14:22 ` Thierry Reding
2016-04-15 14:31 ` Lee Jones
2016-04-15 14:31 ` Lee Jones
2016-04-15 13:11 ` Lee Jones
2016-04-15 13:11 ` Lee Jones
2016-04-15 14:23 ` Thierry Reding
2016-04-15 14:23 ` Thierry Reding
2016-03-02 15:32 ` [RESEND 08/11] pwm: sti: Add support for PWM Capture IRQs Lee Jones
2016-03-02 15:32 ` Lee Jones
2016-04-12 10:35 ` Thierry Reding
2016-04-12 10:35 ` Thierry Reding
2016-04-13 10:05 ` Lee Jones
2016-04-13 10:05 ` Lee Jones
2016-04-13 15:16 ` Thierry Reding
2016-04-13 15:16 ` Thierry Reding
2016-03-02 15:32 ` [RESEND 09/11] pwm: sti: Add PWM Capture call-back Lee Jones
2016-03-02 15:32 ` Lee Jones
2016-04-12 10:53 ` Thierry Reding
2016-04-12 10:53 ` Thierry Reding
2016-04-13 10:25 ` Lee Jones
2016-04-13 10:25 ` Lee Jones
2016-04-13 15:22 ` Thierry Reding
2016-04-13 15:22 ` Thierry Reding
2016-04-15 8:29 ` Lee Jones
2016-04-15 8:29 ` Lee Jones
2016-04-15 14:20 ` Thierry Reding
2016-04-15 14:20 ` Thierry Reding
2016-03-02 15:32 ` [RESEND 10/11] pwm: sti: Enable PWM Capture Lee Jones
2016-03-02 15:32 ` Lee Jones
2016-04-12 10:56 ` Thierry Reding
2016-04-12 10:56 ` Thierry Reding
2016-03-02 15:32 ` [RESEND 11/11] pwm: sti: Take the opportunity to conduct a little house keeping Lee Jones
2016-03-02 15:32 ` Lee Jones
2016-04-12 7:28 ` [RESEND 00/11] pwm: Add support for PWM Capture Lee Jones
2016-04-12 7:28 ` Lee Jones
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=20160412102926.GC18882@ulmo.ba.sec \
--to=thierry.reding@gmail.com \
--cc=ajitpal.singh@st.com \
--cc=kernel@stlinux.com \
--cc=lee.jones@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=maxime.coquelin@st.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.