From: Hanna Hawa <hhhawa@amazon.com>
To: <andriy.shevchenko@linux.intel.com>, <wsa@kernel.org>,
<linus.walleij@linaro.org>, <linux-i2c@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-gpio@vger.kernel.org>
Cc: <dwmw@amazon.co.uk>, <benh@amazon.com>, <ronenk@amazon.com>,
<talel@amazon.com>, <jonnyc@amazon.com>, <hanochu@amazon.com>,
<farbere@amazon.com>, <itamark@amazon.com>, <hhhawa@amazon.com>,
"kernel test robot" <lkp@intel.com>
Subject: [PATCH v5 0/2] i2c: Set i2c pinctrl recovery info from it's device pinctrl
Date: Wed, 28 Dec 2022 16:48:11 +0000 [thread overview]
Message-ID: <20221228164813.67964-1-hhhawa@amazon.com> (raw)
This series include two changes:
1. Adding new API to get the device pinctrl information when it's
initialized before device probed.
2. Make the i2c init recovery to get the device pins if it's not
initialized by the driver from the device pins.
Change Log v4->v5:
- Fix include misplaced
- Update variable set order to reduce one line
- Add Reviewed-by: Andy Shevchenko
Change Log v3->v4:
- Split the change into 2 commits
- Add cover letter and remove change log from commit message
- Fix compilation failure when CONFIG_PINCTRL is not defined
Reported-by: kernel test robot <lkp@intel.com>
Change Log v2->v3:
- Add API to get the device pinctrl
- Make the i2c init recovery to get the device pins
Change Log v1->v2:
- set the rinfo->pinctrl to dev->pins->p instead calling
devm_pinctrl_get()
Hanna Hawa (2):
pinctrl: Add an API to get the pinctrl pins if initialized
i2c: Set i2c pinctrl recovery info from it's device pinctrl
drivers/i2c/i2c-core-base.c | 5 ++++-
include/linux/pinctrl/devinfo.h | 15 +++++++++++++++
2 files changed, 19 insertions(+), 1 deletion(-)
--
2.38.1
next reply other threads:[~2022-12-28 16:54 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 16:48 Hanna Hawa [this message]
2022-12-28 16:48 ` [PATCH v5 1/2] pinctrl: Add an API to get the pinctrl pins if initialized Hanna Hawa
2022-12-29 0:25 ` Linus Walleij
2023-01-20 8:52 ` Wolfram Sang
2022-12-28 16:48 ` [PATCH v5 2/2] i2c: Set i2c pinctrl recovery info from it's device pinctrl Hanna Hawa
2023-01-20 8:53 ` Wolfram Sang
2024-04-11 17:08 ` Robert Marko
2024-04-14 10:34 ` Dan Carpenter
2024-04-14 17:47 ` Robert Marko
2024-04-15 13:43 ` Dan Carpenter
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=20221228164813.67964-1-hhhawa@amazon.com \
--to=hhhawa@amazon.com \
--cc=andriy.shevchenko@linux.intel.com \
--cc=benh@amazon.com \
--cc=dwmw@amazon.co.uk \
--cc=farbere@amazon.com \
--cc=hanochu@amazon.com \
--cc=itamark@amazon.com \
--cc=jonnyc@amazon.com \
--cc=linus.walleij@linaro.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@intel.com \
--cc=ronenk@amazon.com \
--cc=talel@amazon.com \
--cc=wsa@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).