Le 20/06/2016 10:52, Alexandre Belloni a écrit : > On 20/06/2016 at 08:46:02 +0000, Yang, Wenyou wrote : >> Hi Alexandre & Nicolas, >> >>> -----Original Message----- >>> From: Alexandre Belloni [mailto:alexandre.belloni@xxxxxxxxxxxxxxxxxx] >>> Sent: 2016年6月20日 16:04 >>> To: Yang, Wenyou <Wenyou.Yang@xxxxxxxxx> >>> Cc: Rob Herring <robh@xxxxxxxxxx>; Alan Stern <stern@xxxxxxxxxxxxxxxxxxx>; >>> Greg Kroah-Hartman <gregkh@xxxxxxxxxxxxxxxxxxx>; Ferre, Nicolas >>> <Nicolas.FERRE@xxxxxxxxx>; Pawel Moll <pawel.moll@xxxxxxx>; Mark Brown >>> <broonie@xxxxxxxxxx>; Ian Campbell <ijc+devicetree@xxxxxxxxxxxxxx>; Kumar >>> Gala <galak@xxxxxxxxxxxxxx>; linux-kernel@xxxxxxxxxxxxxxx; >>> devicetree@xxxxxxxxxxxxxxx; linux-arm-kernel@xxxxxxxxxxxxxxxxxxx; linux- >>> usb@xxxxxxxxxxxxxxx >>> Subject: Re: [PATCH v3 1/2] usb: ohci-at91: Forcibly suspend ports while USB >>> suspend >>> >>> On 20/06/2016 at 03:16:35 +0000, Yang, Wenyou wrote : >>>>> Sure, what I mean is that you can try to get the regmap for the SFR in every >>> case. >>>>> Depending on whether you were able to get it, you can decide to call >>>>> ohci_at91_port_suspend/resume or not (just test for sfr_regmap != NULL). >>>> >>>> I don't think so. The SFR includes a lot of miscellaneous functions, more than >>> this one. >>>> >>> >>> I know but this is irrelevant to this discussion. If you need to use the SFR from >>> another driver you will simply get it from that other driver. >>> >>> I that case, you will try to get "atmel,sama5d2-sfr". It is only present on sama5d2 >>> so you have enough information to know whether or not you can use it to >>> suspend/resume. >> >> I understand what your meaning :). >> Use "atmel,sama5d2-sfr" compatible to distinguish whether forcibly suspend USB port via SFR or not. >> >> I am not sure if it is a better solution. >> > > It is definitively superior. There is only one lookup in the device tree > instead of two because whatever happens, you will have to get the SFR > regmap and you don't need to add a compatible string for an IP that > didn't change. > >> Nicolas, could you give your opinion? I'll paraphrase Alexandre but this is what I understood: Having the information in one place and not having to managed the synchronization with 2 potential sources of information is clearly an advantage of Alexandre's solution. If the next SoC has the same workaround/feature, we will anyway have a different SFR string to cling to... So it won't change much and we won't have the confusion of having the same sama5d2 compatible string on the OHCI side (same behavior) and different compatible string on the SFR side (probably a new SFR for a new SoC...). If the next SoC doesn't have this workaround/feature... well, it's simple, we don't look for the SFR, we don't use the bits, and we come back to the situation that we've always experienced ; with the same compatibility sting for OHCI as the IP never actually changed... In conclusion: try Alexandre's solution and we'll certainly find that it's actually simpler. Bonus point: it voids the discussion on the OHCI compatible string descriptions! Bye, >>> Alexandre Belloni, Free Electrons >>> Embedded Linux, Kernel and Android engineering http://free-electrons.com >> >> >> Best Regards, >> Wenyou Yang > -- Nicolas Ferre -- 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
