Messages in this thread | | | Subject | Re: [PATCH v6 1/4] clk: zynqmp: Use firmware specific common clock flags | From | Stephen Boyd <> | Date | Mon, 28 Jun 2021 23:10:21 -0700 |
| |
Quoting Rajan Vaja (2021-06-28 00:01:19) > diff --git a/drivers/clk/zynqmp/clk-zynqmp.h b/drivers/clk/zynqmp/clk-zynqmp.h > index 5beeb41b29fa..aa013a59c7cc 100644 > --- a/drivers/clk/zynqmp/clk-zynqmp.h > +++ b/drivers/clk/zynqmp/clk-zynqmp.h > @@ -10,6 +10,20 @@ > > #include <linux/firmware/xlnx-zynqmp.h> > > +/* Common Flags */ > +/* must be gated across rate change */ > +#define ZYNQMP_CLK_SET_RATE_GATE BIT(0) > +/* must be gated across re-parent */ > +#define ZYNQMP_CLK_SET_PARENT_GATE BIT(1) > +/* propagate rate change up one level */ > +#define ZYNQMP_CLK_SET_RATE_PARENT BIT(2) > +/* do not gate even if unused */ > +#define ZYNQMP_CLK_IGNORE_UNUSED BIT(3) > +/* don't re-parent on rate change */ > +#define ZYNQMP_CLK_SET_RATE_NO_REPARENT BIT(7) > +/* do not gate, ever */ > +#define ZYNQMP_CLK_IS_CRITICAL BIT(11)
Ok I was hoping the firmware didn't use the CRITICAL and IGNORE_UNUSED flags but I guess we've lost that battle.
| |