On 2017-01-25 04:50, Danielle Costantino wrote: > On Mon, Jan 23, 2017 at 1:02 AM, Phil Reid <preid@xxxxxxxxxxxxxxxxx> wrote: >> >> On 20/01/2017 06:56, Peter Rosin wrote: >>> >>> On 2017-01-19 08:48, Phil Reid wrote: >>>> >>>> On 18/01/2017 20:19, Peter Rosin wrote: >>>>> >>>>> On 2017-01-17 09:00, Phil Reid wrote: >> >> >> [snip] >> >> >>>>> Hmm, this whole thing is fiddly and while it solves your problem it doesn't >>>>> allow for solving the more general problem when there are "problematic" >>>>> devices mixed with other devices. At least, I don't see it. And the >>>>> limitations we are walking into with tracking number of enables etc suggests >>>>> that we are attacking this at the wrong level. Maybe you should try to work >>>>> around the hw limitations not in the pca954x driver, but in the irq core? >>>> >>>> >>>> I'm looking at the option of getting the hardware changed to not route >>>> the irq for my chips thru the i2c mux. Fortunately the hardware is going thru a >>>> revision for some other changes. Messing with the irq core sounds dangerous >>>> with my level of knowledge. >>> >>> >>> Yeah, but I bet you'd get some attention from people with more irq >>> experience. That can't be bad :-) >>> >>>> The other way I think I can tackle it after reading the datasheet for the ltc1760 is that >>>> it'll deassert it's irq (smbalert) line when the host sends a ARA request on the bus segment. >>>> There's a driver in the kernel for this already, but it's not DT enable and doesn't >>>> handle multiple bus segments. I'll have a look at that as well. >>>> Pretty sure it would need the mux to become an irq parent as per patch 1-3 of this series. >>>> This would be so the system can figure out which segment to do the poll on. >>> >>> >>> Yeah sounds neater. It has the slight drawback that it may not work >>> for pure i2c buses since it an SMB thing?? > > If you need to send SMBus commands like ARA, you should be using an > SMBus 2.0+ compatible bus multiplexer. muxes like the pca954x do not > automatically select the bus segment that the ARA is destined for. It > usually is more efficient to only request the data you need from each > device, rather than checking every segment on each interrupt for the We are not talking about checking every segment on every interrupt, we are talking about checking the segments indicated by the INTx bits in the control register. > cause, one could implement a delayed worker to schedule > checking+clearing the interrupt at a time when the bus is selected for > use by another slave device on that segment when possible. This will > reduce the number of bus setup operations per transfer to slaves on > deeper busses, reducing your i2c latency. i2c traffic scheduling does not exist in linux to the best of my knowledge, it's all handled with a simple mutex AFAIK. So, while traffic scheduling is an interesting problem, I think it is out of scope at this time. If you happen to have a pca954x mux (with irq support) and happen to have devices behind it that needs ARA support, I just don't see how any of the above is relevant. Yes, it could be more efficient to have the hardware done differently, but that is in many cases not a possibility. You have to make do with what you have, and if that costs latency, then there is little to do about that. You only have to make the new stuff optional so that old working setups don't suffer. >>> >>> BTW, why do you need special treatment for multiple segments? Will it not >>> simply have an ARA appear on whatever i2c bus the device sits on? And if >>> something requests to send an ARA message on a bus that happens to be a >>> muxed segment, my mental picture is that the mux will be operated as usual >>> so that the ARA appears on the muxed segment. Maybe I'm missing something? >> >> >> My think was the following. >> When the SMBALERT is asserted a ARA needs to be sent by the master. >> If the device sending the SMBALERT is behind a mux when need to know which segment of the bus to enable. >> Using shared interrupts should work I think, but you have to iterate thru each bus segment. >> If the alert device is nested behind a couple of muxes this could get expensive. >> But yeah otherwise I think the correct mux segment will get enabled automatically. >> The current SMBALERT driver only seems to attached to the root i2c adapter. > > Using ARA in a multi mux environment is very expensive, setting up > each mux segment and then sending ARA will consume more time than it > would take if the mux structure was optimized to service devices on > similar busses, reducing the setup operation count. ARA was only > implemented on the root bus due to the design of the arbiter and mux > cannot guarantee that you are the only owner of the bus when you are > disconnected. ARA handling should take the irq register of the pca95x into account and only send ARAs to indicated mux segments. If more than one segment needs servicing, then of course one ARA for each segment needs to be sent. If someone builds hardware like this and then expect no latency, that someone will hopefully at least learn something. I do not know how this fits with the existing ARA handling (it probably doesn't), but what needs to happen is fairly easy to picture. > You would also need to handle the cases where segments > lock up and must be released using the bus reset mechanism, this > resets the IRQs as well. The added cost of a I2C read to coincide the > write operation to the mux when the irq pin is asserted is > unacceptable for low latency applications. I bet there are a lot of corner cases, and yes, this added cost has to be optional. Perhaps with each mux child segment opting in for ARA support? If a mux then has a way to determine that an ARA isn't needed for some of its child segments (by reading some status register), then linux is free to not send ARAs there. And more importantly, if no mux child segment opts in for ARA support, it should be possible to preserve current behavior... Cheers, peda -- To unsubscribe from this list: send the line "unsubscribe devicetree" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
