From: Wolfgang Denk Date: Tue, 17 Mar 2020 15:36:19 +0100 Subject: [PATCH] powerpc: remove WATCHDOG_RESET call from wait_ticks() In-Reply-To: <56b724ef-8051-8a46-5df8-fc5b00bd8408@prevas.dk> References: <20200316212337.30204-1-rasmus.villemoes@prevas.dk> <20200317100249.1DECD24003E@gemini.denx.de> <1b6c7efd-8264-6cb5-0b39-3223bae5f8dc@prevas.dk> <20200317122144.C479B24003E@gemini.denx.de> <01193803-be8f-865d-5fce-2c7cee0fd9af@prevas.dk> <1682e1ef-430a-56a4-642a-e73db864ce59@c-s.fr> <56b724ef-8051-8a46-5df8-fc5b00bd8408@prevas.dk> Message-ID: <20200317143619.6D71724003E@gemini.denx.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear Rasmus, In message <56b724ef-8051-8a46-5df8-fc5b00bd8408@prevas.dk> you wrote: > > Yes, but I'm not talking about or using the SOC watchdog. Also, this is > not really about the particular watchdog device at all. It is about what > generic code can expect from the __udelay primitive, which is not > currently that on ppc. Maybe what you expect from __udelay() is not what other people expect(ed) from it? I don't think there is any formal description of that __udelay() is supposed to do in any existing U-Boot documentation... Please just face facts: for nearly two decades this code has been doing what it does, and I guess there were good reasons at that time (like memory footprint and resources to fix a specific problem). I agree that from a design point of view this is not nice, but that's not the point here. Best regards, Wolfgang Denk -- DENX Software Engineering GmbH, Managing Director: Wolfgang Denk HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de No, I'm not going to explain it. If you can't figure it out, you didn't want to know anyway... :-) - Larry Wall in <1991Aug7.180856.2854@netlabs.com>