Hi Jaehoon,
On 04/27/2017 12:21 PM, Jaehoon Chung wrote:
> On 04/25/2017 04:52 PM, Philipp Tomsich wrote:
>> The 'clock-freq-min-max' property was deprecated in the upstream
>> (i.e. Linux) DTS bindings in favor of the 'max-frequency' property.
> It's difference wit Linux kernel. "clock-freq-min-
Hi Jaehoon,
On 04/27/2017 12:21 PM, Jaehoon Chung wrote:
On 04/25/2017 04:52 PM, Philipp Tomsich wrote:
The 'clock-freq-min-max' property was deprecated in the upstream
(i.e. Linux) DTS bindings in favor of the 'max-frequency' property.
It's difference wit Linux kernel. "clock-freq-min-max" w
I am aware of this kernel behaviour, but felt that it does not directly apply
for
this specific change, as the original DTS (before the deprecation of this
property)
had defined the minimum frequency for the affected chips as <40>.
For reference, here’s the DTS change that this is tracking:
On 04/25/2017 04:52 PM, Philipp Tomsich wrote:
> The 'clock-freq-min-max' property was deprecated in the upstream
> (i.e. Linux) DTS bindings in favor of the 'max-frequency' property.
It's difference wit Linux kernel. "clock-freq-min-max" was deprecated in Linux.
Linux kernel is supporting to find
The 'clock-freq-min-max' property was deprecated in the upstream
(i.e. Linux) DTS bindings in favor of the 'max-frequency' property.
With the latest RK3399 DTSI does no longer include the deprecated
property and the rockchip_dw_mmc driver requiring it to be present,
the driver doesn't bind to the
5 matches
Mail list logo
