On Wed, Jan 28, 2015 at 04:20:25PM +0200, Heikki Krogerus wrote: > Hi, > > > > > Can you share how tusb1210 is connected on the platform you're using as > > > > test for this patch? I don't think this driver would work reliably with > > > > this device: > > > > http://liliputing.com/2014/11/trekstor-launches-first-android-tablet-based-intels-irda-reference-design.html > > > > > > The only reason why that board doesn't work is because of very much > > > Baytrail-CR specific problems. These are are two issues, but the first > > > > That's not BYT-CR specific problems. That's just dwc3 and tusb1210 > > interacting as they're expecting to. > > > > > one is critical for getting it working. Both will be handled, but > > > separately from this set: > > > > > > 1) The firmware leaves the PHY in reset, forcing us to enable it > > > somehow in OS before accessing ulpi. Unless we can get a firmware fix > > > for that (it's starting to look like it's not going to happen; please > > > correct me if you know something else!), we need to add a quirk for > > > Baytrails (attached), which is probable still OK. But IMO this really > > > should be fixed in the firmware. > > > > It seems you're expecting the PHY to be fully operational in order to > > probe it. That's wrong assumption. BYT-CR's BIOS is doing nothing wrong > > by leaving PHY on reset state. > > But it is. If we want to use ULPI as a bus like we do, then the PHY > will be no different then devices attached to many other buses. We > have made firmware fixes like that before. All the devices need to be > in a state, operational enough after bootup, so we can probe them in > OS without the need for hacks where they are separately enabled before > it's possible. That makes no sense. Not only dwc3 and phy could live as modules (which means they may probe far away from device's boot time) but we have examples of buses not behaving like you said. E.g. I2C needs master to be probed to have bus working and no BIOS needs to make I2C controller functional in order to probe its controller's driver. > > > The real problem is what I stated above. > > With your current logic, you'll get stuck with checking/egg problem: you > > need phy probed to probe dwc3, but need dwc3 probed to power on phy. > > You need a logic to break this circular dependency. > > The moment we register the ulpi interface with the ulpi bus in > dwc3_probe(), we know dwc3 has it's PHY interface in operational mode > and register access to ULPI PHY is possible. And that is all dwc3 > needs to/can do. > > I don't think you are seeing the whole "ulpi bus" in these patches, > but in any case; Like I said, this problem is purely BYT-CR specific, > which IMO really should be fixed in the firmware. The proposed design has a flaw that breaks products on market simply because they don't have BIOS (unnecessarily) powering on phy. You're labeling that as BYT-CR specific issue because BYT-CR needs to be PM efficient and then it won't power on hw components in moment they don't need to. FW developers won't like this suggestion and I'd have to agree with them. > > > > 2) Since the gpio resources are given to the controller device in ACPI > > > tables and there isn't separate device object for the PHY at all, we > > > need to deliver the gpios somehow separately to the phy driver. There > > > is a thread where we are talking about how to do that: > > > https://lkml.org/lkml/2014/12/18/82 > > > > How about just leave the logic the way it is: > > dwc3-pci.c registers platform_device with gpio as resource if the GPIOs > > are provided to dwc3. If not, then dwc3-pci.c will expect phy to have > > its own ACPI id. > > I think you are now talking about the platform devices for the legacy > USB PHY framework created in dwc3-pci.c, which btw. were removed. > Please note that we are not using platform bus with the ULPI devices, > and those devices are created by the bus driver and not dwc3. Yes, that the one. Current products' BIOS on market didn't know about new ULPI bus. They rely on platform devices created by pci probe. Your ULPI bus proposal is way better to handle that problem and got my support since they beginning you showed that to me, but it does not justify breaking current working devices. Removing the platform device registration for phy with firmwares that rely on that was a mistake and any ACPI work related to fix that is unnecessary. These legacy ACPI tables gave the phy-related GPIOs to dwc3. Just mark is as legacy situation and let the legacy hw's happy. No vendor will change their BIOS after market due to non-buggy situation. > > I'm pretty sure now that you are not seeing the whole point with this > set, which is to provide new bus type for ULPI. If so, then could you > please review the whole series. I'll review the whole series. But pls note your design requires vendors to change their FW (including but not limited to ACPI table) after market. That won't happen. Br, David > > > Thanks, > > -- > heikki -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
