Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752549AbbD3SUo (ORCPT ); Thu, 30 Apr 2015 14:20:44 -0400 Received: from mail-la0-f49.google.com ([209.85.215.49]:34669 "EHLO mail-la0-f49.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751807AbbD3SUk (ORCPT ); Thu, 30 Apr 2015 14:20:40 -0400 MIME-Version: 1.0 In-Reply-To: <1430415954-29517-4-git-send-email-sebastian.hesselbarth@gmail.com> References: <1430415954-29517-1-git-send-email-sebastian.hesselbarth@gmail.com> <1430415954-29517-4-git-send-email-sebastian.hesselbarth@gmail.com> Date: Thu, 30 Apr 2015 15:20:38 -0300 Message-ID: Subject: Re: [PATCH 3/4] clk: si5351: Do not pass struct clk in platform_data From: Fabio Estevam To: Sebastian Hesselbarth Cc: Jean-Francois Moine , Mike Turquette , Stephen Boyd , linux-kernel , Michael Welling , Russell King , linux-clk@vger.kernel.org, "linux-arm-kernel@lists.infradead.org" Content-Type: text/plain; charset=UTF-8 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1128 Lines: 26 On Thu, Apr 30, 2015 at 2:45 PM, Sebastian Hesselbarth wrote: > * property silabs,pll-source : , [<..>] > * allow to selectively set pll source > @@ -1328,8 +1321,17 @@ static int si5351_i2c_probe(struct i2c_client *client, > i2c_set_clientdata(client, drvdata); > drvdata->client = client; > drvdata->variant = variant; > - drvdata->pxtal = pdata->clk_xtal; > - drvdata->pclkin = pdata->clk_clkin; > + drvdata->pxtal = devm_clk_get(&client->dev, "xtal"); > + drvdata->pclkin = devm_clk_get(&client->dev, "clkin"); > + > + if (PTR_ERR(drvdata->pxtal) == -EPROBE_DEFER || > + PTR_ERR(drvdata->pclkin) == -EPROBE_DEFER) > + return -EPROBE_DEFER; > + > + if (IS_ERR(drvdata->pxtal) && IS_ERR(drvdata->pclkin)) { Don't you want || instead? -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/