From: George Cherian <gcherian@caviumnetworks.com>
To: Phil Reid <preid@electromag.com.au>,
Jan Glauber <jglauber@cavium.com>,
George Cherian <george.cherian@cavium.com>
Cc: linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org,
wsa@the-dreams.de, Kamlakant Patel <kamlakant.patel@cavium.com>
Subject: Re: [PATCH 3/3] i2c: xlp9xx: Add support for SMBAlert
Date: Tue, 6 Mar 2018 19:53:22 +0530 [thread overview]
Message-ID: <9885c24d-2212-62ac-f452-f37c51255df7@caviumnetworks.com> (raw)
In-Reply-To: <b78f0a77-403d-a5e5-e274-8c4f08a2cd20@electromag.com.au>
On 03/06/2018 02:48 PM, Phil Reid wrote:
> On 6/03/2018 16:36, Jan Glauber wrote:
>> On Tue, Feb 27, 2018 at 01:26:20PM +0000, George Cherian wrote:
>>> Add support for SMBus alert mechanism to i2c-xlp9xx driver.
>>> The second interrupt is parsed to use for SMBus alert.
>>> The first interrupt is the i2c controller main interrupt.
>>>
>>> Signed-off-by: Kamlakant Patel <kamlakant.patel@cavium.com>
>>> Signed-off-by: George Cherian <george.cherian@cavium.com>
>>> ---
>>> drivers/i2c/busses/i2c-xlp9xx.c | 26 ++++++++++++++++++++++++++
>>> 1 file changed, 26 insertions(+)
>>>
>>> diff --git a/drivers/i2c/busses/i2c-xlp9xx.c
>>> b/drivers/i2c/busses/i2c-xlp9xx.c
>>> index eb8913e..9462eab 100644
>>> --- a/drivers/i2c/busses/i2c-xlp9xx.c
>>> +++ b/drivers/i2c/busses/i2c-xlp9xx.c
>>> @@ -10,6 +10,7 @@
>>> #include <linux/clk.h>
>>> #include <linux/completion.h>
>>> #include <linux/i2c.h>
>>> +#include <linux/i2c-smbus.h>
>>> #include <linux/init.h>
>>> #include <linux/interrupt.h>
>>> #include <linux/io.h>
>>> @@ -84,6 +85,8 @@ struct xlp9xx_i2c_dev {
>>> struct device *dev;
>>> struct i2c_adapter adapter;
>>> struct completion msg_complete;
>>> + struct i2c_smbus_alert_setup alert_data;
>>> + struct i2c_client *ara;
>>> int irq;
>>> bool msg_read;
>>> bool len_recv;
>>> @@ -447,6 +450,21 @@ static int xlp9xx_i2c_get_frequency(struct
>>> platform_device *pdev,
>>> return 0;
>>> }
>>> +static int xlp9xx_i2c_smbus_setup(struct xlp9xx_i2c_dev *priv,
>>> + struct platform_device *pdev)
>>> +{
>>> + if (!priv->alert_data.irq)
>>> + return -EINVAL;
>>> +
>>> + priv->alert_data.alert_edge_triggered = 0;
>>
>> Hi George,
>>
>> I think this is not needed anymore, see:
>> 9b9f2b8bc2ac i2c: i2c-smbus: Use threaded irq for smbalert
>>
>> --Jan
>
> Yes.
>
> And also all of this is not needed if named interrupts.
> - interrupt-names
> "irq", "wakeup" and "smbus_alert" names are recognized by I2C core,
> other names are left to individual drivers.
>
> presence of named irq smbus_alert should result in alert handler being
> created for that bus by the core
>
Thanks for the comments I will send out a v2 for this patch.
>>
>>> +
>>> + priv->ara = i2c_setup_smbus_alert(&priv->adapter,
>>> &priv->alert_data);
>>> + if (!priv->ara)
>>> + return -ENODEV;
>>> +
>>> + return 0;
>>> +}
>>> +
>>> static int xlp9xx_i2c_probe(struct platform_device *pdev)
>>> {
>>> struct xlp9xx_i2c_dev *priv;
>>> @@ -467,6 +485,10 @@ static int xlp9xx_i2c_probe(struct
>>> platform_device *pdev)
>>> dev_err(&pdev->dev, "invalid irq!\n");
>>> return priv->irq;
>>> }
>>> + /* SMBAlert irq */
>>> + priv->alert_data.irq = platform_get_irq(pdev, 1);
>>> + if (priv->alert_data.irq <= 0)
>>> + priv->alert_data.irq = 0;
>>> xlp9xx_i2c_get_frequency(pdev, priv);
>>> xlp9xx_i2c_init(priv);
>>> @@ -493,6 +515,10 @@ static int xlp9xx_i2c_probe(struct
>>> platform_device *pdev)
>>> if (err)
>>> return err;
>>> + err = xlp9xx_i2c_smbus_setup(priv, pdev);
>>> + if (err)
>>> + dev_info(&pdev->dev, "No active SMBus alert %d\n", err);
>>> +
>>> platform_set_drvdata(pdev, priv);
>>> dev_dbg(&pdev->dev, "I2C bus:%d added\n", priv->adapter.nr);
>>> --
>>> 2.1.4
>>
>>
>
>
next prev parent reply other threads:[~2018-03-06 14:23 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-02-27 13:26 [PATCHv2 1/3] i2c: xlp9xx: Check for Bus state before every transfer George Cherian
2018-02-27 13:26 ` [PATCH 2/3] i2c: xlp9xx: Handle NACK on DATA properly George Cherian
2018-02-27 13:26 ` [PATCH 3/3] i2c: xlp9xx: Add support for SMBAlert George Cherian
2018-03-06 8:36 ` Jan Glauber
2018-03-06 9:18 ` Phil Reid
2018-03-06 14:23 ` George Cherian [this message]
2018-03-06 8:48 ` [PATCHv2 1/3] i2c: xlp9xx: Check for Bus state before every transfer Jan Glauber
2018-03-06 15:40 ` 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=9885c24d-2212-62ac-f452-f37c51255df7@caviumnetworks.com \
--to=gcherian@caviumnetworks.com \
--cc=george.cherian@cavium.com \
--cc=jglauber@cavium.com \
--cc=kamlakant.patel@cavium.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=preid@electromag.com.au \
--cc=wsa@the-dreams.de \
/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).