Re: [PATCH v1] mmc: mediatek: Fixed bug where clock frequency could be set wrong

2017-03-03 Thread Yong Mao
> >> > From: Yong Mao <yong@mediatek.com> > >> > To: Daniel Kurtz <djku...@chromium.org> > >> > Subject: Re: [PATCH v1] mmc: mediatek: Fixed bug where clock > >> > frequency > >> > could be set wrong > &g

Re: [PATCH v1] mmc: mediatek: Fixed bug where clock frequency could be set wrong

2017-03-03 Thread Yong Mao
> To: Daniel Kurtz > >> > Subject: Re: [PATCH v1] mmc: mediatek: Fixed bug where clock > >> > frequency > >> > could be set wrong > >> > Date: Fri, 24 Feb 2017 17:33:37 +0800 > >> > > >> > > >&g

Re: [PATCH v1] mmc: mediatek: Fixed bug where clock frequency could be set wrong

2017-03-02 Thread Daniel Kurtz
t; To: Daniel Kurtz <djku...@chromium.org> >> > Subject: Re: [PATCH v1] mmc: mediatek: Fixed bug where clock >> > frequency >> > could be set wrong >> > Date: Fri, 24 Feb 2017 17:33:37 +0800 >> > >> > >> > On Fri, 201

Re: [PATCH v1] mmc: mediatek: Fixed bug where clock frequency could be set wrong

2017-03-02 Thread Daniel Kurtz
On Wed, Mar 1, 2017 at 5:56 PM, Yong Mao wrote: > On Tue, 2017-02-28 at 14:56 +0800, Daniel Kurtz wrote: >> On Fri, Feb 24, 2017 at 5:38 PM, Yong Mao wrote: >> > From: Yong Mao >> > To: Daniel Kurtz >> > Subject: Re: [PATCH v1] mmc: mediatek: F

Re: [PATCH v1] mmc: mediatek: Fixed bug where clock frequency could be set wrong

2017-03-01 Thread Yong Mao
On Tue, 2017-02-28 at 14:56 +0800, Daniel Kurtz wrote: > On Fri, Feb 24, 2017 at 5:38 PM, Yong Mao <yong@mediatek.com> wrote: > > From: Yong Mao <yong@mediatek.com> > > To: Daniel Kurtz <djku...@chromium.org> > > Subject: Re: [PATCH v

Re: [PATCH v1] mmc: mediatek: Fixed bug where clock frequency could be set wrong

2017-03-01 Thread Yong Mao
On Tue, 2017-02-28 at 14:56 +0800, Daniel Kurtz wrote: > On Fri, Feb 24, 2017 at 5:38 PM, Yong Mao wrote: > > From: Yong Mao > > To: Daniel Kurtz > > Subject: Re: [PATCH v1] mmc: mediatek: Fixed bug where clock > > frequency > > could be set wron

Re: [PATCH v1] mmc: mediatek: Fixed bug where clock frequency could be set wrong

2017-02-27 Thread Daniel Kurtz
On Fri, Feb 24, 2017 at 5:38 PM, Yong Mao <yong@mediatek.com> wrote: > From: Yong Mao <yong@mediatek.com> > To: Daniel Kurtz <djku...@chromium.org> > Subject: Re: [PATCH v1] mmc: mediatek: Fixed bug where clock frequency > could be set wrong >

Re: [PATCH v1] mmc: mediatek: Fixed bug where clock frequency could be set wrong

2017-02-27 Thread Daniel Kurtz
On Fri, Feb 24, 2017 at 5:38 PM, Yong Mao wrote: > From: Yong Mao > To: Daniel Kurtz > Subject:Re: [PATCH v1] mmc: mediatek: Fixed bug where clock frequency > could be set wrong > Date: Fri, 24 Feb 2017 17:33:37 +0800 > > > On Fri, 2017-02-24 at 17:52 +

Re: [PATCH v1] mmc: mediatek: Fixed bug where clock frequency could be set wrong

2017-02-24 Thread Yong Mao
From: Yong Mao <yong@mediatek.com> To: Daniel Kurtz <djku...@chromium.org> Subject: Re: [PATCH v1] mmc: mediatek: Fixed bug where clock frequency could be set wrong Date: Fri, 24 Feb 2017 17:33:37 +0800 On Fri, 2017-02-24 at 17:52 +0900, Daniel Kurtz wrote: >

Re: [PATCH v1] mmc: mediatek: Fixed bug where clock frequency could be set wrong

2017-02-24 Thread Yong Mao
From: Yong Mao To: Daniel Kurtz Subject:Re: [PATCH v1] mmc: mediatek: Fixed bug where clock frequency could be set wrong Date: Fri, 24 Feb 2017 17:33:37 +0800 On Fri, 2017-02-24 at 17:52 +0900, Daniel Kurtz wrote: > On Fri, Feb 24, 2017 at 5:22 PM, Yong Mao wrote: > >

Re: [PATCH v1] mmc: mediatek: Fixed bug where clock frequency could be set wrong

2017-02-24 Thread Daniel Kurtz
On Fri, Feb 24, 2017 at 5:22 PM, Yong Mao wrote: > > From: yong mao > > This patch can fix two issues: > > Issue 1: > The maximum value of clock divider is 0xff. > Because the type of div is u32, div may be larger than max_div. > In this case, we

Re: [PATCH v1] mmc: mediatek: Fixed bug where clock frequency could be set wrong

2017-02-24 Thread Daniel Kurtz
On Fri, Feb 24, 2017 at 5:22 PM, Yong Mao wrote: > > From: yong mao > > This patch can fix two issues: > > Issue 1: > The maximum value of clock divider is 0xff. > Because the type of div is u32, div may be larger than max_div. > In this case, we should use max_div to set the clock frequency. >

[PATCH v1] mmc: mediatek: Fixed bug where clock frequency could be set wrong

2017-02-24 Thread Yong Mao
From: yong mao This patch can fix two issues: Issue 1: The maximum value of clock divider is 0xff. Because the type of div is u32, div may be larger than max_div. In this case, we should use max_div to set the clock frequency. Issue 2: In previous code, we can not set

[PATCH v1] mmc: mediatek: Fixed bug where clock frequency could be set wrong

2017-02-24 Thread Yong Mao
From: yong mao This patch can fix two issues: Issue 1: The maximum value of clock divider is 0xff. Because the type of div is u32, div may be larger than max_div. In this case, we should use max_div to set the clock frequency. Issue 2: In previous code, we can not set the correct clock