From: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>
To: Valentin Longchamp
<valentin.longchamp-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
Cc: Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Adrian Cox <adrian-nKrwMtk+6Wm9FHfhHBbuYA@public.gmane.org>,
"Boschung,
Rainer" <Rainer.Boschung-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
Subject: Re: [PATCH] I2C: mpc: insert DR read in i2c_fixup()
Date: Tue, 3 Jun 2014 09:11:14 +0200 [thread overview]
Message-ID: <20140603071114.GA2653@katana> (raw)
In-Reply-To: <538D7017.40908-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
[-- Attachment #1: Type: text/plain, Size: 940 bytes --]
> > Have you checked other manuals if this always has been the proposed
> > procedure?
>
> I have just checked the RMs of the Freescale CPUs I am familiar with, and it is
> the same procedure:
> - MPC8360E (PowerQUICC II Pro family): 15.5.7
> - MPC8548E (PowerQUICC III family): 11.5.6
>
> So I think this is the correct procedure for this module according to several RMs.
Thanks.
> >> --- a/drivers/i2c/busses/i2c-mpc.c
> >> +++ b/drivers/i2c/busses/i2c-mpc.c
> >> @@ -107,6 +107,7 @@ static irqreturn_t mpc_i2c_isr(int irq, void *dev_id)
> >> static void mpc_i2c_fixup(struct mpc_i2c *i2c)
> >> {
> >> int k;
> >> + u8 dr;
> >
> > Looks like we can drop this variable since the value read is not used?
>
> That's correct it is not used. I have added it to make sure that this is not
> "optimized" out but I guess the readb call is enough for this purpose ?
I'd think so, but it needs your test :)
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2014-06-03 7:11 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-16 13:36 [PATCH] I2C: mpc: insert DR read in i2c_fixup() Valentin Longchamp
[not found] ` <1400247398-23778-1-git-send-email-valentin.longchamp-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
2014-06-02 16:27 ` Wolfram Sang
2014-06-03 6:49 ` Valentin Longchamp
[not found] ` <538D7017.40908-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org>
2014-06-03 7:11 ` Wolfram Sang [this message]
2014-06-03 8:45 ` Valentin Longchamp
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=20140603071114.GA2653@katana \
--to=wsa-z923lk4zbo2bacvfa/9k2g@public.gmane.org \
--cc=Rainer.Boschung-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.org \
--cc=adrian-nKrwMtk+6Wm9FHfhHBbuYA@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=valentin.longchamp-SkAbAL50j+5BDgjK7y7TUQ@public.gmane.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