From: Wolfram Sang <wsa+renesas@sang-engineering.com>
To: linux-i2c@vger.kernel.org,
Benjamin Tissoires <benjamin.tissoires@redhat.com>
Cc: linux-renesas-soc@vger.kernel.org, Alain Volmat <alain.volmat@st.com>
Subject: Re: [PATCH] i2c: core: do not use logical device when creating irq domain
Date: Fri, 24 Jul 2020 21:47:19 +0200 [thread overview]
Message-ID: <20200724194719.GF1227@ninjato> (raw)
In-Reply-To: <20200701082318.11174-1-wsa+renesas@sang-engineering.com>
[-- Attachment #1: Type: text/plain, Size: 1205 bytes --]
On Wed, Jul 01, 2020 at 10:23:18AM +0200, Wolfram Sang wrote:
> Let's rather use its physical parent device to give proper namings and
> connections in debugfs.
>
> Signed-off-by: Wolfram Sang <wsa+renesas@sang-engineering.com>
> ---
>
> This turns the name from "unknown-1" to ":soc:i2c@e6540000" in debugfs
> for my use case.
>
> @Benjamin: I am not aware of any other side effects or regression
> possibilites. Do you see any?
Last call for opinions before I apply it ;)
>
> drivers/i2c/i2c-core-base.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/i2c/i2c-core-base.c b/drivers/i2c/i2c-core-base.c
> index dc43242a85ba..69217d2193da 100644
> --- a/drivers/i2c/i2c-core-base.c
> +++ b/drivers/i2c/i2c-core-base.c
> @@ -1227,7 +1227,7 @@ static int i2c_setup_host_notify_irq_domain(struct i2c_adapter *adap)
> if (!i2c_check_functionality(adap, I2C_FUNC_SMBUS_HOST_NOTIFY))
> return 0;
>
> - domain = irq_domain_create_linear(adap->dev.fwnode,
> + domain = irq_domain_create_linear(adap->dev.parent->fwnode,
> I2C_ADDR_7BITS_COUNT,
> &i2c_host_notify_irq_ops, adap);
> if (!domain)
> --
> 2.20.1
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-07-24 19:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-01 8:23 [PATCH] i2c: core: do not use logical device when creating irq domain Wolfram Sang
2020-07-24 19:47 ` Wolfram Sang [this message]
2020-07-27 10:04 ` Benjamin Tissoires
2020-07-27 20:32 ` Wolfram Sang
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=20200724194719.GF1227@ninjato \
--to=wsa+renesas@sang-engineering.com \
--cc=alain.volmat@st.com \
--cc=benjamin.tissoires@redhat.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-renesas-soc@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 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 NNTP newsgroup(s).