> -----Original Message----- > From: Kevin Hilman [mailto:[email protected]] > Sent: Tuesday, August 10, 2010 4:36 AM > To: Varadarajan, Charulatha > Cc: [email protected]; [email protected]; Cousson, Benoit; Nayak, > Rajendra; Basak, Partha > Subject: Re: [PATCH 10/13 v5] OMAP: GPIO: Implement GPIO as a platform > device > > Charulatha V <[email protected]> writes: > > > @@ -650,21 +511,28 @@ static void _set_gpio_debounce(struct gpio_bank > *bank, unsigned gpio, > > __raw_writel(debounce, reg); > > > > reg = bank->base; > > - if (cpu_is_omap44xx()) > > + if (bank->method == METHOD_GPIO_44XX) > > reg += OMAP4_GPIO_DEBOUNCENABLE; > > else > > reg += OMAP24XX_GPIO_DEBOUNCE_EN; > > > > val = __raw_readl(reg); > > > > + if (!bank->dbck) { > > + struct platform_device *pdev = to_platform_device(bank->dev); > > + struct omap_device *odev = to_omap_device(pdev); > > insert empty line > > > + if (odev->hwmods[0]->opt_clks->_clk) > > + bank->dbck = odev->hwmods[0]->opt_clks->_clk;
This is not correct always as opt_clks points to an array of optional clocks which can have more than one element. The correct approach would be to scan through the list of optional clocks and pick up the one with role === "dbclk". > > As was discussed in Bangalore, drivers should have no knowledge of hwmod > internals. > > Instead, please propose an API to hwmod for getting the optional > clock(s), or possibly cleaner, an API to directly enable/disable > optional clocks for an omap_device. As per our discussion with Paul & you during workshop, I believe, optional clock control should be done using clock APIs. So, I would go by your suggestion 1 of exposing an API to expose the optional clocks in the hwmod, something like: struct omap_hwmod_opt_clk * omap_hwmod_get_opt_clks(struct omap_hwmod *oh); If agreed, Charu will send updated patch. > > Kevin > > > + if (IS_ERR(bank->dbck)) > > + dev_err(bank->dev, "Could not get gpio dbck\n"); > > + } > > + -- 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
