Hello,
On Wednesday, February 29, 2012 1:26 AM KyongHo Cho wrote:
On Tue, Feb 28, 2012 at 4:20 PM, Kyungmin Park
kyungmin.p...@samsung.com wrote:
Hi,
On 2/28/12, KyongHo Cho pullip@samsung.com wrote:
Handling System MMUs with an identifier is not flexible to manage
System MMU
Hello,
On 02/29/2012 01:25 AM, KyongHo Cho wrote:
static int exynos4_clk_hdmiphy_ctrl(struct clk *clk, int enable)
{
return s5p_gatectrl(S5P_HDMI_PHY_CONTROL, clk, enable);
@@ -679,61 +684,55 @@ static struct clk exynos4_init_clocks_off[] = {
.enable =
On Tue, Feb 28, 2012 at 4:20 PM, Kyungmin Park
kyungmin.p...@samsung.com wrote:
Hi,
On 2/28/12, KyongHo Cho pullip@samsung.com wrote:
Handling System MMUs with an identifier is not flexible to manage
System MMU platform devices because of the following reasons:
1. A device driver which
Handling System MMUs with an identifier is not flexible to manage
System MMU platform devices because of the following reasons:
1. A device driver which needs to handle System MMU must know the ID.
2. A System MMU may not present in some implementations of Exynos family.
3. Handling System MMU
Hi,
On 2/28/12, KyongHo Cho pullip@samsung.com wrote:
Handling System MMUs with an identifier is not flexible to manage
System MMU platform devices because of the following reasons:
1. A device driver which needs to handle System MMU must know the ID.
2. A System MMU may not present in
