All of lore.kernel.org
 help / color / mirror / Atom feed
From: deller@kernel.org
To: linux-parisc@vger.kernel.org
Cc: Helge Deller <deller@gmx.de>
Subject: [PATCH 3/3] parisc: chassis: Do not overwrite LCD display
Date: Fri, 25 Aug 2023 20:09:28 +0200	[thread overview]
Message-ID: <20230825180928.205499-3-deller@kernel.org> (raw)
In-Reply-To: <20230825180928.205499-1-deller@kernel.org>

From: Helge Deller <deller@gmx.de>

If we have the LCD/LED driver and tell PDC about a status change
of the system, PDC will usually overwrite the contents on the LCD.

To avoid that, just write the LCD string again via the LCD driver.

Signed-off-by: Helge Deller <deller@gmx.de>
---
 arch/parisc/kernel/pdc_chassis.c | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/arch/parisc/kernel/pdc_chassis.c b/arch/parisc/kernel/pdc_chassis.c
index 0a9d7008ef2a..d477d0177c2f 100644
--- a/arch/parisc/kernel/pdc_chassis.c
+++ b/arch/parisc/kernel/pdc_chassis.c
@@ -31,6 +31,7 @@
 #include <asm/processor.h>
 #include <asm/pdc.h>
 #include <asm/pdcpat.h>
+#include <asm/led.h>
 
 #define PDC_CHASSIS_VER	"0.05"
 
@@ -234,6 +235,11 @@ int pdc_chassis_send_status(int message)
 		} else retval = -1;
 #endif /* CONFIG_64BIT */
 	}	/* if (pdc_chassis_enabled) */
+
+	/* if system has LCD display, update current string */
+	if (retval != -1 && IS_ENABLED(CONFIG_CHASSIS_LCD_LED))
+		lcd_print(NULL);
+
 #endif /* CONFIG_PDC_CHASSIS */
 	return retval;
 }
-- 
2.41.0


  parent reply	other threads:[~2023-08-25 18:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-25 18:09 [PATCH 1/3] parisc: led: Reduce CPU overhead for disk & lan LED computation deller
2023-08-25 18:09 ` [PATCH 2/3] parisc: led: Switch LCD/LED driver to use a kthread deller
2023-08-25 18:09 ` deller [this message]
2023-08-26  7:34 ` [PATCH 1/3] parisc: led: Reduce CPU overhead for disk & lan LED computation Greg KH
2023-08-26  7:54   ` Helge Deller
2023-08-26  7:58     ` Greg KH
2023-08-26  8:12       ` Helge Deller

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230825180928.205499-3-deller@kernel.org \
    --to=deller@kernel.org \
    --cc=deller@gmx.de \
    --cc=linux-parisc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.