From mboxrd@z Thu Jan 1 00:00:00 1970 From: "Enrico Weigelt, metux IT consult" Subject: Re: linux-next: Tree for Apr 29 (drivers/leds/leds-turris-omnia) Date: Mon, 29 Apr 2019 20:49:59 +0200 Message-ID: References: <20190429190354.0d5e2e93@canb.auug.org.au> <20190429153200.GA11761@amd> <20190429173842.06f02852@nic.cz> <20190429163753.GA16782@amd> <20190429184439.68049050@nic.cz> <20190429165319.GB16782@amd> <20190429181245.GA24658@amd> Mime-Version: 1.0 Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20190429181245.GA24658@amd> Content-Language: en-US Sender: linux-kernel-owner@vger.kernel.org To: Pavel Machek Cc: Marek Behun , Randy Dunlap , Stephen Rothwell , Linux Next Mailing List , Linux Kernel Mailing List , linux-leds@vger.kernel.org List-Id: linux-next.vger.kernel.org On 29.04.19 20:12, Pavel Machek wrote: >> Is that controller only built-in into some SoCs, or also available >> as a separate chip ? > > AFAIU.. separate chip, but runs firmware not likely to be available > outside Turris routers. hmm, if it's a separate chip, IMHO it should be selectable, so that anybody who puts that chip on his board can directly use it. --mtx -- Enrico Weigelt, metux IT consult Free software and Linux embedded engineering info@metux.net -- +49-151-27565287