Re: [PATCH v5 01/10] clk: mediatek: Removed unused dpi_ck clock from MT8173

[James Liao]

Hi Stephen,

Could you help to apply this patch into 4.2?


Best regards,

James

On Wed, 2015-07-29 at 09:05 +0200, Heiko Stübner wrote:
> Am Mittwoch, 29. Juli 2015, 14:52:25 schrieb James Liao:
> > The dpi_ck clock can be removed because it not actually used
> > in topckgen and subsystems.
> > 
> > Signed-off-by: James Liao <jamesjj.liao@xxxxxxxxxxxx>
> 
> From our past discussions this change looks about right, and should still 
> become _part of 4.2_, to not have the CLK_TOP_DPI become part of the 
> devicetree CLK_TOP_DPI.
> 
> Reviewed-by: Heiko Stuebner <heiko@xxxxxxxxx>
> 
> > ---
> >  drivers/clk/mediatek/clk-mt8173.c      | 1 -
> >  include/dt-bindings/clock/mt8173-clk.h | 1 -
> >  2 files changed, 2 deletions(-)
> > 
> > diff --git a/drivers/clk/mediatek/clk-mt8173.c
> > b/drivers/clk/mediatek/clk-mt8173.c index 4b9e04c..4486f8f 100644
> > --- a/drivers/clk/mediatek/clk-mt8173.c
> > +++ b/drivers/clk/mediatek/clk-mt8173.c
> > @@ -26,7 +26,6 @@ static DEFINE_SPINLOCK(mt8173_clk_lock);
> > 
> >  static const struct mtk_fixed_factor root_clk_alias[] __initconst = {
> >  	FACTOR(CLK_TOP_CLKPH_MCK_O, "clkph_mck_o", "clk_null", 1, 1),
> > -	FACTOR(CLK_TOP_DPI, "dpi_ck", "clk_null", 1, 1),
> >  	FACTOR(CLK_TOP_USB_SYSPLL_125M, "usb_syspll_125m", "clk_null", 1, 1),
> >  	FACTOR(CLK_TOP_HDMITX_DIG_CTS, "hdmitx_dig_cts", "clk_null", 1, 1),
> >  };
> > diff --git a/include/dt-bindings/clock/mt8173-clk.h
> > b/include/dt-bindings/clock/mt8173-clk.h index 4ad76ed..7230c38 100644
> > --- a/include/dt-bindings/clock/mt8173-clk.h
> > +++ b/include/dt-bindings/clock/mt8173-clk.h
> > @@ -18,7 +18,6 @@
> >  /* TOPCKGEN */
> > 
> >  #define CLK_TOP_CLKPH_MCK_O		1
> > -#define CLK_TOP_DPI			2
> >  #define CLK_TOP_USB_SYSPLL_125M		3
> >  #define CLK_TOP_HDMITX_DIG_CTS		4
> >  #define CLK_TOP_ARMCA7PLL_754M		5
> 


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/