On Mon, 28 Dec 2020 15:31:17 -0600, Adam Ford wrote:
> The AVB driver assumes there is an external clock, but it could
> be driven by an external clock. In order to enable a programmable
> clock, it needs to be added to the clocks list and enabled in the
> driver. Since there currently only one c
Hi Adam,
On Fri, Jan 8, 2021 at 3:11 PM Geert Uytterhoeven wrote:
> On Mon, Dec 28, 2020 at 10:32 PM Adam Ford wrote:
> > The AVB driver assumes there is an external clock, but it could
> > be driven by an external clock. In order to enable a programmable
> > clock, it needs to be added to the
On Mon, Dec 28, 2020 at 10:32 PM Adam Ford wrote:
> The AVB driver assumes there is an external clock, but it could
> be driven by an external clock. In order to enable a programmable
> clock, it needs to be added to the clocks list and enabled in the
> driver. Since there currently only one clo
Hello!
On 29.12.2020 0:31, Adam Ford wrote:
The AVB driver assumes there is an external clock, but it could
be driven by an external clock.
Driver can be driven by external clock? :-)
In order to enable a programmable
clock, it needs to be added to the clocks list and enabled in the
dri
The AVB driver assumes there is an external clock, but it could
be driven by an external clock. In order to enable a programmable
clock, it needs to be added to the clocks list and enabled in the
driver. Since there currently only one clock, there is no
clock-names list either.
Update bindings t
