Re: [PATCH 2/2] soc: qcom: geni: geni_se_clk_freq_match() should always accept multiples

2018-09-06 Thread Doug Anderson
Hi, On Wed, Sep 5, 2018 at 5:20 PM, Matthias Kaehlcke wrote: > On Thu, Aug 30, 2018 at 11:36:12AM -0700, Douglas Anderson wrote: >> The geni_se_clk_freq_match() has some strange semantics. Specifically >> it is defined with two modes: >> 1. It can find a clock that's an exact multiple of the req

Re: [PATCH 2/2] soc: qcom: geni: geni_se_clk_freq_match() should always accept multiples

2018-09-05 Thread Matthias Kaehlcke
On Thu, Aug 30, 2018 at 11:36:12AM -0700, Douglas Anderson wrote: > The geni_se_clk_freq_match() has some strange semantics. Specifically > it is defined with two modes: > 1. It can find a clock that's an exact multiple of the requested rate > 2. If can find a non-exact match but it can't handle m

[PATCH 2/2] soc: qcom: geni: geni_se_clk_freq_match() should always accept multiples

2018-08-30 Thread Douglas Anderson
The geni_se_clk_freq_match() has some strange semantics. Specifically it is defined with two modes: 1. It can find a clock that's an exact multiple of the requested rate 2. If can find a non-exact match but it can't handle multiples then ...but callers should always be able to handle a clock that