From: Gregory CLEMENT <gregory.clement-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
To: Jean-Jacques Hiblot
<jjhiblot-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] i2c : i2c-ibm-iic : use interrupts to perform the data transfer
Date: Thu, 21 Nov 2013 13:16:02 +0100 [thread overview]
Message-ID: <528DF982.6000803@free-electrons.com> (raw)
In-Reply-To: <528DD837.5060005-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Hi Jean-Jacques,
[...]
>>
>>> + if (ext_status & EXTSTS_LA)
>>> + dev_dbg(dev->dev, "Lost arbitration\n");
>>
>> Ditto
> I don't know if this is really an error. Arbitration loss wan be very
> common in a multi master environement. What about dev_warn ou dev_info
I think dev_warn should be fine but I don't have a strong opinion on it.
>
>>
>>> + if (ext_status & EXTSTS_ICT)
>>> + dev_dbg(dev->dev, "Incomplete transfer\n");
>>
>> Ditto
>>
>>> + if (ext_status & EXTSTS_XFRA)
>>> + dev_dbg(dev->dev, "Transfer aborted\n");
>>
>> Ditto
>>
> I'll use dev_err instead for those two.
>
>
[...]
>> Is it related to the topic of this patch?
> I needed the pointer to the struct device for the dev_err, dev_dbg etc.,
> so I stored it in the private structure. If it's better I can modify the
> driver to get it from adap->dev.parent when needed.
What I have in mind was more to write a separate patch for this kind
of improvement
Thanks,
Gregory
--
Gregory Clement, Free Electrons
Kernel, drivers, real-time and embedded Linux
development, consulting, training and support.
http://free-electrons.com
prev parent reply other threads:[~2013-11-21 12:16 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-20 15:08 [PATCH] i2c : i2c-ibm-iic : use interrupts to perform the data transfer jean-jacques hiblot
[not found] ` <1384960134-24039-1-git-send-email-jean-jacques.hiblot-qU79poH1Kb0@public.gmane.org>
2013-11-20 15:53 ` Gregory CLEMENT
[not found] ` <528CDAEC.3040307-wi1+55ScJUtKEb57/3fJTNBPR1lH4CV8@public.gmane.org>
2013-11-21 9:53 ` Jean-Jacques Hiblot
[not found] ` <528DD837.5060005-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
2013-11-21 10:43 ` Wolfram Sang
2013-11-21 12:16 ` Gregory CLEMENT [this message]
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=528DF982.6000803@free-electrons.com \
--to=gregory.clement-wi1+55scjutkeb57/3fjtnbpr1lh4cv8@public.gmane.org \
--cc=jjhiblot-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.