From: Biwen Li <biwen.li@nxp.com>
To: Peter Rosin <peda@axentia.se>, Leo Li <leoyang.li@nxp.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"mark.rutland@arm.com" <mark.rutland@arm.com>
Cc: "linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: RE: [EXT] Re: [PATCH 2/2] i2c: mux: pca954x: replace property i2c-mux-idle-disconnect
Date: Tue, 15 Oct 2019 03:17:50 +0000 [thread overview]
Message-ID: <DB7PR04MB44906BE3732F777C4DBB67538F930@DB7PR04MB4490.eurprd04.prod.outlook.com> (raw)
In-Reply-To: <f3d1e68e-dfb0-b820-7797-1f0d95fa72dd@axentia.se>
>
> Caution: EXT Email
>
> On 2019-10-14 13:25, Biwen Li wrote:
> > This replaces property i2c-mux-idle-disconnect with idle-state
> >
> > Signed-off-by: Biwen Li <biwen.li@nxp.com>
> > ---
> > drivers/i2c/muxes/i2c-mux-pca954x.c | 44
> > ++++++++++++++++++++---------
> > 1 file changed, 31 insertions(+), 13 deletions(-)
> >
> > diff --git a/drivers/i2c/muxes/i2c-mux-pca954x.c
> > b/drivers/i2c/muxes/i2c-mux-pca954x.c
> > index 923aa3a5a3dc..a330929c4d67 100644
> > --- a/drivers/i2c/muxes/i2c-mux-pca954x.c
> > +++ b/drivers/i2c/muxes/i2c-mux-pca954x.c
> > @@ -86,7 +86,7 @@ struct pca954x {
> >
> > u8 last_chan; /* last register value */
> > /* MUX_IDLE_AS_IS, MUX_IDLE_DISCONNECT or >= 0 for channel */
> > - s8 idle_state;
> > + s32 idle_state;
> >
> > struct i2c_client *client;
> >
> > @@ -256,7 +256,7 @@ static int pca954x_deselect_mux(struct
> > i2c_mux_core *muxc, u32 chan) {
> > struct pca954x *data = i2c_mux_priv(muxc);
> > struct i2c_client *client = data->client;
> > - s8 idle_state;
> > + s32 idle_state;
> >
> > idle_state = READ_ONCE(data->idle_state);
> > if (idle_state >= 0)
> > @@ -411,7 +411,6 @@ static int pca954x_probe(struct i2c_client *client,
> > struct i2c_adapter *adap = client->adapter;
> > struct device *dev = &client->dev;
> > struct device_node *np = dev->of_node;
> > - bool idle_disconnect_dt;
> > struct gpio_desc *gpio;
> > struct i2c_mux_core *muxc;
> > struct pca954x *data;
> > @@ -462,22 +461,31 @@ static int pca954x_probe(struct i2c_client
> *client,
> > }
> > }
> >
> > + if (of_property_read_u32(np, "idle-state", &data->idle_state))
> > + data->idle_state = MUX_IDLE_AS_IS;
> > +
> > /* Write the mux register at addr to verify
> > * that the mux is in fact present. This also
> > * initializes the mux to disconnected state.
> > */
> > - if (i2c_smbus_write_byte(client, 0) < 0) {
> > + if (data->idle_state >= 0){
>
> Space before {
Okay, got it, I will add it in v2.
>
> > + data->last_chan = data->idle_state;
>
> data->last_chan should have the actual register value, i.e. (untested)
Okay, got it, I will adjust it in v2.
>
> if (data->chip->muxtype == pca954x_ismux)
> data->last_chan = data->idle_state |
> data->chip->enable;
> else
> data->last_chan = 1 << data->idle_state;
>
> ret = i2c_smbus_write_byte(client, data->last_chan);
>
> But since this regval calculation is now needed in three places, it should be
> moved to a helper function.
You are right, I will add a helper function in v2.
>
> > + /* Always enable multiplexer */
> > + ret = i2c_smbus_write_byte(client, data->last_chan |
> > + (data->chip->muxtype ==
> pca954x_ismux ?
> > + data->chip->enable : 0));
> > + }
> > + else{
>
> Space before {
Got it, I will add it in v2.
>
> Naturally, you have the exact same issues in the pca954x_resume hunk,
> below.
Got it
>
> > + data->last_chan = 0; /* force the first
> selection */
> > + /* Disconnect multiplexer */
> > + ret = i2c_smbus_write_byte(client, data->last_chan);
> > + }
> > +
> > + if (ret < 0) {
> > dev_warn(dev, "probe failed\n");
> > return -ENODEV;
> > }
> >
> > - data->last_chan = 0; /* force the first selection */
> > - data->idle_state = MUX_IDLE_AS_IS;
> > -
> > - idle_disconnect_dt = np &&
> > - of_property_read_bool(np, "i2c-mux-idle-disconnect");
> > - if (idle_disconnect_dt)
> > - data->idle_state = MUX_IDLE_DISCONNECT;
>
> In case the idle-state property is missing, you need to fall back to the old
> behavior and handle i2c-mux-idle-disconnect as before.
Okay, got it, I will add it in v2.
>
> Cheers,
> Peter
>
> >
> > ret = pca954x_irq_setup(muxc);
> > if (ret)
> > @@ -531,8 +539,18 @@ static int pca954x_resume(struct device *dev)
> > struct i2c_mux_core *muxc = i2c_get_clientdata(client);
> > struct pca954x *data = i2c_mux_priv(muxc);
> >
> > - data->last_chan = 0;
> > - return i2c_smbus_write_byte(client, 0);
> > + if (data->idle_state >= 0){
> > + data->last_chan = data->idle_state;
> > + /* Always enable multiplexer */
> > + return i2c_smbus_write_byte(client, data->last_chan |
> > + (data->chip->muxtype ==
> pca954x_ismux ?
> > + data->chip->enable : 0));
> > + }
> > + else{
> > + data->last_chan = 0;
> > + /* Disconnect multiplexer */
> > + return i2c_smbus_write_byte(client, data->last_chan);
> > + }
> > }
> > #endif
> >
> >
next prev parent reply other threads:[~2019-10-15 3:17 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-14 11:25 [PATCH 1/2] dt-bindings: i2c: " Biwen Li
2019-10-14 11:25 ` [PATCH 2/2] i2c: mux: pca954x: " Biwen Li
2019-10-14 16:03 ` Peter Rosin
2019-10-15 3:17 ` Biwen Li [this message]
2019-10-14 11:41 ` [PATCH 1/2] dt-bindings: i2c: " Biwen Li
2019-10-14 15:44 ` Peter Rosin
2019-10-15 3:18 ` [EXT] " Biwen Li
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=DB7PR04MB44906BE3732F777C4DBB67538F930@DB7PR04MB4490.eurprd04.prod.outlook.com \
--to=biwen.li@nxp.com \
--cc=devicetree@vger.kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=peda@axentia.se \
--cc=robh+dt@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
all inboxes | Powered by JetHome®