This leads me to believe that this patch:
commit c05199e5a57a579fea1e8fa65e2b511ceb524ffc
Author: Kan Liang kan.li...@intel.com
Date: Tue Jan 20 04:54:25 2015 +
perf/x86/intel/uncore: Move uncore_box_init() out of driver
initialization
If I revert it, I bet things
On Fri, Apr 24, 2015 at 09:03:04PM +0200, Arend van Spriel wrote:
On 04/24/15 20:24, John Tobias wrote:
Hi Arend,
Apologize for the confusion. I am asking the repo for the device
driver for 43340. Looking at the link you sent, it's more userspace
support and didn't see the device driver
This patch allows for GPIOs specified in the devicetree to be used as SPI
chipselects on TI OMAP2 SoCs.
Tested on the AM3354.
Signed-off-by: Michael Welling mwell...@ieee.org
---
v2: Considers the possible use of SPI_CS_HIGH during chip select activation.
drivers/spi/spi-omap2-mcspi.c | 13
On Thu, Apr 23, 2015 at 05:50:33PM -0700, John Tobias wrote:
Hello Guys,
I have a follow up questions:
When the I power up the brcm44340 without loading the driver, the
sdhci-esdhc-imx host controller configured it with the following info
(cat /sys/kernel/debug/mmc0/ios):
clock:
btwilink binds bluetooth hci0 interface with the shared transport driver
Signed-off-by: Gigi Joseph gigi.jos...@ti.com
---
Documentation/devicetree/bindings/btwilink.txt | 15 +++
1 file changed, 15 insertions(+)
create mode 100644 Documentation/devicetree/bindings/btwilink.txt
On Fri, Apr 24, 2015 at 08:26:39AM +0200, Henrik Rydberg wrote:
Peter,
It may be a long time ago now, but we had very vocal discussions regarding the
MT protocol back then, and I am quite sure all the subtleties are well
understood. In order to fully appreciate the simplicity of the
On Wed, Apr 22, 2015 at 12:42 AM, Johan Hovold jo...@kernel.org wrote:
Remove gpiod_sysfs_set_active_low (and gpio_sysfs_set_active_low) which
allowed code to change the polarity of a gpio line even after it had
been exported through sysfs.
Drivers should not care, and generally does not
On Wed, Apr 22, 2015 at 12:42 AM, Johan Hovold jo...@kernel.org wrote:
Rename the gpio-chip export/unexport functions to the more descriptive
names gpiochip_register and gpiochip_unregister.
Since these functions are related to sysfs, wouldn't
gpiochip_sysfs_export (or gpiochip_sysfs_register,
On Wed, Apr 22, 2015 at 12:42 AM, Johan Hovold jo...@kernel.org wrote:
Clean gpio-chip class device registration and deregistration.
The class device is registered when a gpio-chip is added (or from
gpiolib_sysfs_init post-core init call), and deregistered when the chip
is removed.
Store
On Wed, Apr 22, 2015 at 12:42 AM, Johan Hovold jo...@kernel.org wrote:
These patches fix a number of issues with the gpio sysfs interface,
including
- fix memory leaks and crashes on device hotplug
- straighten out the convoluted locking
- reduce sysfs-interface latencies through more
701 - 710 of 710 matches
Mail list logo