From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S932571AbcHINE3 (ORCPT <rfc822;w@1wt.eu>);
	Tue, 9 Aug 2016 09:04:29 -0400
Received: from [195.159.176.226] ([195.159.176.226]:36392 "EHLO
	blaine.gmane.org" rhost-flags-FAIL-FAIL-OK-OK) by vger.kernel.org
	with ESMTP id S932240AbcHINE2 (ORCPT
	<rfc822;linux-kernel@vger.kernel.org>);
	Tue, 9 Aug 2016 09:04:28 -0400
X-Injected-Via-Gmane: http://gmane.org/
To: linux-kernel@vger.kernel.org
From: Stefan Monnier <monnier@iro.umontreal.ca>
Subject: Re: [RFC PATCH 0/5] Allwinner MMC firmware clocks implementation
Date: Tue, 09 Aug 2016 09:04:13 -0400
Message-ID: <jwv7fbqp048.fsf-monnier+gmane.comp.hardware.netbook.arm.sunxi@gnu.org>
References: <20160809115303.17032-1-andre.przywara@arm.com>
Mime-Version: 1.0
Content-Type: text/plain
X-Complaints-To: usenet@blaine.gmane.org
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.1.50 (gnu/linux)
Cancel-Lock: sha1:zdH/5YlIC4L+HDPbwCiPtl8VlwU=
Cc: linux-sunxi@googlegroups.com, linux-arm-kernel@lists.infradead.org
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

> frequencies in an SoC agnostic manner. The actual clock access can be
> put in firmware, which is by definition SoC specific and thus can
> be easier and much quicker adapted to support a new SoC.

Hmm... what do you mean by "firmware"?


        Stefan "just a by-stander trying to understand"