From: Lee Jones <lee.jones@linaro.org>
To: Guru Das Srinagesh <gurus@codeaurora.org>
Cc: "Kate Stewart" <kstewart@linuxfoundation.org>,
linux-fbdev@vger.kernel.org,
"David Collins" <collinsd@codeaurora.org>,
"Liam Girdwood" <lgirdwood@gmail.com>,
"David Airlie" <airlied@linux.ie>,
"Michael Turquette" <mturquette@baylibre.com>,
"Kamil Debski" <kamil@wypas.org>,
dri-devel@lists.freedesktop.org,
"Chris Wilson" <chris@chris-wilson.co.uk>,
"Atish Patra" <atish.patra@wdc.com>,
"Thierry Reding" <thierry.reding@gmail.com>,
linux-riscv@lists.infradead.org, linux-clk@vger.kernel.org,
"Daniel Thompson" <daniel.thompson@linaro.org>,
"Mauro Carvalho Chehab" <mchehab@kernel.org>,
"Alexander Shiyan" <shc_work@mail.ru>,
"Chen-Yu Tsai" <wens@csie.org>,
"NXP Linux Team" <linux-imx@nxp.com>,
"Uwe Kleine-König" <u.kleine-koenig@pengutronix.de>,
"Sascha Hauer" <s.hauer@pengutronix.de>,
"Guenter Roeck" <linux@roeck-us.net>,
linux-media@vger.kernel.org, linux-pwm@vger.kernel.org,
"Jean Delvare" <jdelvare@suse.com>,
"Alexandre Torgue" <alexandre.torgue@st.com>,
"Arnd Bergmann" <arnd@arndb.de>,
"Bartlomiej Zolnierkiewicz" <b.zolnierkie@samsung.com>,
intel-gfx@lists.freedesktop.org,
"Mark Brown" <broonie@kernel.org>,
"Paul Walmsley" <paul.walmsley@sifive.com>,
"Subbaraman Narayanamurthy" <subbaram@codeaurora.org>,
"Thomas Gleixner" <tglx@linutronix.de>,
"Fabrice Gasnier" <fabrice.gasnier@st.com>,
"Pengutronix Kernel Team" <kernel@pengutronix.de>,
"Allison Randal" <allison@lohutok.net>,
linux-hwmon@vger.kernel.org,
"Maxime Coquelin" <mcoquelin.stm32@gmail.com>,
"Richard Fontana" <rfontana@redhat.com>,
"Stephen Boyd" <sboyd@kernel.org>,
"Jingoo Han" <jingoohan1@gmail.com>,
linux-kernel@vger.kernel.org, "Yash Shah" <yash.shah@sifive.com>,
"Palmer Dabbelt" <palmer@dabbelt.com>,
"Dan Carpenter" <dan.carpenter@oracle.com>,
"Joe Perches" <joe@perches.com>,
"Shawn Guo" <shawnguo@kernel.org>
Subject: Re: [PATCH v13 00/11] Convert PWM period and duty cycle to u64
Date: Thu, 23 Apr 2020 12:48:57 +0100 [thread overview]
Message-ID: <20200423114857.GG3612@dell> (raw)
In-Reply-To: <cover.1587523702.git.gurus@codeaurora.org>
On Tue, 21 Apr 2020, Guru Das Srinagesh wrote:
> [REQUEST]
>
> Would it be possible for the patches that have already received Acked-by's in
> this series to be accepted and applied to the tree? I lost an Acked-by (in
> intel-panel.c) because it had a merge conflict with a new change that came in
> after I rebased to tip. I wasn't sure earlier about accepting single patches as
> opposed to the entire series en masse, but this event has got me thinking.
>
> [COVER LETTER]
>
> Because period and duty cycle are defined in the PWM framework structs as ints
> with units of nanoseconds, the maximum time duration that can be set is limited
> to ~2.147 seconds. Consequently, applications desiring to set greater time
> periods via the PWM framework are not be able to do so - like, for instance,
> causing an LED to blink at an interval of 5 seconds.
>
> Redefining the period and duty cycle struct members in the core PWM framework
> structs as u64 values will enable larger time durations to be set and solve
> this problem. Such a change to the framework mandates that drivers using these
> struct members (and corresponding helper functions) also be modified correctly
> in order to prevent compilation errors.
>
> This patch series introduces the changes to all the drivers first, followed by
> the framework change at the very end so that when the latter is applied, all
> the drivers are in good shape and there are no compilation errors.
What's the merge plan for this set?
FYI, it's better to send all patches to all parties. That way
maintainers and interested persons can follow the discussion and
progress, or lack there of.
--
Lee Jones [李琼斯]
Linaro Services Technical Lead
Linaro.org │ Open source software for ARM SoCs
Follow Linaro: Facebook | Twitter | Blog
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2020-04-23 11:49 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-22 2:57 [PATCH v13 00/11] Convert PWM period and duty cycle to u64 Guru Das Srinagesh
2020-04-22 2:57 ` [PATCH v13 01/11] drm/i915: Use 64-bit division macro Guru Das Srinagesh
2020-04-24 6:17 ` Jani Nikula
2020-04-24 22:17 ` Guru Das Srinagesh
2020-04-27 13:48 ` Jani Nikula
2020-04-22 2:57 ` [PATCH v13 09/11] backlight: pwm_bl: Use 64-bit division function Guru Das Srinagesh
2020-05-26 7:00 ` Lee Jones
2020-04-22 8:49 ` [PATCH v13 00/11] Convert PWM period and duty cycle to u64 Daniel Thompson
2020-04-22 23:37 ` Guru Das Srinagesh
2020-04-23 9:20 ` Daniel Thompson
2020-04-23 11:48 ` Lee Jones [this message]
2020-04-23 21:53 ` Guru Das Srinagesh
2020-04-24 6:43 ` Lee Jones
2020-04-24 22:14 ` Guru Das Srinagesh
2020-04-27 6:44 ` Lee Jones
2020-04-24 6:45 ` Lee Jones
2020-04-24 6:46 ` 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=20200423114857.GG3612@dell \
--to=lee.jones@linaro.org \
--cc=airlied@linux.ie \
--cc=alexandre.torgue@st.com \
--cc=allison@lohutok.net \
--cc=arnd@arndb.de \
--cc=atish.patra@wdc.com \
--cc=b.zolnierkie@samsung.com \
--cc=broonie@kernel.org \
--cc=chris@chris-wilson.co.uk \
--cc=collinsd@codeaurora.org \
--cc=dan.carpenter@oracle.com \
--cc=daniel.thompson@linaro.org \
--cc=dri-devel@lists.freedesktop.org \
--cc=fabrice.gasnier@st.com \
--cc=gurus@codeaurora.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jdelvare@suse.com \
--cc=jingoohan1@gmail.com \
--cc=joe@perches.com \
--cc=kamil@wypas.org \
--cc=kernel@pengutronix.de \
--cc=kstewart@linuxfoundation.org \
--cc=lgirdwood@gmail.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-fbdev@vger.kernel.org \
--cc=linux-hwmon@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-media@vger.kernel.org \
--cc=linux-pwm@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=linux@roeck-us.net \
--cc=mchehab@kernel.org \
--cc=mcoquelin.stm32@gmail.com \
--cc=mturquette@baylibre.com \
--cc=palmer@dabbelt.com \
--cc=paul.walmsley@sifive.com \
--cc=rfontana@redhat.com \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=shc_work@mail.ru \
--cc=subbaram@codeaurora.org \
--cc=tglx@linutronix.de \
--cc=thierry.reding@gmail.com \
--cc=u.kleine-koenig@pengutronix.de \
--cc=wens@csie.org \
--cc=yash.shah@sifive.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