From: Michael Krufky <mkrufky-dJidKbW2IEtAfugRpC6u6w@public.gmane.org>
To: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
Cc: David Miller <davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>,
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
Subject: Re: [PATCH 2/6]: i2c-pcf: Add adapter hooks around xfer begin and end.
Date: Wed, 15 Oct 2008 17:37:41 -0400 [thread overview]
Message-ID: <48F662A5.4050303@linuxtv.org> (raw)
In-Reply-To: <20081015141914.7d6c3dd5-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
Jean Delvare wrote:
> Hi David,
>
> On Thu, 21 Aug 2008 02:43:22 -0700 (PDT), David Miller wrote:
>
>> i2c-pcf: Add adapter hooks around xfer begin and end.
>>
>> Some I2C bus implementations need to synchronize with external
>> entities, such as system firmware, which might also be programming the
>> same I2C bus.
>>
>> In order to facilitate this add ->xfer_begin() and ->xfer_end() hooks
>> which are invoked around pcf_xfer().
>>
>
> I get the idea, but I'm not sure about the implementation. I had a
> request several months ago for something similar for the i2c-algo-bit
> driver. I don't think we want to duplicate this mechanism in every
> i2c-algo driver, so it would probably make sense to implement it
> at the i2c-core level?
>
> Michael, do you still need this for i2c-algo-bit? We did not discuss
> this again recently, so I admit I don't know what is the status of this
> request.
Jean,
Yes, the problem still exists, and I still need a way to lock the i2c
adapter during certain volitile operations at driver start-up.
Right now I have an artificial delay in place as a workaround, but
that's only because there currently is no other choice.
Basically, I have a single piece of silicon that is capable of bringing
down the entire i2c bus if somebody attempts to communicate with any
other IC during initialization of this silicon.
Regards,
Mike
_______________________________________________
i2c mailing list
i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org
http://lists.lm-sensors.org/mailman/listinfo/i2c
next prev parent reply other threads:[~2008-10-15 21:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-08-21 9:43 [PATCH 2/6]: i2c-pcf: Add adapter hooks around xfer begin and end David Miller
[not found] ` <20080821.024322.35962617.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-10-15 12:19 ` Jean Delvare
[not found] ` <20081015141914.7d6c3dd5-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-10-15 21:32 ` David Miller
[not found] ` <20081015.143212.196108134.davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org>
2008-10-16 12:57 ` Jean Delvare
[not found] ` <20081016145741.1d94f482-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-10-17 11:43 ` Jean Delvare
2008-10-15 21:37 ` Michael Krufky [this message]
[not found] ` <48F662A5.4050303-dJidKbW2IEtAfugRpC6u6w@public.gmane.org>
2008-10-16 16:17 ` Jean Delvare
[not found] ` <20081016181707.4878bf31-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2008-10-16 18:32 ` Michael Krufky
[not found] ` <48F788C0.10300-dJidKbW2IEtAfugRpC6u6w@public.gmane.org>
2008-10-17 11:16 ` Jean Delvare
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=48F662A5.4050303@linuxtv.org \
--to=mkrufky-djidkbw2ietafugrpc6u6w@public.gmane.org \
--cc=davem-fT/PcQaiUtIeIZ0/mPfg9Q@public.gmane.org \
--cc=i2c-GZX6beZjE8VD60Wz+7aTrA@public.gmane.org \
--cc=khali-PUYAD+kWke1g9hUCZPvPmw@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