[meta-xilinx] Zynq TTC usage by Linux

[Jiaying Liang]

HI Edward,

> -----Original Message-----
> From: meta-xilinx-bounces at yoctoproject.org [mailto:meta-xilinx-
> bounces at yoctoproject.org] On Behalf Of Edward Wingate
> Sent: Friday, October 21, 2016 12:42 PM
> To: Nathan Rossi
> Cc: meta-xilinx at yoctoproject.org
> Subject: Re: [meta-xilinx] Zynq TTC usage by Linux
>
> On Fri, Oct 21, 2016 at 12:26 AM, Nathan Rossi <nathan at nathanrossi.com>
> wrote:
> > This is informing that the ttc device is probed and setup as a
> > clocksource device. Althought it is probably not used.
> > You can also check to see what is currently in use: cat
> > /sys/devices/system/clocksource/clocksource0/current_clocksource
>
> Fortunately, my kernel is using the arm global timer.
>
> > I could be mistaken but remoteproc should be able to unregister the
> > clocksource from the kernel and provide it to the remoteproc
> > application?
>
> Is this capability built in already? Are there parameters I need to somehow
> specify during modprobe?  Or do I need to modify zynq_remoteproc driver?
> I couldn't find any documentation about this.
[Wendy] you will need to modify zynq_remoteproc driver to deregister it.

>
> > If not invalidating it in the linux kernel device tree should be fine.
[Wendy] If it is working for you, this is easier.

Best Regards,
Wendy

>
> Yep, it's working with this.  Thanks!
> --
> _______________________________________________
> meta-xilinx mailing list
> meta-xilinx at yoctoproject.org
> https://lists.yoctoproject.org/listinfo/meta-xilinx


This email and any attachments are intended for the sole use of the named recipient(s) and contain(s) confidential information that may be proprietary, privileged or copyrighted under applicable law. If you are not the intended recipient, do not read, copy, or forward this email message or any attachments. Delete this email message and any attachments immediately.