On 10-11-23, 17:49, David Dai wrote:
> diff --git a/Documentation/devicetree/bindings/cpufreq/qemu,cpufreq-virtual.yaml b/Documentation/devicetree/bindings/cpufreq/qemu,cpufreq-virtual.yaml
> +$id: http://devicetree.org/schemas/cpufreq/qemu,cpufreq-virtual.yaml#
> +properties:
> + compatible:
> + const: qemu,virtual-cpufreq
Not sure why we need to mention QEMU here.. Why limit this to just QEMU ?
--
viresh
On Wed, Nov 15, 2023 at 11:57:41AM +0530, Viresh Kumar wrote:
> On 10-11-23, 17:49, David Dai wrote:
> > diff --git a/Documentation/devicetree/bindings/cpufreq/qemu,cpufreq-virtual.yaml b/Documentation/devicetree/bindings/cpufreq/qemu,cpufreq-virtual.yaml
> > +$id: http://devicetree.org/schemas/cpufreq/qemu,cpufreq-virtual.yaml#
> > +properties:
> > + compatible:
> > + const: qemu,virtual-cpufreq
>
> Not sure why we need to mention QEMU here.. Why limit this to just QEMU ?
Because that is the implementation. And also to discourage anyone from
using this on their hardware or thinking it is generic and the way to
extend it to another implementation is adding properties.
Rob