W dniu 2015-08-10 o 14:22, Fabio Estevam pisze:
On Mon, Aug 10, 2015 at 9:12 AM, Stefan Wahren wrote:
/* set baud rate */
- baud = uart_get_baud_rate(u, termios, old, 0, u->uartclk);
+ baud_min = u->uartclk * 32 / 0x3fffc0;
+ baud_max = u->uartclk * 32 / 0xec;
+
W dniu 2015-02-09 o 10:44, Jon Medhurst (Tixy) pisze:
Hi Janusz
On Thu, 2015-02-05 at 16:17 +0100, Janusz Użycki wrote:
I got the compilation error on next-20150204:
[...]
In file included from arch/arm/probes/kprobes/core.c:37:
arch/arm/probes/kprobes/core.h:43: error: '[*]' n
Hi,
I got the compilation error on next-20150204:
CC arch/arm/probes/kprobes/actions-arm.o
In file included from arch/arm/probes/kprobes/actions-common.c:18:
arch/arm/probes/kprobes/core.h:43: error: '[*]' not allowed in other
than a declaration
make[2]: *** [arch/arm/probes/kprobes/act
W dniu 2014-12-12 o 11:47, Philipp Zabel pisze:
Some board designers, when running out of clock output pads, decide to
(mis)use PWM output pads to provide a clock to external components.
This driver supports this practice by providing an adapter between the
PWM and clock bindings in the device t
,
.recalc_rate = clk_pwm_recalc_rate,
};
What do you think about?
best regards
Janusz
W dniu 2014-12-11 o 18:02, Janusz Użycki pisze:
Hi again,
Part of my .config:
CONFIG_TREE_PREEMPT_RCU=y
CONFIG_PREEMPT_RCU=y
CONFIG_RCU_STALL_COMMON=y
CONFIG_PREEMPT=y
CONFIG_PREEMPT_COUNT=y
However the patch does
econd for
pwm's clock (clk_prepare_enable/clk_disable_unprepare).
Any idea? How does it work for you?
thanks,
Janusz
W dniu 2014-12-11 o 17:17, Janusz Użycki pisze:
Hi Philipp,
W dniu 2014-12-10 o 15:59, Philipp Zabel pisze:
Hi Janusz,
thank you for the comments.
Am Dienstag, den 09.
Hi Philipp,
W dniu 2014-12-10 o 15:59, Philipp Zabel pisze:
Hi Janusz,
thank you for the comments.
Am Dienstag, den 09.12.2014, 17:49 +0100 schrieb Janusz Użycki:
[...]
[...]
+ pwm = devm_pwm_get(&pdev->dev, NULL);
NULL or clk_name ?
There's only one pwm input to the pwm
W dniu 2014-12-09 o 16:19, Philipp Zabel pisze:
Some board designers, when running out of clock output pads, decide to
(mis)use PWM output pads to provide a clock to external components.
This driver supports this practice by providing an adapter between the
PWM and clock bindings in the device t
Hi Philipp,
W dniu 2014-12-09 o 10:15, Philipp Zabel pisze:
Hi Janusz,
Am Montag, den 08.12.2014, 21:03 +0100 schrieb Janusz Użycki:
Hi,
I've fixed my pwm driver and I can enable 12MHz 50% output using sysfs.
Then I rebased the pwm-clock to 3.14.
I have connected mcp2515 and it works
value is about 12.048MHz instead of 12.0MHz.
While PWM block is clocked 24MHz and the pwm generates exactly 12MHz
the pwm-clock driver returns drifted value. Using clock-frequency like
fixed-clock does could simply solve the binding problem.
thanks,
Janusz
W dniu 2014-12-04 o 19:00, Janusz Użycki
Hi,
W dniu 2014-11-03 o 10:31, Philipp Zabel pisze:
Some board designers, when running out of clock output pads, decide to
(mis)use PWM output pads to provide a clock to external components.
This driver supports this practice by providing an adapter between the
PWM and clock bindings in the devi
Hello,
W dniu 2014-11-25 o 08:37, Alexandre Courbot pisze:
On Wed, Nov 19, 2014 at 7:09 PM, Uwe Kleine-König
wrote:
Hello Alexandre,
On Wed, Nov 19, 2014 at 06:07:50PM +0900, Alexandre Courbot wrote:
On Wed, Nov 19, 2014 at 6:02 PM, Uwe Kleine-König
wrote:
I'd make gpiod_get_direction st
W dniu 2014-09-27 o 22:01, Mike Turquette pisze:
Quoting Thierry Reding (2014-09-23 01:51:31)
On Wed, Sep 10, 2014 at 10:05:17PM +0200, Janusz Użycki wrote:
Hi,
http://patchwork.ozlabs.org/patch/359069/
https://lkml.org/lkml/2014/6/12/186
Will the patch ever included to linux-next?
I&#x
Hi,
http://patchwork.ozlabs.org/patch/359069/
https://lkml.org/lkml/2014/6/12/186
Will the patch ever included to linux-next?
pwm_config() API could be extended to support
not only period [ns] and duty [ns] time
but also frequency [Hz] and duty cycle fraction [1/1000?]
(instead of time in ns)
Hi.
http://www.spinics.net/lists/linux-watchdog/msg04055.html
The patch is little similar to mine.
I see the proposal http://www.spinics.net/lists/linux-watchdog/msg05004.html
need our common forward evaluation. We all have similar needs.
I propose to add to my initial patch rootfs's warm-up ti
Hello.
Please join to the watchdog_dev thread:
http://www.spinics.net/lists/linux-watchdog/msg05004.html.
best regards
Janusz
W dniu 2014-09-09 12:29, Lisovy Rostislav pisze:
Hello;
If my understanding is correct, the purpose of the "watchdog subsystem"
is to provide an unified interface fro
Hi,
Some applications require to start watchdog before userspace software.
This patch enables such feature. Only WATCHDOG_KERNEL_PING flag is necessary to
enable it (attached example for stmp3xxx_rtc_wdt.c).
Moreover kernel's ping is re-enabled when userspace software closed watchdog
using the
Hi,
Some applications require to start watchdog before userspace software.
This patch enables such feature. Only WATCHDOG_KERNEL_PING flag is necessary to
enable it (attached example for stmp3xxx_rtc_wdt.c).
Moreover kernel's ping is re-enabled when userspace software closed watchdog
using the
Hi,
Some applications require to start watchdog before userspace software.
This patch enables such feature. Only WATCHDOG_KERNEL_PING flag is
necessary to enable it (attached example for stmp3xxx_rtc_wdt.c).
Moreover kernel's ping is re-enabled when userspace software closed
watchdog using the
19 matches
Mail list logo
