From mboxrd@z Thu Jan 1 00:00:00 1970 From: Stefan Roese Date: Mon, 13 Jan 2020 09:19:48 +0100 Subject: [PATCH 03/10] arm: mvebu: clearfog: initial ClearFog Base variant In-Reply-To: References: <20200111193639.19022-1-mrjoel@lixil.net> <20200111193639.19022-3-mrjoel@lixil.net> <87r205yoac.fsf@tarshish> Message-ID: List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de On 12.01.20 16:16, Joel Johnson wrote: > > > On January 12, 2020 10:14:35 AM UTC, Baruch Siach wrote: >> Hi Joel, >> >> Thanks for working on Clearfog hardware support improvements. > > Sure - I finally just got tired of not being able to easily use mainline builds, sat down and figured out the gaps and missing dependencies in order to support at least my use cases and flexibility in general. > >> >> On Sat, Jan 11 2020, Joel Johnson wrote: >>> Add a unique entry for ClearFog Base variant, reflected >>> in the board name and adjusted SerDes topology. >> >> This conflicts with the series I posted adding support for A388 SOM and >> Clearfog Base/Pro carriers EEPROM TLV: >> >> https://patchwork.ozlabs.org/cover/1200324/ >> >> The EEPROM TLV is meant to allow run-time detection of the hardware on >> newer hardware revisions that populate the EEPROM. This patch is still >> useful for older SOM and carrier revisions but it might cause confusion >> for users. >> >> Would you mind to rebase your patches on top of my code? > > Sure, I hadn't seen this in flight patch series, I'll take a look and adjust/adapt/drop as needed. I believe that most of my units are older non-EEPROM variants, but will test with your patches and at least make the manual vs. dynamic detected config interoperable. Okay, let's wait for Baruch to update his patchset and yours rebased on top of that one. Thanks, Stefan