On Thu, Jul 21, 2016 at 01:55:55PM -0700, Hoan Tran wrote:
> This patch adds the APM X-Gene hwmon device tree node documentation.
>
> Signed-off-by: Hoan Tran
> Acked-by: Rob Herring
Applied to hwmon-next.
Thanks,
Guenter
--
To unsubscribe from this list: send the line "unsubscribe linux-doc"
, "APM X-Gene SoC HW monitor driver registered\n");
> +
> + return rc;
> +
Nitpick: rc == 0 here, so return 0; is a better choice.
Otherwise looks good.
Reviewed-by: Guenter Roeck
Note that I can not apply the patch at this time due to its dependency.
Guenter
--
To unsubsc
On Thu, Jul 21, 2016 at 01:55:57PM -0700, Hoan Tran wrote:
> This patch adds DT node to enable hwmon driver for APM X-Gene SoC.
>
> Signed-off-by: Hoan Tran
Acked-by: Guenter Roeck
> ---
> arch/arm64/boot/dts/apm/apm-shadowcat.dtsi | 5 +
> arch/arm64/boot/dts/apm/apm-
On 07/21/2016 03:37 PM, Hoan Tran wrote:
This patch set adds hardware temperature and power reading support for
APM X-Gene SoC using the mailbox communication interface.
For device tree, it is the standard DT mailbox.
For ACPI, it is the PCC mailbox.
For ACPI, this patch is built on top and depe
On Wed, Sep 07, 2016 at 11:41:44PM +0200, Arnd Bergmann wrote:
> On Thursday, July 21, 2016 1:55:56 PM CEST Hoan Tran wrote:
> > + ctx->comm_base_addr = cppc_ss->base_address;
> > + if (ctx->comm_base_addr) {
> > + ctx->pcc_comm_addr =
> > +
On Wed, Sep 07, 2016 at 11:41:44PM +0200, Arnd Bergmann wrote:
> On Thursday, July 21, 2016 1:55:56 PM CEST Hoan Tran wrote:
> > + ctx->comm_base_addr = cppc_ss->base_address;
> > + if (ctx->comm_base_addr) {
> > + ctx->pcc_comm_addr =
> > +
On 09/08/2016 01:15 AM, Arnd Bergmann wrote:
On Wednesday, September 7, 2016 3:27:54 PM CEST Guenter Roeck wrote:
On Wed, Sep 07, 2016 at 11:41:44PM +0200, Arnd Bergmann wrote:
On Thursday, July 21, 2016 1:55:56 PM CEST Hoan Tran wrote:
+ ctx->comm_base_addr = cppc
Hi Arnd,
On Fri, Sep 09, 2016 at 05:38:58PM +0200, Arnd Bergmann wrote:
> The newly added hwmon driver fails to build in an allmodconfig
> kernel:
>
> 1 ERROR: "memblock_is_memory" [drivers/hwmon/xgene-hwmon.ko] undefined!
>
> According to comments in the code, the mailbox is a shared mem
On Fri, Sep 09, 2016 at 10:10:45PM +0200, Arnd Bergmann wrote:
> The newly added hwmon driver fails to build in an allmodconfig
> kernel:
>
> ERROR: "memblock_is_memory" [drivers/hwmon/xgene-hwmon.ko] undefined!
>
> According to comments in the code, the mailbox is a shared memory region,
>
From: Guenter Roeck
The watchdog infrastructure is currently purely passive, meaning
it only passes information from user space to drivers and vice versa.
Since watchdog hardware tends to have its own quirks, this can result
in quite complex watchdog drivers. A number of scanarios are
From: Guenter Roeck
Drop 'cancel' parameter; simply cancel worker unconditionally
if not needed.
Signed-off-by: Guenter Roeck
---
v7: Rebased to v4.5-rc1
v6: Rebased to v4.4-rc2
v5: Introduced patch
---
drivers/watchdog/watchdog_dev.c | 15 +++
1 file changed, 7 insert
From: Guenter Roeck
Introduce an optional hardware maximum timeout in the watchdog core.
The hardware maximum timeout can be lower than the maximum timeout.
Drivers can set the maximum hardware timeout value in the watchdog data
structure. If the configured timeout exceeds the maximum hardware
From: Guenter Roeck
Some watchdogs require a minimum time between heartbeats.
Examples are the watchdogs in DA9062 and AT91SAM9x.
Signed-off-by: Guenter Roeck
---
v7: Rebased to v4.5-rc1
v6: Rebased to v4.4-rc2
v5: Rebased to v4.4-rc1
Fixed typo in documentation.
v4: Added patch
From: Guenter Roeck
For some watchdogs, the hardware timeout is fixed, and the
watchdog driver depends on the watchdog core to handle the
actual timeout. In this situation, the watchdog driver might
only set the 'timeout' variable but do nothing else.
This can as well be hand
From: Guenter Roeck
Convert driver to use watchdog infrastructure. This includes
infrastructure support to handle watchdog keepalive if the watchdog
is running while the watchdog device is closed.
Signed-off-by: Guenter Roeck
---
v7: Set max_hw_timeout_ms
Rebased to v4.5-rc1
v6: Added
From: Guenter Roeck
The WDOG_HW_RUNNING flag is expected to be set by watchdog drivers if
the hardware watchdog is running. If the flag is set, the watchdog
subsystem will ping the watchdog even if the watchdog device is closed.
The watchdog driver stop function is now optional and may be
From: Guenter Roeck
The watchdog infrastructure now supports handling watchdog keepalive
if the watchdog is running while the watchdog device is closed.
Convert the driver to use this infrastructure.
Signed-off-by: Guenter Roeck
---
v7: Set max_hw_timeout_ms
Rebased to v4.5-rc1
v6: Rename
From: Guenter Roeck
The watchdog infrastructure now supports handling watchdog keepalive
if the watchdog is running while the watchdog device is closed.
The infrastructure now also supports generating additional heartbeats
if the maximum hardware timeout is smaller than or close to the
From: Guenter Roeck
The watchdog infrastructure now supports handling watchdog keepalive
if the watchdog is running while the watchdog device is closed.
Convert the driver to use this infrastructure.
Signed-off-by: Guenter Roeck
---
v7: Set max_hw_timeout_ms
Rebased to v4.5-rc1
v6: Rename
Hi Uwe,
On 01/26/2016 12:07 AM, Uwe Kleine-König wrote:
Hello Guenter,
On Mon, Jan 25, 2016 at 06:53:11PM -0800, Guenter Roeck wrote:
From: Guenter Roeck
Some watchdogs require a minimum time between heartbeats.
Examples are the watchdogs in DA9062 and AT91SAM9x.
Signed-off-by: Guenter
Hi Uwe,
On 01/26/2016 12:09 AM, Uwe Kleine-König wrote:
Hello Guenter,
On Mon, Jan 25, 2016 at 06:53:07PM -0800, Guenter Roeck wrote:
Patch #1 adds timer functionality to the watchdog core. It solves the problem
of short maximum hardware timeouts by augmenting heartbeats triggered from
user
Hi Doug,
On 01/29/2016 09:52 AM, Doug Anderson wrote:
Guenter,
On Mon, Jan 25, 2016 at 6:53 PM, Guenter Roeck
wrote:
From: Guenter Roeck
Convert driver to use watchdog infrastructure. This includes
infrastructure support to handle watchdog keepalive if the watchdog
is running while the
On 01/25/2016 06:53 PM, Guenter Roeck wrote:
From: Guenter Roeck
The watchdog infrastructure now supports handling watchdog keepalive
if the watchdog is running while the watchdog device is closed.
Convert the driver to use this infrastructure.
Signed-off-by: Guenter Roeck
I managed to
On 02/03/2016 03:00 PM, Fu Wei wrote:
On 4 February 2016 at 02:45, Timur Tabi wrote:
Fu Wei wrote:
As you know I have made the pre-timeout support patch, If people like
it, i am happy to go on upstream it separately.
If we want to use pre-timeout here, user only can use get_pretimeout
and di
On 02/04/2016 05:48 AM, Timur Tabi wrote:
Guenter Roeck wrote:
Also, if panic is enabled, the timeout needs to be adjusted accordingly
(to only panic after the entire timeout period has expired, not after
half of it). We can not panic the system after timeout / 2.
It's a debugging fe
On 02/04/2016 08:37 AM, Timur Tabi wrote:
Will Deacon wrote:
+static int sbsa_gwdt_keepalive(struct watchdog_device *wdd)
>+{
>+struct sbsa_gwdt *gwdt = to_sbsa_gwdt(wdd);
>+
>+/*
>+* Writing WRR for an explicit watchdog refresh.
>+* You can write anyting(like 0xc0ffee).
>+*/
On 02/04/2016 08:32 AM, Mathieu Poirier wrote:
On 3 February 2016 at 10:18, wrote:
From: Fu Wei
This patch registers the WS0 interrupt routine to trigger panic,
when the watchdog reachs the first stage (the half timeout).
This function can help administrator to backup the system context
info
On 02/05/2016 01:51 AM, Fu Wei wrote:
Hi Guenter,
On 4 February 2016 at 13:17, Guenter Roeck wrote:
On 02/03/2016 03:00 PM, Fu Wei wrote:
On 4 February 2016 at 02:45, Timur Tabi wrote:
Fu Wei wrote:
As you know I have made the pre-timeout support patch, If people like
it, i am happy
On 02/05/2016 10:21 AM, Fu Wei wrote:
On 5 February 2016 at 22:42, Guenter Roeck wrote:
On 02/05/2016 01:51 AM, Fu Wei wrote:
Hi Guenter,
On 4 February 2016 at 13:17, Guenter Roeck wrote:
On 02/03/2016 03:00 PM, Fu Wei wrote:
On 4 February 2016 at 02:45, Timur Tabi wrote:
Fu Wei
On 02/06/2016 10:02 AM, Fu Wei wrote:
Hi Guenter,
On 6 February 2016 at 07:54, Guenter Roeck wrote:
On 02/05/2016 10:21 AM, Fu Wei wrote:
On 5 February 2016 at 22:42, Guenter Roeck wrote:
On 02/05/2016 01:51 AM, Fu Wei wrote:
Hi Guenter,
On 4 February 2016 at 13:17, Guenter Roeck
Hi,
On Sat, Nov 02, 2024 at 10:51:10AM -0700, Rong Xu wrote:
> When the -ffunction-sections compiler option is enabled, each function
> is placed in a separate section named .text.function_name rather than
> putting all functions in a single .text section.
>
...
>
> Co-developed-by: Han Shen
>
On Wed, Feb 05, 2025 at 09:48:16AM +1100, Alistair Popple wrote:
> Currently fs dax pages are considered free when the refcount drops to
> one and their refcounts are not increased when mapped via PTEs or
> decreased when unmapped. This requires special logic in mm paths to
> detect that these page
301 - 332 of 332 matches
Mail list logo
