Linux Kernel https://git.etezian.org/cgit.cgi/linux.git/atom?h=master 2016-12-15T19:45:13+00:00 2016-12-15T19:45:13+00:00 Linus Torvalds torvalds@linux-foundation.org 2016-12-15T19:45:13+00:00 urn:sha1:57d64e6f5fac7b47dd03487f5f2670a7f0c67335 Pull pwm updates from Thierry Reding: "This is a very tiny pull request, with just a new driver for HiSilicon BVT SoCs and a cleanup for the Amlogic Meson driver. There are other patches on the list, but my timing was really bad this time and I ended up not having the time to look at them in enough detail to be comfortable merging them" * tag 'pwm/for-4.10-rc1' of git://git.kernel.org/pub/scm/linux/kernel/git/thierry.reding/linux-pwm: pwm: Add PWM driver for HiSilicon BVT SOCs pwm: meson: Remove unneeded platform MODULE_ALIAS 2016-11-29T15:50:12+00:00 yuanjian yuanjian12@hisilicon.com 2016-11-28T09:42:46+00:00 urn:sha1:d09f00810850dd6e6eac8895b62bc3fc35435431 Add PWM driver for the PWM controller found on HiSilicon BVT SoCs such as Hi3519V100, Hi3516CV300, etc. The PWM controller is primarily in charge of controlling the P-Iris lens. Reviewed-by: Jiancheng Xue <xuejiancheng@hisilicon.com> Signed-off-by: Jian Yuan <yuanjian12@hisilicon.com> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Thierry Reding <thierry.reding@gmail.com> 2016-11-29T15:43:24+00:00 Johan Hovold johan@kernel.org 2016-11-01T10:46:39+00:00 urn:sha1:0e1614ac84f1719d87bed577963bb8140d0c9ce8 Make sure to drop the reference to the parent device taken by class_find_device() after "unexporting" any children when deregistering a PWM chip. Fixes: 0733424c9ba9 ("pwm: Unexport children before chip removal") Signed-off-by: Johan Hovold <johan@kernel.org> Signed-off-by: Thierry Reding <thierry.reding@gmail.com> 2016-10-21T07:12:41+00:00 Javier Martinez Canillas javier@osg.samsung.com 2016-10-19T19:49:59+00:00 urn:sha1:58d5b693637d9963018bcb92fecf858e6899ed49 The Amlogic Meson is a DT-only platform, which means the devices are registered via OF and not using the legacy platform devices support. So there's no need to have a MODULE_ALIAS("platform:meson-pwm") since the reported uevent MODALIAS to user-space will always be the OF one. Signed-off-by: Javier Martinez Canillas <javier@osg.samsung.com> Acked-by: Kevin Hilman <khilman@baylibre.com> Signed-off-by: Thierry Reding <thierry.reding@gmail.com> 2016-10-21T07:10:11+00:00 Axel Lin axel.lin@ingics.com 2016-09-10T01:55:49+00:00 urn:sha1:c699995663b40d61afcc14ca27f0106f13151772 The driver uses the spin_lock but does not initialize it. Fix it. Signed-off-by: Axel Lin <axel.lin@ingics.com> Acked-by: Neil Armstrong <narmstrong@baylibre.com> Signed-off-by: Thierry Reding <thierry.reding@gmail.com> 2016-09-08T08:59:30+00:00 Thierry Reding thierry.reding@gmail.com 2016-09-08T08:59:30+00:00 urn:sha1:dc8e6e1e8f2d2719dd396708b0f56d8b73c9ea52 2016-09-08T08:58:33+00:00 Arnd Bergmann arnd@arndb.de 2016-09-06T12:50:47+00:00 urn:sha1:2fbc487df6e6927bc0a0092f86d4d15961e070de When building with -Wmaybe-uninitialized, we get a couple of harmless warnings about three functions in this new driver that don't look safe to the compiler: drivers/pwm/pwm-meson.c: In function 'meson_pwm_get_state': drivers/pwm/pwm-meson.c:355:26: error: 'mask' may be used uninitialized in this function [-Werror=maybe-uninitialized] drivers/pwm/pwm-meson.c: In function 'meson_pwm_disable': drivers/pwm/pwm-meson.c:263:13: error: 'enable' may be used uninitialized in this function [-Werror=maybe-uninitialized] drivers/pwm/pwm-meson.c: In function 'meson_pwm_apply': drivers/pwm/pwm-meson.c:231:13: error: 'clk_shift' may be used uninitialized in this function [-Werror=maybe-uninitialized] drivers/pwm/pwm-meson.c:231:36: error: 'enable' may be used uninitialized in this function [-Werror=maybe-uninitialized] drivers/pwm/pwm-meson.c:231:24: error: 'clk_enable' may be used uninitialized in this function [-Werror=maybe-uninitialized] Specifically, if we have a device with an ID other than 0 or 1, this would result in undefined behavior. This is currently not possible, but the compiler cannot be expected to know this. This patch adds a 'default' clause to let the compiler know what to do instead, which shuts up the warning and makes the code slightly more resiliant in case it gets extended to other identifiers. Signed-off-by: Arnd Bergmann <arnd@arndb.de> Acked-by: Neil Armstrong <narmstrong@baylibre.com> Signed-off-by: Thierry Reding <thierry.reding@gmail.com> 2016-09-08T08:55:12+00:00 Lee Jones lee.jones@linaro.org 2016-08-16T09:35:07+00:00 urn:sha1:7d8a600c916cab347662de212340d3eaf0e93db2 This includes fixing some Coding Style issues and re-ordering and/or simplifying a little code. Signed-off-by: Lee Jones <lee.jones@linaro.org> [thierry.reding@gmail.com: applied some bikeshedding> Signed-off-by: Thierry Reding <thierry.reding@gmail.com> 2016-09-08T08:55:11+00:00 Lee Jones lee.jones@linaro.org 2016-08-16T09:35:06+00:00 urn:sha1:85a834c42a491deed9ac5bca549b93b7a5455d84 Setting up the STI PWM IP as capture only, with zero PWM output devices is a perfectly valid configuration. It is no longer okay to assume that there must be at least 1 PWM output device. In this patch we make the default number of PWM output devices zero and only configure channels explicitly requested. Reported-by: Peter Griffin <peter.griffin@linaro.org> Signed-off-by: Lee Jones <lee.jones@linaro.org> Signed-off-by: Thierry Reding <thierry.reding@gmail.com> 2016-09-08T08:55:11+00:00 Lee Jones lee.jones@linaro.org 2016-08-16T09:35:05+00:00 urn:sha1:c97267ae831da2711e9592398d490dbd1f4d5ddd Once a PWM capture has been initiated, the capture call enables a rising edge detection interrupt, then waits. Once each of the 3 phase changes have been recorded the thread then wakes. The remaining part of the call carries out the relevant calculations and returns a structure filled out with the capture data. Signed-off-by: Lee Jones <lee.jones@linaro.org> Signed-off-by: Thierry Reding <thierry.reding@gmail.com>