From: Raag Jadav <raag.jadav@intel.com>
To: linus.walleij@linaro.org, mika.westerberg@linux.intel.com,
andriy.shevchenko@linux.intel.com
Cc: linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org,
mallikarjunappa.sangannavar@intel.com, pandith.n@intel.com,
Raag Jadav <raag.jadav@intel.com>
Subject: [PATCH v3 0/3] Minor improvements for Intel pinctrl
Date: Tue, 13 Jun 2023 14:20:51 +0530 [thread overview]
Message-ID: <20230613085054.10976-1-raag.jadav@intel.com> (raw)
This series implements minor improvements for Intel pinctrl driver.
The optimizations are as tested with gcc 7.5.0 with default -O2.
Changes since v2:
- Drop redundant patches.
- Update commit message.
Changes since v1:
- Update commit message.
- Specify compiler options used to measure optimizations.
- Drop redundant comments.
Raag Jadav (3):
pinctrl: intel: refine ->set_mux() hook
pinctrl: intel: refine ->irq_set_type() hook
pinctrl: intel: simplify exit path of ->gpio_request_enable() hook
drivers/pinctrl/intel/pinctrl-intel.c | 48 +++++++++++++--------------
1 file changed, 24 insertions(+), 24 deletions(-)
--
2.17.1
next reply other threads:[~2023-06-13 8:51 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-13 8:50 Raag Jadav [this message]
2023-06-13 8:50 ` [PATCH v3 1/3] pinctrl: intel: refine ->set_mux() hook Raag Jadav
2023-06-14 16:20 ` Andy Shevchenko
2023-06-13 8:50 ` [PATCH v3 2/3] pinctrl: intel: refine ->irq_set_type() hook Raag Jadav
2023-06-14 16:22 ` Andy Shevchenko
2023-06-15 9:48 ` Jadav, Raag
2023-06-15 9:55 ` mika.westerberg
2023-06-15 10:50 ` Andy Shevchenko
2023-06-15 11:08 ` Jadav, Raag
2023-06-15 11:17 ` Andy Shevchenko
2023-06-13 8:50 ` [PATCH v3 3/3] pinctrl: intel: simplify exit path of ->gpio_request_enable() hook Raag Jadav
2023-06-13 15:38 ` Andy Shevchenko
2023-06-19 13:53 ` Andy Shevchenko
2023-06-14 5:14 ` [PATCH v3 0/3] Minor improvements for Intel pinctrl Mika Westerberg
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=20230613085054.10976-1-raag.jadav@intel.com \
--to=raag.jadav@intel.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mallikarjunappa.sangannavar@intel.com \
--cc=mika.westerberg@linux.intel.com \
--cc=pandith.n@intel.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®