On 10/01, Heiko Stübner wrote: > Am Donnerstag, 1. Oktober 2015, 11:54:24 schrieb Ulf Hansson: > > On 30 September 2015 at 16:55, Heiko Stübner <heiko@xxxxxxxxx> wrote: > > > Am Mittwoch, 30. September 2015, 16:42:05 schrieb Ulf Hansson: > > >> On 30 September 2015 at 16:07, Heiko Stuebner <heiko@xxxxxxxxx> wrote: > > > The clock changes of course only touch internals of the phase-clocks, so > > > should have no problem going through another tree. > > > > What happens if I take mmc and dt changes, wouldn't I need the clock > > patches as well? > > The API stays of course the same, only the degree to settings translation gets > optimized, so I guess in the worst case you would get no good phase and thus > fall back to non-highspeed modes - but the system would stay running. > > But of course, if the clock maintainers could Ack the two clock patches and > everything would stay together that would work even better :-) > If Ulf doesn't want to take them we can apply them to clk tree. Otherwise, you can have my acked-by on the clk patches. -- Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project -- To unsubscribe from this list: send the line "unsubscribe linux-mmc" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
