to
be scaled via USER_HZ, and when are they not?
Thanks,
William Breathitt Gray
--
To unsubscribe from this list: send the line unsubscribe linux-kernel in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ
On 10/27/2015 07:13 AM, Simon Guinot wrote:
> On Tue, Oct 27, 2015 at 11:06:58AM +0100, Linus Walleij wrote:
>> On Mon, Oct 19, 2015 at 6:59 PM, William Breathitt Gray
>> <vilhelm.g...@gmail.com> wrote:
>>
>>> The ACCES 104-IDIO-16 family of PC/104 utility boar
r them to be positioned?
William Breathitt Gray
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
To prevent confusion and to match existing coding style used in other
gpio drivers symbol names within the 104-idio-16 gpio driver should be
lowercase.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
drivers/gpio/gpio-104-idio-16.c | 31 +++
to digital outputs 0-15, while GPIO 16-31
correspond to digital inputs 0-15. The base port address for the device
may be set via the a_104_idio_16_base module parameter.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
Changes in v7:
- Return -EINVAL when gpio_get ope
to digital outputs 0-15, while GPIO 16-31
correspond to digital inputs 0-15. The base port address for the device
may be set via the idio_16_base module parameter.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
Changes in v10:
- Rename symbols to be more concise
- Allocat
->move_in_progress))
Sincerely,
William Breathitt Gray
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the
to digital outputs 0-15, while GPIO 16-31
correspond to digital inputs 0-15. The base port address for the device
may be set via the a_104_idio_16_base module parameter.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
Changes in v5
- Remove owner field from a_104_idio_16_driver
to digital outputs 0-15, while GPIO 16-31
correspond to digital inputs 0-15. The base port address for the device
may be set via the a_104_idio_16_base module parameter.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
Changes in v6:
- Add support for gpio_get_direction functio
to digital outputs 0-15, while GPIO 16-31
correspond to digital inputs 0-15. The base port address for the device
may be set via the a_104_idio_16_base module parameter.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
Changes in v4:
- Replace compile-time co
to digital outputs 0-15, while GPIO 16-31
correspond to digital inputs 0-15. The base port address for the device
may be set via the a_104_idio_16_base module parameter.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
Changes in v8:
- Remove value inversion before output sinc
to digital outputs 0-15, while GPIO 16-31
correspond to digital inputs 0-15. The base port address for the device
may be set via the a_104_idio_16_base module parameter.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
Changes in v9:
- Initialize GPIO device private data str
To prevent confusion, and to match the existing coding style used in
other GPIO drivers, symbol names within the 104-idio-16 GPIO driver
should be lowercase.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
Reviewed-by: Alexandre Courbot <acour...@nvidia.com>
---
C
to digital outputs 0-15, while GPIO 16-31
correspond to digital inputs 0-15.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
drivers/gpio/Kconfig| 14
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-104-idio-16.c
to digital outputs 0-15, while GPIO 16-31
correspond to digital inputs 0-15.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
Changes in v2:
- Add X86 dependency for CONFIG_GPIO_104_IDIO_16
- Encapsulate container_of macro within static function
drivers/gpio/K
On 10/05/2015 04:29 AM, Linus Walleij wrote:
>> +struct a_104_idio_16_gpio {
>> + struct gpio_chip chip;
>> + spinlock_t lock;
>> + unsigned base;
>
> Isn't this void __iomem *base?
The 'base' member is used to hold the I/O port base address passed to the
inb/outb functions for
to digital outputs 0-15, while GPIO 16-31
correspond to digital inputs 0-15.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
Changes in v3:
- Replace gpio.h include with gpio/driver.h since all needed
relevant symbols and resources are within the latter
- Rename
On 10/05/2015 06:47 PM, Bjorn Helgaas wrote:
> I'm really not familiar with PC/104, but wikipedia claims it only uses
> ISA. Apparently PCI/104-Plus, PCI-104, PCI/104-Express, and PCIe/104
> *do* have PCI and/or PCIe, but it looks like the base PC/104 does not.
>
> Bjorn
>
This is correct:
. The base port address for the device may be configured via
the ws16c48_base module parameter. The interrupt line number for the
device may be configured via the ws16c48_irq module parameter.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
MAINTAINERS | 6 +
d
. The base port address for the device may be configured via
the ws16c48_base module parameter. The interrupt line number for the
device may be configured via the ws16c48_irq module parameter.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
Changes in v2:
- Use gpio_chip data p
number for the
device may be configured via the idi_48_irq module parameter.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
Changes in v2:
- Reimplement irq_ack callback as a NOOP since status register read in
idi_48_irq_handler clears all pending interrupts.
MAINT
ange
as a separate patch based on top of this commit?
- William Breathitt Gray
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read th
IRQ should be disabled on device probe so that the device IRQ is in a
known starting state. If IRQ is not disabled, interrupts may be reported
as handled by the IRQ handler, despite no irq_unmask calls made by the
user.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
d
number for the
device may be configured via the idi_48_irq module parameter.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
MAINTAINERS| 6 +
drivers/gpio/Kconfig | 9 ++
drivers/gpio/Makefile | 1 +
drivers/gpio/gpio-104-id
array memory access for a non-existent third control port.
Fixes: 1b06d64f7374 ("gpio: Add GPIO support for the ACCES 104-DIO-48E")
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
drivers/gpio/gpio-104-dio-48e.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletion
The Apex Embedded Systems STX104 device features eight lines of digital
I/O (four digital inputs and four digital outputs). This patch adds GPIO
support for these eight lines of digital I/O via GPIOLIB.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
drivers/iio/dac/K
The Apex Embedded Systems STX104 device features eight lines of digital
I/O (four digital inputs and four digital outputs). This patch adds GPIO
support for these eight lines of digital I/O via GPIOLIB.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
Changes in v2:
-
ers to ISA_BUS_API, thus
>> allowing them to build for X86_64 as they are expected to.
>>
>> Cc: Guenter Roeck <li...@roeck-us.net>
>> Cc: Linus Walleij <linus.wall...@linaro.org>
>> Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
>> --
On Sun, Jun 05, 2016 at 09:24:24PM +0200, Pavel Machek wrote:
>On Sat 2016-06-04 07:12:21, William Breathitt Gray wrote:
>> I think I see the merit of a prompt for PC104 devices. I've encountered
>> a use case recently which I'm curious about in this scenario. Given the
>> c
m>
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
Changes in v3:
- Revert v2 change; any arch should be able to select GPIOLIB
- Return -EINVAL when attempting to set a GPIO to a direction it
cannot be
- Call stx104_gpio_set to have an initial value w
On Mon, Jun 13, 2016 at 02:15:43PM +0200, Linus Walleij wrote:
>On Fri, Jun 3, 2016 at 7:42 PM, William Breathitt Gray
><vilhelm.g...@gmail.com> wrote:
>
>> The Apex Embedded Systems STX104 device features eight lines of digital
>> I/O (four digital inputs and four d
On Sat, Jun 04, 2016 at 09:14:08AM +0200, Pavel Machek wrote:
>On Fri 2016-06-03 17:12:44, William Breathitt Gray wrote:
>> On Fri, Jun 03, 2016 at 10:57:03PM +0200, Pavel Machek wrote:
>> >Should we do "depends on PC104" here, because that is what it really
>> &
e -display none
> -monitor null
>
>
>
>
>
>Thanks,
>Xiaolong
Hello,
I believe this bug occurs when isa_register_driver is called before
isa_bus_init; this is possible with built-in drivers since isa_bus_init
is registered via device_initcall within the drivers/base/isa.c file.
I submitted a patch addressing this on May 11; see:
https://lkml.org/lkml/2016/5/11/857.
Let me know if this fixes the bug, or if there are any other issues.
Thank you,
William Breathitt Gray
On Fri, May 27, 2016 at 11:20:57AM -0700, Guenter Roeck wrote:
>On Mon, May 23, 2016 at 08:31:07PM -0400, William Breathitt Gray wrote:
>> With the introduction of the ISA_BUS_API Kconfig option, ISA-style
>> drivers may be built for X86_64 architectures. This patch changes the
viewed-by: Guenter Roeck <li...@roeck-us.net>
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
arch/Kconfig | 3 +++
arch/x86/Kconfig | 9 +
drivers/base/Makefile | 2 +-
include/linux/isa.h | 2 +-
4 files changed, 14 insertions(+), 2 deleti
: Wim Van Sebroeck <w...@iguana.be>
Reviewed-by: Guenter Roeck <li...@roeck-us.net>
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
drivers/watchdog/Kconfig | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/watchdog/Kconfig b/drivers/watc
: Hartmut Knaack <knaac...@gmx.de>
Cc: Lars-Peter Clausen <l...@metafoo.de>
Cc: Peter Meerwald-Stadler <pme...@pmeerw.net>
Cc: Jonathan Cameron <ji...@kernel.org>
Reviewed-by: Guenter Roeck <li...@roeck-us.net>
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com&
gnu...@gmail.com>
Cc: Linus Walleij <linus.wall...@linaro.org>
Reviewed-by: Guenter Roeck <li...@roeck-us.net>
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
drivers/gpio/Kconfig | 8
1 file changed, 4 insertions(+), 4 deletions(-)
diff --git
GPIO driver
William Breathitt Gray (4):
isa: Allow ISA-style drivers on modern systems
gpio: Allow PC/104 devices on X86_64
iio: stx104: Allow build for X86_64
watchdog: ebc-c384_wdt: Allow build for X86_64
arch/Kconfig | 3 +++
arch/x86/Kconfig | 9 +
drivers/
This driver does not do anything special in module init/exit. This patch
eliminates the module init/exit boilerplate code by utilizing the
module_isa_driver macro.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
drivers/net/can/sja1000/tscan1.c | 12 +---
This driver does not do anything special in module init/exit. This patch
eliminates the module init/exit boilerplate code by utilizing the
module_isa_driver macro.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
drivers/watchdog/pcwd.c | 14 +-
1 file chan
On Tue, May 31, 2016 at 10:41:49AM +0200, Linus Walleij wrote:
>On Sat, May 28, 2016 at 12:08 AM, William Breathitt Gray
><vilhelm.g...@gmail.com> wrote:
>
>> With the introduction of the ISA_BUS_API Kconfig option, ISA-style
>> drivers may be built for X86_64 archit
This driver does not do anything special in module init/exit. This patch
eliminates the module init/exit boilerplate code by utilizing the
module_isa_driver macro.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
drivers/i2c/busses/i2c-elektor.c | 13 +
This driver does not do anything special in module init/exit. This patch
eliminates the module init/exit boilerplate code by utilizing the
module_isa_driver macro.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
sound/isa/cs423x/cs4231.c | 13 +
1 file chan
This driver does not do anything special in module init/exit. This patch
eliminates the module init/exit boilerplate code by utilizing the
module_isa_driver macro.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
sound/isa/cmi8328.c | 13 +
1 file chan
This driver does not do anything special in module init/exit. This patch
eliminates the module init/exit boilerplate code by utilizing the
module_isa_driver macro.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
sound/isa/sb/jazz16.c | 13 +
1 file chan
This driver does not do anything special in module init/exit. This patch
eliminates the module init/exit boilerplate code by utilizing the
module_isa_driver macro.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
sound/isa/gus/gusmax.c | 13 +
1 file chan
This driver does not do anything special in module init/exit. This patch
eliminates the module init/exit boilerplate code by utilizing the
module_isa_driver macro.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
sound/isa/gus/gusextreme.c | 13 +
1 file chan
This driver does not do anything special in module init/exit. This patch
eliminates the module init/exit boilerplate code by utilizing the
module_isa_driver macro.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
sound/isa/ad1848/ad1848.c | 13 +
1 file chan
This driver does not do anything special in module init/exit. This patch
eliminates the module init/exit boilerplate code by utilizing the
module_isa_driver macro.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
sound/isa/adlib.c | 13 +
1 file changed, 1 ins
This driver does not do anything special in module init/exit. This patch
eliminates the module init/exit boilerplate code by utilizing the
module_isa_driver macro.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
sound/isa/sb/sb8.c | 13 +
1 file chan
The module_isa_driver macro is a helper macro for ISA drivers which do
not do anything special in module init/exit. This patchset eliminates a
lot of ISA driver registration boilerplate code by utilizing
module_isa_driver, which replaces module_init and module_exit.
William Breathitt Gray (11
This driver does not do anything special in module init/exit. This patch
eliminates the module init/exit boilerplate code by utilizing the
module_isa_driver macro.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
sound/isa/gus/gusclassic.c | 13 +
1 file chan
This driver does not do anything special in module init/exit. This patch
eliminates the module init/exit boilerplate code by utilizing the
module_isa_driver macro.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
sound/isa/galaxy/galaxy.c | 13 +
1 file chan
This driver does not do anything special in module init/exit. This patch
eliminates the module init/exit boilerplate code by utilizing the
module_isa_driver macro.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
sound/isa/sc6000.c | 13 +
1 file chan
This driver does not do anything special in module init/exit. This patch
eliminates the module init/exit boilerplate code by utilizing the
module_isa_driver macro.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
drivers/i2c/busses/i2c-pca-isa.c | 13 +
On Fri, Jun 17, 2016 at 08:18:10PM -0700, Greg KH wrote:
>On Fri, Jun 17, 2016 at 10:49:59PM -0400, William Breathitt Gray wrote:
>> The PC/104 drivers were changed to utilize the ISA bus driver as part of
>> the original patchset which attempted to decouple the X86_32 dependency
On Fri, Jun 17, 2016 at 07:36:07PM -0700, Greg KH wrote:
>On Fri, Jun 17, 2016 at 12:47:14PM +0200, Thorsten Leemhuis wrote:
>> On 31.05.2016 17:25, Greg KH wrote:
>> > On Tue, May 31, 2016 at 07:23:06AM -0400, William Breathitt Gray wrote:
>> >> On Tue, May 31, 2
On Wed, Feb 10, 2016 at 06:55:45PM +, Jonathan Cameron wrote:
>On 10/02/16 02:19, William Breathitt Gray wrote:
>> On Tue, Feb 09, 2016 at 10:37:09PM +, Jonathan Cameron wrote:
>>> My only real question is on the naming of the module parameter.
>>> Is it the e
On Sat, Feb 06, 2016 at 07:15:41PM +, Jonathan Cameron wrote:
>On 02/02/16 23:30, William Breathitt Gray wrote:
>> The Apex Embedded Systems STX104 is a 16-channel 16-bit analog input and
>> 2-channel 16-bit analog output PC/104 card. The STX104 incorporates a
>> large
be configured via the
stx104_base module parameter array.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
Changes in v2:
- Inline use of dev_name macro
- Use devm_iio_device_register to simplify cleanup code
- Use ISA bus driver instead of platform driver
- Provide stx104_base
eline Linux kernel); see
drivers/gpio/gpio-104-idio-16.c and drivers/gpio/gpio-104-idi-48.c for
example. I have thus far been following the convention of naming the
base address module parameter as "modname_base," where "modname" is the
respective module name.
William Breathitt Gray
dress until the
hardware has been identified; this second method may not be the best
route either.
What do you think?
William Breathitt Gray
By the time request_region is called in the WinSystems WS16C48 GPIO
driver, a corresponding device structure has already been allocated. The
devm_request_region function should be used to help simplify the cleanup
code and reduce the possible points of failure.
Signed-off-by: William Breathitt
By the time request_region is called in the SMSC SCH311x GPIO driver, a
corresponding device structure has already been allocated. The
devm_request_region function should be used to help simplify the cleanup
code and reduce the possible points of failure.
Signed-off-by: William Breathitt Gray
By the time request_region is called in the ACCES 104-DIO-48E GPIO
driver, a corresponding device structure has already been allocated. The
devm_request_region function should be used to help simplify the cleanup
code and reduce the possible points of failure.
Signed-off-by: William Breathitt
com>
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
drivers/gpio/gpio-ich.c | 51 +
1 file changed, 9 insertions(+), 42 deletions(-)
diff --git a/drivers/gpio/gpio-ich.c b/drivers/gpio/gpio-ich.c
index a489338..4f
The ACCES 104-DIO-48E GPIO driver copyright boilerplate lacks the "or
later" verbiage regarding GPL compliant distribution. The MODULE_LICENSE
string should reflect the actual copyright license terms used.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
drive
The ACCES 104-IDI-48 GPIO driver copyright boilerplate lacks the "or
later" verbiage regarding GPL compliant distribution. The MODULE_LICENSE
string should reflect the actual copyright license terms used.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
drive
By the time request_region is called in several GPIO drivers, a
corresponding device structure has already been allocated. The
devm_request_region function should be used to help simplify the cleanup
code and reduce the possible points of failure.
William Breathitt Gray (7):
gpio: 104-dio-48e
By the time request_region is called in the AMD 8111 GPIO driver, a
corresponding device structure has already been allocated. The
devm_request_region function should be used to help simplify the cleanup
code and reduce the possible points of failure.
Signed-off-by: William Breathitt Gray
By the time request_region is called in the ACCES 104-IDI-48 GPIO
driver, a corresponding device structure has already been allocated. The
devm_request_region function should be used to help simplify the cleanup
code and reduce the possible points of failure.
Signed-off-by: William Breathitt Gray
By the time request_region is called in the ACCES 104-IDIO-16 GPIO
driver, a corresponding device structure has already been allocated. The
devm_request_region function should be used to help simplify the cleanup
code and reduce the possible points of failure.
Signed-off-by: William Breathitt
Several of the GPIO drivers have a copyright boilerplate lacking the "or
later" verbiage regarding GPL compliant distribution. The MODULE_LICENSE
string should reflect the actual copyright license terms used.
William Breathitt Gray (4):
gpio: 104-dio-48e: Pass correct lice
The WinSystems WS16C48 GPIO driver copyright boilerplate lacks the "or
later" verbiage regarding GPL compliant distribution. The MODULE_LICENSE
string should reflect the actual copyright license terms used.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
d
The ACCES 104-IDIO-16 GPIO driver copyright boilerplate lacks the "or
later" verbiage regarding GPL compliant distribution. The MODULE_LICENSE
string should reflect the actual copyright license terms used.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
drive
via the
stx104_base module parameter.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
MAINTAINERS | 6 ++
drivers/iio/dac/Kconfig | 8 +++
drivers/iio/dac/Makefile | 1 +
drivers/iio/dac/stx104.c | 178 +++
4
-idi-48
module: base port address for the hardware must be manually set by the
user since the hardware lacks discovery functionality.
William Breathitt Gray
By the time request_region is called in the WinSystems WS16C48 GPIO
driver, a corresponding device structure has already been allocated. The
devm_request_region function should be used to help simplify the cleanup
code and reduce the possible points of failure.
Signed-off-by: William Breathitt
By the time request_region is called in the ACCES 104-IDIO-16 GPIO
driver, a corresponding device structure has already been allocated. The
devm_request_region function should be used to help simplify the cleanup
code and reduce the possible points of failure.
Signed-off-by: William Breathitt
com>
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
Reviewed-by: Alexandre Courbot <acour...@nvidia.com>
---
drivers/gpio/gpio-ich.c | 51 +
1 file changed, 9 insertions(+), 42 deletions(-)
diff --git a/drivers/gpio/gp
By the time request_region is called in the AMD 8111 GPIO driver, a
corresponding device structure has already been allocated. The
devm_request_region function should be used to help simplify the cleanup
code and reduce the possible points of failure.
Signed-off-by: William Breathitt Gray
On 02/02/2016 07:26 PM, Alexandre Courbot wrote:
> On Tue, Feb 2, 2016 at 8:54 AM, William Breathitt Gray
> <vilhelm.g...@gmail.com> wrote:
>> By the time request_region is called in several GPIO drivers, a
>> corresponding device structure has already been allocated. Th
from 104-dio-48e, 104-idi-48,
104-idio-16, and ws16c48 respective private data structures
- Remove unused pdata pointer from sch311x_gpio_remove function
William Breathitt Gray (7):
gpio: 104-dio-48e: Use devm_request_region
gpio: 104-idi-48: Use devm_request_region
gpio: 104-idio-16: Use
By the time request_region is called in the ACCES 104-IDI-48 GPIO
driver, a corresponding device structure has already been allocated. The
devm_request_region function should be used to help simplify the cleanup
code and reduce the possible points of failure.
Signed-off-by: William Breathitt Gray
By the time request_region is called in the ACCES 104-DIO-48E GPIO
driver, a corresponding device structure has already been allocated. The
devm_request_region function should be used to help simplify the cleanup
code and reduce the possible points of failure.
Signed-off-by: William Breathitt
By the time request_region is called in the SMSC SCH311x GPIO driver, a
corresponding device structure has already been allocated. The
devm_request_region function should be used to help simplify the cleanup
code and reduce the possible points of failure.
Signed-off-by: William Breathitt Gray
hopes that it will be useful to someone,
and perhaps even motivate the companies to improve and share their own
Linux drivers.
William Breathitt Gray
watchdog timer.
The timeout may be configured via the timeout module parameter.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
Reviewed-by: Guenter Roeck <li...@roeck-us.net>
---
Changes in v5:
- Round up rather than down when converting seconds to minutes
watchdog timer.
The timeout may be configured via the timeout module parameter.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
Reviewed-by: Guenter Roeck <li...@roeck-us.net>
---
Changes in v6:
- Use DIV_ROUND_UP to round up to minutes from seconds
MAINTAINERS
that the watchdog timer will wait at least that amount of
time (with the understanding that it may be somewhat late due to the
granularity of the timer).
This behavior follows a lot of other timer standards (e.g. nanosleep)
so it's what the user expects and what we should follow for now. I'll
submit a version 5 patch with this change.
William Breathitt Gray
watchdog timer.
The timeout may be configured via the timeout module parameter.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
Reviewed-by: Guenter Roeck <li...@roeck-us.net>
---
Changes in v7:
- Make sure timeout member is in seconds resolution despite minutes
On 02/28/2016 11:20 PM, William Breathitt Gray wrote:
> The WinSystems EBC-C384 has an onboard watchdog timer. The timeout range
> supported by the watchdog timer is 1 second to 255 minutes. Timeouts
> under 256 seconds have a 1 second granularity, while the rest have a 1
> minute
watchdog timer.
The timeout may be configured via the timeout module parameter.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
Reviewed-by: Guenter Roeck <li...@roeck-us.net>
---
MAINTAINERS | 6 ++
drivers/watchdog/Kconfig| 9 ++
drivers/watch
watchdog timer.
The timeout may be configured via the timeout module parameter.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
Changes in v8:
- Utilize the roundup macro to round up second resolution to minute
granularity when setting the timeout member
MAINT
dependency should be removed from the ISA configuration option in
order to support these newer motherboards.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
arch/x86/Kconfig | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/arch/x86/Kconfig b/ar
should be removed.
William Breathitt Gray
cy tree and fix the
build errors with explicit CONFIG_X86_32 dependencies. I'll submit a new patch
with those changes when complete.
William Breathitt Gray
timer.
The timeout may be configured via the timeout module parameter.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
MAINTAINERS | 6 ++
drivers/watchdog/Kconfig| 9 ++
drivers/watchdog/Makefile | 1 +
drivers/watchdog/ebc-c384
timer.
The timeout may be configured via the timeout module parameter.
Signed-off-by: William Breathitt Gray <vilhelm.g...@gmail.com>
---
Changes in v2:
- Reimplement the start and set_timeout callback to reflect the
watchdog API
- Remove unnecessary synchronization locks
- Fi
1 - 100 of 1620 matches
Mail list logo
