[PATCH v8 4/6] cpufreq: powernv/tracing: Add powernv_throttle tracepoint
This patch adds the powernv_throttle tracepoint to trace the CPU frequency throttling event, which is used by the powernv-cpufreq driver in POWER8. S
View Article[PATCH v8 5/6] cpufreq: powernv: Replace pr_info with trace print for...
Currently we use printk message to notify the throttle event. But this can flood the console if the cpu is throttled frequently. So replace the printk
View Article[PATCH v8 6/6] cpufreq: powernv: Add sysfs attributes to show throttle stats
Create sysfs attributes to export throttle information in /sys/devices/system/cpu/cpufreq/chipX. The newly added sysfs files are as follows: 1)/sys/d
View Article[PATCH 0/2] GPIO: Clean up asm/gpio.h
Many arches supply an asm/gpio.h that contains only this: #warning Include linux/gpio.h instead of asm/gpio.h #include <linux/gpio.h> These two
View Article[PATCH 1/2] gpio: Include linux/gpio.h instead of asm/gpio.h
Most arches have an asm/gpio.h that merely includes linux/gpio.h. The others select ARCH_HAVE_CUSTOM_GPIO_H, and when that's selected, linux/gpio.h i
View Article[PATCH 2/2] gpio: Remove unused asm/gpio.h files
asm/gpio.h is included only by linux/gpio.h, and then only when the arch selects ARCH_HAVE_CUSTOM_GPIO_H. Only the following arches select it: arm av
View Article[PATCH 0/3] USB: PHY: minor include cleanups
Remove some gpio and regulator #includes when they can be replaced by trivial forward struct declarations. Also move a linux/gpio/consumer.h #include
View Article[PATCH 1/3] usb: phy: generic: use forward declarations instead of #includes
In include/linux/usb/usb_phy_generic.h, use a forward declaration for struct gpio_desc instead of including linux/gpio/consumer.h. Of the files that
View Article[PATCH 2/3] usb: phy: generic: use forward declarations instead of #includes
In drivers/usb/phy/phy-generic.h, use forward declarations for struct regulator and struct gpio_desc instead of including linux/regulator/consumer.h a
View Article[PATCH 3/3] usb: phy: phy-am335x: remove include of regulator/consumer.h
phy-am335x.c doesn't use any interfaces from linux/regulator/consumer.h, so stop including it. Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> CC:
View Article[RFC 0/12] introduce down_write_killable for rw_semaphore
Hi, the following patchset implements a killable variant of write lock for rw_semaphore. My usecase is to turn as many mmap_sem write users to use a k
View Article[RFC 01/12] locking, rwsem: get rid of __down_write_nested
From: Michal Hocko <mhocko@suse.com> This is no longer used anywhere and all callers (__down_write) use 0 as a subclass. Ditch __down_write_nested to
View Article[RFC 02/12] locking, rwsem: drop explicit memory barriers
From: Michal Hocko <mhocko@suse.com> sh and xtensa seem to be the only architectures which use explicit memory barriers for rw_semaphore operations e
View Article[RFC 03/12] locking, rwsem: introduce basis for down_write_killable
From: Michal Hocko <mhocko@suse.com> Introduce a generic implementation necessary for down_write_killable. This is a trivial extension of the already
View Article[RFC 04/12] alpha, rwsem: provide __down_write_killable
From: Michal Hocko <mhocko@suse.com> Introduce ___down_write for the fast path and reuse it for __down_write resp. __down_write_killable each using t
View Article[RFC 05/12] ia64, rwsem: provide __down_write_killable
From: Michal Hocko <mhocko@suse.com> Introduce ___down_write for the fast path and reuse it for __down_write resp. __down_write_killable each using t
View Article[RFC 06/12] s390, rwsem: provide __down_write_killable
From: Michal Hocko <mhocko@suse.com> Introduce ___down_write for the fast path and reuse it for __down_write resp. __down_write_killable each using t
View Article[RFC 07/12] sh, rwsem: provide __down_write_killable
From: Michal Hocko <mhocko@suse.com> which is uses the same fast path as __down_write except it falls back to rwsem_down_write_failed_killable slow p
View Article[RFC 08/12] sparc, rwsem: provide __down_write_killable
From: Michal Hocko <mhocko@suse.com> which is uses the same fast path as __down_write except it falls back to rwsem_down_write_failed_killable slow p
View Article[RFC 09/12] xtensa, rwsem: provide __down_write_killable
From: Michal Hocko <mhocko@suse.com> which is uses the same fast path as __down_write except it falls back to rwsem_down_write_failed_killable slow p
View Article
