Hi,
On Fri, Dec 02, 2011 at 13:05:22, Heiko Schocher wrote:
Hello,
trying Linux 3.2.0-rc3 on an am1808 based board using MMCSD1 controller,
and facing problems with using DMA. Deactivating use_dma=0 in the
davinci_mmc controller and mmc works in pio mode without problems.
So there are no
Hello Rajashekhara, Sudhakar,
Rajashekhara, Sudhakar wrote:
Hi,
On Fri, Dec 02, 2011 at 13:05:22, Heiko Schocher wrote:
Hello,
trying Linux 3.2.0-rc3 on an am1808 based board using MMCSD1 controller,
and facing problems with using DMA. Deactivating use_dma=0 in the
davinci_mmc controller
Hi,
On Fri, Dec 02, 2011 at 14:25:48, Heiko Schocher wrote:
Hello Rajashekhara, Sudhakar,
Rajashekhara, Sudhakar wrote:
Hi,
On Fri, Dec 02, 2011 at 13:05:22, Heiko Schocher wrote:
Hello,
trying Linux 3.2.0-rc3 on an am1808 based board using MMCSD1 controller,
and facing
Hi,
These v1 patches(against -next tree) introduce v4l2 based face
detection(FD) device driver, and enable FD hardware[1] on omap4 SoC..
The idea of implementing it on v4l2 is from from Alan Cox, Sylwester
and Greg-Kh.
For verification purpose, I write one user space utility[2] to
test the
Signed-off-by: Ming Lei ming@canonical.com
---
arch/arm/mach-omap2/devices.c | 33 +
1 files changed, 33 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/devices.c b/arch/arm/mach-omap2/devices.c
index 1166bdc..a392af5 100644
---
So that we can reuse vb2_mmap_pfn_range for the coming videobuf2_page
memops.
Signed-off-by: Ming Lei ming@canonical.com
---
drivers/media/video/videobuf2-dma-contig.c |1 +
drivers/media/video/videobuf2-memops.c |1 -
2 files changed, 1 insertions(+), 1 deletions(-)
diff --git
DMA contig memory resource is very limited and precious, also
accessing to it from CPU is very slow on some platform.
For some cases(such as the comming face detection driver), DMA Streaming
buffer is enough, so introduce VIDEOBUF2_PAGE to allocate continuous
physical memory but letting video
This patch introduces two new IOCTLs and related data
structure defination which will be used by the coming
face detection video device.
The two IOCTLs and related data structure are used by
user space application to retrieve the results of face
detection. They can be called after one v4l2_buffer
This patch introduces one driver for face detection purpose.
The driver is responsible for all v4l2 stuff, buffer management
and other general things, and doesn't touch face detection hardware
directly. Several interfaces are exported to low level drivers
(such as the coming omap4 FD driver)which
The patch introduces one face detection device driver for
driving face detection hardware on omap4[1].
Most things of the driver are dealing with omap4 face detection
hardware.
This driver is platform independent, so in theory it can
be used to drive same IP module on other platforms.
[1], Ch9
Signed-off-by: Ming Lei ming@canonical.com
---
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 81
1 files changed, 81 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
index
[..]
diff --git a/arch/arm/mach-omap2/prm-regbits-33xx.h
b/arch/arm/mach-omap2/prm-regbits-33xx.h
new file mode 100644
index 000..5299287
--- /dev/null
+++ b/arch/arm/mach-omap2/prm-regbits-33xx.h
@@ -0,0 +1,357 @@
+/*
+ * AM33XX Power Management register bits
+ *
+ * Copyright (C) 2011
Hello Juha,
Rajashekhara, Sudhakar wrote:
Hi,
On Fri, Dec 02, 2011 at 14:25:48, Heiko Schocher wrote:
Hello Rajashekhara, Sudhakar,
Rajashekhara, Sudhakar wrote:
Hi,
On Fri, Dec 02, 2011 at 13:05:22, Heiko Schocher wrote:
Hello,
trying Linux 3.2.0-rc3 on an am1808 based board using
Under some error conditions the i2c driver may do a reset.
Adding a reset field and support in the device-specific code.
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
arch/arm/plat-omap/i2c.c | 18 ++
include/linux/i2c-omap.h |1 +
2 files changed, 19 insertions(+),
The SYSC register should not accessed in the driver removing the
define from the driver.
Also clean up the syscstate from the omap_i2c_dev struct.
Acked-by: Santosh Shilimkar santosh.shilim...@ti.com
Signed-off-by: Shubhrajyoti D shubhrajy...@ti.com
---
drivers/i2c/busses/i2c-omap.c |5 -
The series attempts to do the following
- The reset should not be done in the driver
have support for the same.
- Remove the sysc register access in the driver.
Incorporated review comments:
- Fix the indentation.
- Restore in the error path is not needed as we are
doing a init.
-
- The reset in the driver at init is not needed anymore as the
hwmod framework takes care of reseting it.
- Reset is removed from omap_i2c_init, which was called
not only during probe, but also after time out and error handling.
device_reset were added in those places to effect the
Hello,
The following series adds device tree support for omap-dmic, omap-mcpdm ASoC
DAI drivers.
The OMAP4 platform patches have dependency on the DMIC driver series:
http://www.mail-archive.com/linux-omap@vger.kernel.org/msg59161.html
Regards,
Peter
---
Peter Ujfalusi (5):
ASoC: omap-dmic:
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
.../bindings/sound/soc/omap/omap-dmic.txt | 13 +
sound/soc/omap/omap-dmic.c |8
2 files changed, 21 insertions(+), 0 deletions(-)
create mode 100644
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
.../bindings/sound/soc/omap/omap-mcpdm.txt | 13 +
sound/soc/omap/omap-mcpdm.c|8
2 files changed, 21 insertions(+), 0 deletions(-)
create mode 100644
If dtb is provided of will create the needed devices dynamically so there
is no need to create the platform device for McPDM here.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/devices.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git
Add DT support for dmic, and McPDM on OMAP4 platforms.
Panda board does not have DMIC lines accessable, so
disable the dmic on panda.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/boot/dts/omap4-panda.dts |4
arch/arm/boot/dts/omap4.dtsi |9 +
2 files
If dtb is provided of will create the needed devices dynamically so there
is no need to create the platform device for DMIC here.
Signed-off-by: Peter Ujfalusi peter.ujfal...@ti.com
---
arch/arm/mach-omap2/devices.c |4
1 files changed, 4 insertions(+), 0 deletions(-)
diff --git
On Thu, Dec 1, 2011 at 10:42 AM, Artem Bityutskiy dedeki...@gmail.com wrote:
On Tue, 2011-11-29 at 10:00 +0100, Jan Weitzel wrote:
Signed-off-by: Jan Weitzel j.weit...@phytec.de
Pushed to l2-mtd-2.6.git, thank you!
This breaks build here, did you really test it, Jan?
Hi Ming,
On 12/02/2011 10:12 AM, Ming Lei wrote:
Hi,
These v1 patches(against -next tree) introduce v4l2 based face
detection(FD) device driver, and enable FD hardware[1] on omap4 SoC..
The idea of implementing it on v4l2 is from from Alan Cox, Sylwester
and Greg-Kh.
For verification
On Fri, 2011-12-02 at 12:20 +0200, Grazvydas Ignotas wrote:
On Thu, Dec 1, 2011 at 10:42 AM, Artem Bityutskiy dedeki...@gmail.com wrote:
On Tue, 2011-11-29 at 10:00 +0100, Jan Weitzel wrote:
Signed-off-by: Jan Weitzel j.weit...@phytec.de
Pushed to l2-mtd-2.6.git, thank you!
This breaks
Hello.
On 02-12-2011 13:12, Ming Lei wrote:
Signed-off-by: Ming Leiming@canonical.com
---
arch/arm/mach-omap2/devices.c | 33 +
1 files changed, 33 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/devices.c
On Fri, Dec 02, 2011 at 11:52:56AM +0200, Peter Ujfalusi wrote:
+Required properties:
+ - compatible : ti,omap4-dmic
+ - ti,hwmods : List of hwmod names associated with DMIC, in most case
+ it is dmic.
Shouldn't there also be a regs property giving the register window?
--
To
On 12/2/2011 1:25 PM, Mark Brown wrote:
On Fri, Dec 02, 2011 at 11:52:56AM +0200, Peter Ujfalusi wrote:
+Required properties:
+ - compatible : ti,omap4-dmic
+ - ti,hwmods : List of hwmod names associated with DMIC, in most case
+it is dmic.
Shouldn't there also be a regs
On 12/02/2011 02:25 PM, Mark Brown wrote:
On Fri, Dec 02, 2011 at 11:52:56AM +0200, Peter Ujfalusi wrote:
+Required properties:
+ - compatible : ti,omap4-dmic
+ - ti,hwmods : List of hwmod names associated with DMIC, in most case
+ it is dmic.
Shouldn't there also be a
On Friday 02 December 2011 17:12:56 Ming Lei wrote:
+/**
+ * struct v4l2_fd_result - VIDIOC_G_FD_RESULT argument
+ * @buf_index: entry, index of v4l2_buffer for face detection
+ * @face_cnt: return, how many faces detected from the @buf_index
+ * @fd:return, result of faces'
On Fri, Dec 02, 2011 at 02:32:59PM +0200, Peter Ujfalusi wrote:
As of now we receive all these information via OMAP hwmod.
All the properties (addresses, irq, etc) of the HW IP will be coming
from DT as soon as I can remove the ti,hwmod property.
Oh, right. We should really be churning the
On 12/2/2011 2:02 PM, Mark Brown wrote:
On Fri, Dec 02, 2011 at 02:32:59PM +0200, Peter Ujfalusi wrote:
As of now we receive all these information via OMAP hwmod.
All the properties (addresses, irq, etc) of the HW IP will be coming
from DT as soon as I can remove the ti,hwmod property.
Oh,
Hi, Sergio
This change in interface is not used from the omap4iss driver.
You could drop it from the patch set, if so.
On 12/01/2011 02:14 AM, Sergio Aguirre wrote:
From: Stanimir Varbanov svarba...@mm-sol.com
Introduce g_interface_parms sensor operation for getting sensor
interface
On Fri, Dec 02, 2011 at 02:31:13PM +0100, Cousson, Benoit wrote:
Even if the reg-names and interrupts-names are accepted, which is
still not obvious due to a little bit of resistance, we still do not
Yeah, it seems like there's very little traction on any of the problems
with legacy bindings
Hi,
On Fri, Dec 2, 2011 at 6:28 PM, Sylwester Nawrocki snj...@gmail.com wrote:
Hi Ming,
On 12/02/2011 10:12 AM, Ming Lei wrote:
Hi,
These v1 patches(against -next tree) introduce v4l2 based face
detection(FD) device driver, and enable FD hardware[1] on omap4 SoC..
The idea of implementing
On 12/2/2011 3:00 PM, Mark Brown wrote:
On Fri, Dec 02, 2011 at 02:31:13PM +0100, Cousson, Benoit wrote:
Even if the reg-names and interrupts-names are accepted, which is
still not obvious due to a little bit of resistance, we still do not
Yeah, it seems like there's very little traction on
Hi,
These v1 patches(against -next tree) introduce v4l2 based face
detection(FD) device driver, and enable FD hardware[1] on omap4 SoC..
The idea of implementing it on v4l2 is from from Alan Cox, Sylwester
and Greg-Kh.
For verification purpose, I write one user space utility[2] to
test the
So that we can reuse vb2_mmap_pfn_range for the coming videobuf2_page
memops.
Signed-off-by: Ming Lei ming@canonical.com
---
drivers/media/video/videobuf2-dma-contig.c |1 +
drivers/media/video/videobuf2-memops.c |1 -
2 files changed, 1 insertions(+), 1 deletions(-)
diff --git
The patch introduces one face detection device driver for
driving face detection hardware on omap4[1].
Most things of the driver are dealing with omap4 face detection
hardware.
This driver is platform independent, so in theory it can
be used to drive same IP module on other platforms.
[1], Ch9
Signed-off-by: Ming Lei ming@canonical.com
---
arch/arm/mach-omap2/omap_hwmod_44xx_data.c | 81
1 files changed, 81 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
b/arch/arm/mach-omap2/omap_hwmod_44xx_data.c
index
Signed-off-by: Ming Lei ming@canonical.com
---
arch/arm/mach-omap2/devices.c | 33 +
1 files changed, 33 insertions(+), 0 deletions(-)
diff --git a/arch/arm/mach-omap2/devices.c b/arch/arm/mach-omap2/devices.c
index 1166bdc..a392af5 100644
---
DMA contig memory resource is very limited and precious, also
accessing to it from CPU is very slow on some platform.
For some cases(such as the comming face detection driver), DMA Streaming
buffer is enough, so introduce VIDEOBUF2_PAGE to allocate continuous
physical memory but letting video
This patch introduces two new IOCTLs and related data
structure defination which will be used by the coming
face detection video device.
The two IOCTLs and related data structure are used by
user space application to retrieve the results of face
detection. They can be called after one v4l2_buffer
This patch introduces one driver for face detection purpose.
The driver is responsible for all v4l2 stuff, buffer management
and other general things, and doesn't touch face detection hardware
directly. Several interfaces are exported to low level drivers
(such as the coming omap4 FD driver)which
On Fri, Dec 02, 2011 at 03:59:01PM +0100, Cousson, Benoit wrote:
On 12/2/2011 3:00 PM, Mark Brown wrote:
At least the DMA bindings seem fairly well sorted - we just merged the
Tegra audio bindings which define a Tegra property for the DMA request
signal. There's a reasonable amount of
Hi Stan,
On Fri, Dec 2, 2011 at 7:32 AM, Stanimir Varbanov svarba...@mm-sol.com wrote:
Hi, Sergio
This change in interface is not used from the omap4iss driver.
You could drop it from the patch set, if so.
Oops, yes... I used to depend on this for my soc_camera implementation before...
Enable TSC2005 touchscreen driver on the RX-51 board by providing the
needed platform data.
Signed-off-by: Aaro Koskinen aaro.koski...@nokia.com
---
Tony, this patch has been forgotten, any chance to get it
into 3.3?
arch/arm/mach-omap2/board-rx51-peripherals.c | 46
Hi Ming,
Thanks for the patches.
On Fri, Dec 2, 2011 at 9:02 AM, Ming Lei ming@canonical.com wrote:
Signed-off-by: Ming Lei ming@canonical.com
---
arch/arm/mach-omap2/devices.c | 33 +
1 files changed, 33 insertions(+), 0 deletions(-)
diff --git
Hi Ming,
On Fri, Dec 2, 2011 at 3:12 AM, Ming Lei ming@canonical.com wrote:
DMA contig memory resource is very limited and precious, also
accessing to it from CPU is very slow on some platform.
For some cases(such as the comming face detection driver), DMA Streaming
buffer is enough, so
Kevin,
-Original Message-
From: Vishwanath Sripathy [mailto:vishwanath...@ti.com]
Sent: Wednesday, November 30, 2011 2:58 PM
To: Kevin Hilman
Cc: linux-omap@vger.kernel.org; linux-arm-ker...@lists.infradead.org
Subject: RE: [PATCHv2 0/7]ARM: OMAP3PLUS PM: Add IO DaisyChain
support
On Friday 02 of December 2011 at 03:09:37, Tony Lindgren wrote:
* Janusz Krzysztofik jkrzy...@tis.icnet.pl [111201 11:38]:
After dpll1 reprogramming has been moved from setup_arch() to
kernel_init(), I've been observing several issues, resulting in
undesired system behaviour on my Amstrad
Hi Russell,
On Thu, 1 Dec 2011, Russell King - ARM Linux wrote:
On Wed, Nov 30, 2011 at 06:20:50PM -0700, Paul Walmsley wrote:
1. When a clock user calls clk_enable() on a clock, the clock framework
should prevent other users of the clock from changing the clock's rate.
This should
On Fri, Dec 2, 2011 at 2:20 AM, Grazvydas Ignotas nota...@gmail.com wrote:
On Thu, Dec 1, 2011 at 10:42 AM, Artem Bityutskiy dedeki...@gmail.com wrote:
On Tue, 2011-11-29 at 10:00 +0100, Jan Weitzel wrote:
Signed-off-by: Jan Weitzel j.weit...@phytec.de
Pushed to l2-mtd-2.6.git, thank you!
Mohammed, Afzal af...@ti.com writes:
Hi Kevin,
On Thu, Dec 01, 2011 at 20:40:03, Hilman, Kevin wrote:
Hiremath, Vaibhav hvaib...@ti.com writes:
:
We can detect the board using on-board EEPROM, so same mach-id
should work for both EVM and Beagle.
And also going forward with device
Rajendra Nayak rna...@ti.com writes:
[..]
First some general comments:
At first glance, it seems like there could be much more reuse with OMAP4
code here. From what I see, AM33x has only one partition compared to
several on OMAP4, but that doesn't mean you couldn't reuse the OMAP4
Dave,
Kevin Hilman khil...@ti.com writes:
Hi Dave,
Here's the updated pull request after a rebase onto v3.2-rc1 and some
fixes to address other changes that went into v3.2.
This is targetted for v3.3, so I'd like to get it into your tree and
into linux-next.
Are there any problems with
On Fri, Dec 02, 2011 at 09:45:17AM -0800, Kevin Hilman wrote:
Dave,
Kevin Hilman khil...@ti.com writes:
Hi Dave,
Here's the updated pull request after a rebase onto v3.2-rc1 and some
fixes to address other changes that went into v3.2.
This is targetted for v3.3, so I'd
On Thu, Dec 01, 2011 at 06:34:19, Hilman, Kevin wrote:
Vaibhav Hiremath hvaib...@ti.com writes:
From: Afzal Mohammed af...@ti.com
This patch adds AM33XX power domain data,
corresponding API's to access PRM module and
PRM register offsets bit fields.
Signed-off-by: Rachna Patil
Booting the Linux kernel on Nokia RM-680 board has been broken since
2.6.39 due to the following:
[0.217193] omap_hwmod: timer12: enabling
[0.221435] Unhandled fault: external abort on non-linefetch (0x1028) at
0xfa304010
[0.229431] Internal error: : 1028 [#1] SMP
[0.233825]
On Fri, Dec 02, 2011 at 12:52:57PM -0500, Dave Jones wrote:
On Fri, Dec 02, 2011 at 09:45:17AM -0800, Kevin Hilman wrote:
Dave,
Kevin Hilman khil...@ti.com writes:
Hi Dave,
Here's the updated pull request after a rebase onto v3.2-rc1 and some
fixes to
On Fri, Dec 02, 2011 at 10:13:10AM -0700, Paul Walmsley wrote:
Hi Russell,
On Thu, 1 Dec 2011, Russell King - ARM Linux wrote:
On Wed, Nov 30, 2011 at 06:20:50PM -0700, Paul Walmsley wrote:
1. When a clock user calls clk_enable() on a clock, the clock framework
should prevent other
Hello,
On Fri, Dec 02, 2011 at 08:23:06PM +, Russell King - ARM Linux wrote:
On Fri, Dec 02, 2011 at 10:13:10AM -0700, Paul Walmsley wrote:
Hi Russell,
On Thu, 1 Dec 2011, Russell King - ARM Linux wrote:
On Wed, Nov 30, 2011 at 06:20:50PM -0700, Paul Walmsley wrote:
1. When
Dave Jones da...@redhat.com writes:
On Fri, Dec 02, 2011 at 12:52:57PM -0500, Dave Jones wrote:
On Fri, Dec 02, 2011 at 09:45:17AM -0800, Kevin Hilman wrote:
Dave,
Kevin Hilman khil...@ti.com writes:
Hi Dave,
Here's the updated pull request after a
Nori, Sekhar nsek...@ti.com writes:
On Thu, Dec 01, 2011 at 06:34:19, Hilman, Kevin wrote:
Vaibhav Hiremath hvaib...@ti.com writes:
From: Afzal Mohammed af...@ti.com
This patch adds AM33XX power domain data,
corresponding API's to access PRM module and
PRM register offsets bit
Hi Shubhrajyoti,
On 12/2/2011 3:21, Shubhrajyoti D wrote:
- The reset in the driver at init is not needed anymore as the
hwmod framework takes care of reseting it.
- Reset is removed from omap_i2c_init, which was called
not only during probe, but also after time out and error
Hi Shubhrajyoti,
On 12/2/2011 15:37, Jon Hunter wrote:
[snip]
@@ -594,6 +545,11 @@ static int omap_i2c_xfer_msg(struct i2c_adapter
*adap,
return r;
if (r == 0) {
dev_err(dev-dev, controller timed out\n);
+ if (dev-device_reset) {
+ r = dev-device_reset(dev-dev);
+ if (r 0)
+ dev_err(dev-dev,
Bedia, Vaibhav vaibhav.be...@ti.com writes:
Hi,
On Thu, Nov 17, 2011 at 21:58:23, Bedia, Vaibhav wrote:
TI processors in TI81x and AM33x family work with PMICs like
TPS65910/1 which are not part of the TWL series. These processors
also do not have a voltage controller/processor module.
Shubhrajyoti D shubhrajy...@ti.com writes:
On OMAP4 we were writing 1 to IRQENABLE_CLR which cleared only
the arbitration lost interrupt however for other ips (not
OMAP_I2C_IP_VERSION_2)
we clear all the interrupts at idle. The patch intends to fix the same by
writing 0 to the
IE
Sergio Aguirre saagui...@ti.com writes:
NOTE: This isn't the whole list of features that the
ISS supports, but the only ones supported at the moment.
Signed-off-by: Sergio Aguirre saagui...@ti.com
[...]
diff --git a/arch/arm/plat-omap/include/plat/omap44xx.h
+Benoit,
Aguirre, Sergio saagui...@ti.com writes:
Hi Vaibhav,
Thanks for the comments.
On Thu, Dec 1, 2011 at 12:34 AM, Hiremath, Vaibhav hvaib...@ti.com wrote:
-Original Message-
From: linux-media-ow...@vger.kernel.org [mailto:linux-media-
ow...@vger.kernel.org] On Behalf Of
Hi Kevin,
Thanks for the review.
On Fri, Dec 2, 2011 at 4:49 PM, Kevin Hilman khil...@ti.com wrote:
+Benoit,
Aguirre, Sergio saagui...@ti.com writes:
Hi Vaibhav,
Thanks for the comments.
On Thu, Dec 1, 2011 at 12:34 AM, Hiremath, Vaibhav hvaib...@ti.com wrote:
-Original
Hi Kevin,
Thanks for the review.
On Fri, Dec 2, 2011 at 4:45 PM, Kevin Hilman khil...@ti.com wrote:
Sergio Aguirre saagui...@ti.com writes:
NOTE: This isn't the whole list of features that the
ISS supports, but the only ones supported at the moment.
Signed-off-by: Sergio Aguirre
Aguirre, Sergio saagui...@ti.com writes:
[...]
Also, work with Benoit to make sure at the scripts that autogenerate
this data are updated to include these two regions.
Ok.
As a side note, I might need more addresses for the rest of the ISP
components later on. I'll enable more subsystems
Tero Kristo t-kri...@ti.com writes:
OMAP3 uses the default settings for VDD1 channel, otherwise the settings will
overlap with VDD2 and attempting to modify VDD1 voltage will actually change
VDD2 voltage.
Signed-off-by: Tero Kristo t-kri...@ti.com
I've forgotten a bit how this was supposed
Tero Kristo t-kri...@ti.com writes:
VDD1 and VDD2 are the core voltage regulators on OMAP3. VDD1 is used
to control MPU/IVA voltage, and VDD2 is used for CORE. These regulators
are needed by DVFS.
Signed-off-by: Tero Kristo t-kri...@ti.com
[...]
+static struct regulator_init_data
On Thu, 1 Dec 2011, Russell King - ARM Linux wrote:
On Thu, Dec 01, 2011 at 11:30:16AM -0700, Paul Walmsley wrote:
The intention behind the clk_{allow,block}_rate_change() proposal was to
allow the current user of the clock to change its rate without having to
call
77 matches
Mail list logo
