On Wed, 8 Oct 2008 11:43:17 -0500
Bill Gatliff <[EMAIL PROTECTED]> wrote:
> diff --git a/drivers/misc/Kconfig b/drivers/misc/Kconfig
> index a726f3b..cdea0bb 100644
> --- a/drivers/misc/Kconfig
> +++ b/drivers/misc/Kconfig
> @@ -13,15 +13,6 @@ menuconfig MISC_DEVICES
>
> if MISC_DEVICES
>
On Thu, Oct 9, 2008 at 00:18, Bill Gatliff wrote:
> Mike Frysinger wrote:
>> if you'd seriously play with a Blackfin board, i think we can arrange that
>
> I'd seriously *love* to play with one, but I'm pretty strapped for time for
> another couple of months. The only purpose it would serve near-t
Mike Frysinger wrote:
> if you'd seriously play with a Blackfin board, i think we can arrange that
I'd seriously *love* to play with one, but I'm pretty strapped for time for
another couple of months. The only purpose it would serve near-term would be to
prove out the input capabilities of a devi
On Wed, Oct 8, 2008 at 23:46, Bill Gatliff wrote:
> Mike Frysinger wrote:
>>> Are you proposing that the API accommodate both input and output devices?
>>
>> i dont think we should preclude it from the outset.
>
> I don't think have a problem with that. At some point, I would need someone
> with i
Mike Frysinger wrote:
>
> the Blackfin timers/pwm's can flip between input and ouput based on
> the configuration register. everything else (pin/etc...) is
> unchanged.
Interesting!
>> Are you proposing that the API accommodate both input and output devices?
>
> i dont think we should preclude
On Wed, Oct 8, 2008 at 22:23, Bill Gatliff wrote:
> Mike Frysinger wrote:
>> On Wed, Oct 8, 2008 at 12:43, Bill Gatliff wrote:
>>> This series proposes a "generic PWM" driver API.
>>
>> seems that the API is solely geared to handle PWM as an output signal.
>
> True. The peripherals I'm currently t
Bill Gatliff wrote:
>
>> all the utility config functions lack "set" in their name. it's a
>> little confusing as to whether the function is a get or set at first
>> glance.
For the record, I can support adding a "set" to the function names.
b.g.
--
Bill Gatliff
[EMAIL PROTECTED]
--
To unsu
Mike Frysinger wrote:
> On Wed, Oct 8, 2008 at 12:43, Bill Gatliff wrote:
>> This series proposes a "generic PWM" driver API.
>
> seems that the API is solely geared to handle PWM as an output signal.
True. The peripherals I'm currently targeting are output-only devices, and the
API reflects tha
Chris Snook wrote:
> The kernel build system is supposed to be stateless, and integrating
> this with make would mess that up.
> If your goal is to get more people
> to use Bloatwatch
Not really. Bloatwatch is a means to an end. It's
only the end I care about, which is more visibility
into kerne
On Wed, Oct 8, 2008 at 12:43, Bill Gatliff wrote:
> This series proposes a "generic PWM" driver API.
seems that the API is solely geared to handle PWM as an output signal.
what about input ?
all the utility config functions lack "set" in their name. it's a
little confusing as to whether the fun
Tim Bird wrote:
I've been thinking about a tool that might be useful
to track kernel size changes. I'm posting this
Request For Comments to get feedback, and determine
if this is something that would be worthwhile to
pursue.
What I envision is some new kernel build targets, specifically
related
On Wed, 2008-10-08 at 11:25 -0700, Tim Bird wrote:
> Marco Stornelli wrote:
> > Hi Mike,
> >
> > I am not the PRAMFS mantainer, and I think he is in charge to do that
> > (right?), I sent an email to Steve Longerbeam and to MontaVista support,
> > but I haven't received any response. However, if y
Marco Stornelli wrote:
> Hi Mike,
>
> I am not the PRAMFS mantainer, and I think he is in charge to do that
> (right?), I sent an email to Steve Longerbeam and to MontaVista support,
> but I haven't received any response. However, if you think it could be
> useful to submit it to lkml I could do i
Signed-off-by: Bill Gatliff <[EMAIL PROTECTED]>
---
drivers/pwm/atmel-pwm.c | 631 +++
1 files changed, 631 insertions(+), 0 deletions(-)
create mode 100644 drivers/pwm/atmel-pwm.c
diff --git a/drivers/pwm/atmel-pwm.c b/drivers/pwm/atmel-pwm.c
new fi
This series proposes a "generic PWM" driver API.
This proposed API is motivated by the author's need to support
pluggable devices; a secondary objective is to consolidate the
existing PWM implementations behind an agreeable, consistent,
redundancy-reducing interface.
The code included in this pat
Signed-off-by: Bill Gatliff <[EMAIL PROTECTED]>
---
drivers/leds/Kconfig | 21 --
drivers/leds/Makefile |2 +
drivers/leds/leds-pwm.c| 141
drivers/leds/ledtrig-dim.c | 95 +
include/linux/pwm-led
Signed-off-by: Bill Gatliff <[EMAIL PROTECTED]>
---
Documentation/pwm.txt | 258 +
1 files changed, 258 insertions(+), 0 deletions(-)
create mode 100644 Documentation/pwm.txt
diff --git a/Documentation/pwm.txt b/Documentation/pwm.txt
new file mod
Signed-off-by: Bill Gatliff <[EMAIL PROTECTED]>
---
drivers/pwm/pwm.c | 667 +
1 files changed, 667 insertions(+), 0 deletions(-)
create mode 100644 drivers/pwm/pwm.c
diff --git a/drivers/pwm/pwm.c b/drivers/pwm/pwm.c
new file mode 100644
ind
Signed-off-by: Bill Gatliff <[EMAIL PROTECTED]>
---
arch/arm/Kconfig |2 +
drivers/Makefile |2 +
drivers/misc/Kconfig |9 -
drivers/misc/Makefile|1 -
drivers/misc/atmel_pwm.c | 409 --
drivers/pwm/Kconfig
Signed-off-by: Bill Gatliff <[EMAIL PROTECTED]>
---
include/linux/pwm.h | 168 --
1 files changed, 147 insertions(+), 21 deletions(-)
diff --git a/include/linux/pwm.h b/include/linux/pwm.h
index 3945f80..d3d18f7 100644
--- a/include/linux/pwm.h
++
Hi Mike,
I am not the PRAMFS mantainer, and I think he is in charge to do that
(right?), I sent an email to Steve Longerbeam and to MontaVista support,
but I haven't received any response. However, if you think it could be
useful to submit it to lkml I could do it.
Regards.
Mike Frysinger ha scr
21 matches
Mail list logo
