From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-3.6 required=3.0 tests=BAYES_00,DKIM_INVALID, DKIM_SIGNED,HEADER_FROM_DIFFERENT_DOMAINS,MAILING_LIST_MULTI,SPF_HELO_NONE, SPF_PASS autolearn=no autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id D1D92C4338F for ; Fri, 23 Jul 2021 23:28:47 +0000 (UTC) Received: from phobos.denx.de (phobos.denx.de [85.214.62.61]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by mail.kernel.org (Postfix) with ESMTPS id 8FEEB60F23 for ; Fri, 23 Jul 2021 23:28:46 +0000 (UTC) DMARC-Filter: OpenDMARC Filter v1.4.1 mail.kernel.org 8FEEB60F23 Authentication-Results: mail.kernel.org; dmarc=fail (p=quarantine dis=none) header.from=JTi.uk.com Authentication-Results: mail.kernel.org; spf=pass smtp.mailfrom=lists.denx.de Received: from h2850616.stratoserver.net (localhost [IPv6:::1]) by phobos.denx.de (Postfix) with ESMTP id 2E1A382DB1; Sat, 24 Jul 2021 01:28:44 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=fail (p=quarantine dis=none) header.from=JTi.uk.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=u-boot-bounces@lists.denx.de Authentication-Results: phobos.denx.de; dkim=fail reason="signature verification failed" (1024-bit key; unprotected) header.d=jti.uk.com header.i=@jti.uk.com header.b="HyWG0Goz"; dkim-atps=neutral Received: by phobos.denx.de (Postfix, from userid 109) id 3208582D8C; Fri, 23 Jul 2021 14:45:43 +0200 (CEST) Received: from jti.uk.com (jti.uk.com [81.137.207.160]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by phobos.denx.de (Postfix) with ESMTPS id 9ADB882D84 for ; Fri, 23 Jul 2021 14:45:40 +0200 (CEST) Authentication-Results: phobos.denx.de; dmarc=pass (p=quarantine dis=none) header.from=JTi.uk.com Authentication-Results: phobos.denx.de; spf=pass smtp.mailfrom=timh@jti.uk.com Received: from TIMHPZEON (jti.uk.com [81.137.207.160]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by jti.uk.com (Postfix) with ESMTPSA id 4C7C15E1256 for ; Fri, 23 Jul 2021 13:45:31 +0100 (IST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=jti.uk.com; s=jtinnovations; t=1627044331; bh=Z0mEVrutuZolpVZXEUbuJeY8PwKnd3LmxLS+A7TTq88=; h=From:To:Subject:Date; b=HyWG0Gozs3YMabBPE8+xDOqIcyBsBiilnpr0waJfYNtKr0MoDWjci4q7pFpUdaX4q h01GN/qht8Tmn5GNRKpcC6dvL5R0TfhHChLQFCcG+x9pLK0amarAsrs6IBvpmZWZP9 elbFh74ga9KZ/1rvnaFk5prLdNAI4lETLm8fGsvY= From: "Tim" To: Subject: SAMA5D27 - UTMI issue? Date: Fri, 23 Jul 2021 13:45:31 +0100 Message-ID: <0e5501d77fc0$9f4e82d0$ddeb8870$@JTi.uk.com> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Thread-Index: AQKD78fseP7sjXzi8rA5hpG2RNiuYQ== Content-Language: en-gb X-MailScanner-ID: 4C7C15E1256.A21F0 X-MailScanner: Found to be clean X-MailScanner-From: timh@jti.uk.com X-Mailman-Approved-At: Sat, 24 Jul 2021 01:28:42 +0200 X-BeenThere: u-boot@lists.denx.de X-Mailman-Version: 2.1.34 Precedence: list List-Id: U-Boot discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: u-boot-bounces@lists.denx.de Sender: "U-Boot" X-Virus-Scanned: clamav-milter 0.103.2 at phobos.denx.de X-Virus-Status: Clean Hi, I have a custom board using the SAMA5D27 and basically have u-boot running now. The only issue I have is that because it uses a 24MHz crystal (like the SOM EV board) the UTMICKTRIM register needs to be set correctly (not just for USB - the CAN system runs best from the 480MHz UPLL clock). I can see code (a driver?) that does this but I don't believe it is being called (an inspection of the relevant register from the final user app that u-boot calls shows it has not been set, or not set correctly). I can see a patch 4 years ago that discusses this but I cannot for the life of me work out where or how from the myriad of Kconfig options, or anything else, that this would get called/set/used. Undoubtedly due to my inexperience with u-boot! Can someone please point me in the right direction? I don't think it's a bug/issue as such, I just need what is the magic CONFIG or board specific function/call, or whatever I need get the code called! Thanks, Tim.