mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Gareth Randall <gareth.randall@virgin.net>
To: abhi1.singh@samsung.com
Cc: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	SRI-N IT Security <sri-n.itsec@samsung.com>
Subject: Re: [PATCH] input: gpio-keys - optimize wakeup sequence.
Date: Wed, 18 Oct 2023 22:49:44 +0100	[thread overview]
Message-ID: <11a2da09-bd42-4a2f-9b4b-a4c1b019e8aa@virgin.net> (raw)
In-Reply-To: <1830198030.734987.1697538855953@mail-kr5-1.mail-kr5.knoxportal-kr-prod-blue.svc.cluster.local>

Dear Mr Singh,

I am not a maintainer but can point out some issues you need to resolve 
with this post.

1. Put the patch in the body of the email and not in an attachment.
2. You need a "Signed-off-by:" line.
3. The email needs to start with a description of the what the patch 
resolves. Don't put "suggested changes".

There are probably other issues as well but I hope this helps you to get 
started. Note that I am not involved in the review process.

Yours,

Gareth

On 17/10/2023 11:34, Abhishek Kumar Singh wrote:
> Dear Mr. Dmitry,
> 
> Greetings!
> 
> 
> 
> This patch is related to optimization in input key event driver of Kernel module.
> 
> Suggested change to avoid the many APIs call chain if there is no key press event triggered.
> 
> 
> 
> There is a call back function gpio_keys_resume() called for every suspend/resume of the device.
> 
> And whenever this function is called, it is reading the status of the key.
> 
> And gpio_keys_resume() API further calls the below chain of API irrespective of key press event.
> 
> 
> 
> APIs call chain:
> 
> static void gpio_keys_report_state(struct gpio_keys_drvdata *ddata)
> 
> static void gpio_keys_gpio_report_event(struct gpio_button_data *bdata)
> 
> gpiod_get_value_cansleep(bdata->gpiod);
> 
> input_event(input, type, *bdata->code, state);
> 
> input_sync(input);
> 
> 
> 
> 
> Suggested changes to avoid the above APIs call chain if there is no key press event triggered.
> 
> It will save the device computational resources, power resources and optimize the suspend/resume time"
> 
> 
> Please help to review the attached patch and integrate in main line kernel code.
> 
>   
> 
> 
> 
> Thanks and Regards,
> Abhishek Kumar Singh
> Sr. Chief Engineer, Samsung Electronics, Noida-India


  reply	other threads:[~2023-10-18 21:53 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20231017103415epcms5p2f8f5b28a8f5d71055622b82f71b0fc93@epcms5p2>
2023-10-17 10:34 ` Abhishek Kumar Singh
2023-10-18 21:49   ` Gareth Randall [this message]
     [not found] <CGME20231017103415epcms5p2f8f5b28a8f5d71055622b82f71b0fc93@epcms5p4>
2023-10-26  5:53 ` Abhishek Kumar Singh
2023-10-29  2:11   ` dmitry.torokhov

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=11a2da09-bd42-4a2f-9b4b-a4c1b019e8aa@virgin.net \
    --to=gareth.randall@virgin.net \
    --cc=abhi1.singh@samsung.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=sri-n.itsec@samsung.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®