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 S1752864AbdGMWbC (ORCPT <rfc822;w@1wt.eu>);
        Thu, 13 Jul 2017 18:31:02 -0400
Received: from mail-pg0-f53.google.com ([74.125.83.53]:35833 "EHLO
        mail-pg0-f53.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org
        with ESMTP id S1752446AbdGMWbB (ORCPT
        <rfc822;linux-kernel@vger.kernel.org>);
        Thu, 13 Jul 2017 18:31:01 -0400
From: Brendan Higgins <brendanhiggins@google.com>
To: wsa@the-dreams.de, benh@kernel.crashing.org, joel@jms.id.au
Cc: linux-i2c@vger.kernel.org, openbmc@lists.ozlabs.org,
        linux-kernel@vger.kernel.org
Subject: [PATCH v1 0/1] i2c: aspeed: add proper support for 24xx clock params
Date: Thu, 13 Jul 2017 15:30:51 -0700
Message-Id: <20170713223052.8387-1-brendanhiggins@google.com>
X-Mailer: git-send-email 2.13.2.932.g7449e964c-goog
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

Joel, Ben, our g5 device tree has I2C bus compatibility strings for the 24xx;
this will need to be changed because the clock is no longer programmed the same
way for the 24xx and the 25xx. I have a patch that fixes this; I will send it to
the OpenBMC list once this patch gets accepted.

Tested on an Aspeed 2400 and an Aspeed 2500.