"Basak, Partha" <[email protected]> writes: [...]
>> > /* TODO: Analyze removing gpio_bank_count usage from driver code */ >> > @@ -1045,6 +1044,9 @@ static int omap_gpio_request(struct >> gpio_chip *chip, unsigned offset) >> > struct gpio_bank *bank = container_of(chip, struct >> gpio_bank, chip); >> > unsigned long flags; >> > >> > + if (!bank->mod_usage) >> > + pm_runtime_get_sync(bank->dev); >> > + >> >> Would be fine to skip the 'if' here and let runtime PM continue the >> usecounting. Since we'll have trace tools that instrument runtime PM, >> it will be nice to be able to trace all the users instead of just the >> first one to request a GPIO in a given bank. >> > We are continuing to use mod_usage checks for the following reasons: > > 1. In the absence of mod_usage, > pm_runtime_getsync() would be called in the omap_gpio_request()once per > pin for each bank. However, a matching pm_runtime_putsync() would be > called in the CPU_Idle path only once for a given bank. This would lead to > atomic_dec_and_test(&dev->power.usage_count) to return false and > the put_sync will not be effective. OK, per-bank is most important. > 2. Consider a case that a bank is not requested at all but in the CPU_Idle > path we > go-ahead and call pm_runtime_putsync() for that bank. Since usage_count is > already zero, this call makes it negative. Now, a subsequent call to > get_sync() will increment it to 0 and enable the clocks. > This leads to an error-scenario where clocks are enabled with usage_cnt = 0. OK > 3. Ideally we should not be even attempting to fiddle with the > un-requested GPIO banks in the CPU_Idle path. Agreed. Sounds like the right path. Kevin -- To unsubscribe from this list: send the line "unsubscribe linux-omap" in the body of a message to [email protected] More majordomo info at http://vger.kernel.org/majordomo-info.html
