From patchwork Fri Apr 27 16:02:58 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Patchwork-Submitter: =?utf-8?q?Pawe=C5=82_Chmiel?= X-Patchwork-Id: 905843 Return-Path: X-Original-To: incoming-dt@patchwork.ozlabs.org Delivered-To: patchwork-incoming-dt@bilbo.ozlabs.org Authentication-Results: ozlabs.org; spf=none (mailfrom) smtp.mailfrom=vger.kernel.org (client-ip=209.132.180.67; helo=vger.kernel.org; envelope-from=devicetree-owner@vger.kernel.org; receiver=) Authentication-Results: ozlabs.org; dmarc=fail (p=none dis=none) header.from=gmail.com Authentication-Results: ozlabs.org; dkim=fail reason="signature verification failed" (2048-bit key; unprotected) header.d=gmail.com header.i=@gmail.com header.b="rSFu2wZb"; dkim-atps=neutral Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by ozlabs.org (Postfix) with ESMTP id 40Xf0k34xzz9s0v for ; Sat, 28 Apr 2018 02:05:26 +1000 (AEST) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1758594AbeD0QFY (ORCPT ); Fri, 27 Apr 2018 12:05:24 -0400 Received: from mail-lf0-f68.google.com ([209.85.215.68]:43340 "EHLO mail-lf0-f68.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1758550AbeD0QFX (ORCPT ); Fri, 27 Apr 2018 12:05:23 -0400 Received: by mail-lf0-f68.google.com with SMTP id g12-v6so3424934lfb.10; Fri, 27 Apr 2018 09:05:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=qsmipXqAavoDKUfCf2k3nFluAS5M/9FOJofHjGW364w=; b=rSFu2wZbXmkMEpE8bAMLqSQBQtwHd+Wn1yzxBAv3M5fWoltZC7UbgBj3T5ShkYgmIj XHNxh8ZGAQ0N39W6y3Gu/e26LP8IcnLj16pDL7eVm3yY42zwgE94ceUuvp9XktE5dbnR 6IKyGDU1MBQzKHSN52x08mwDXPeGNZlLkk9gst+8QsLNlLoB8DF4X7BsNprwEe4oRvKE mtV/0bu8t1A5sX0oU7yGTuOmmZSOhboblJrn/CFqmNR8Wjf527DW3xQs3qx7tlzzRNwI 8Tog7h8SzNGjXTR9L6A9xJtNaZfbbBhzbNqvvF01l8h/VqCpJK37qOIeLIEYeKFsbbWZ jDKA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:to:cc:subject:date:message-id:mime-version :content-transfer-encoding; bh=qsmipXqAavoDKUfCf2k3nFluAS5M/9FOJofHjGW364w=; b=XrzGDcn1YmEKgenA2KO9SfLtCCSJ1tTVeVbCdO+yLmWahThsILyJ2db1djOA3/NzoG YcOIEEFATlkiguulRjtGoO+EfuIbwPNVVfcWM49nuVIYHyGDoSV7TMJbfjQRl5BwJIzy tZnF5hwmTVDSnVFstFYuNwqkZaYhAv92BAshbSk3O5ofM08n5QBCeIAdto04jbaEb44a 4KGVmtxwCiWI8m5jwzj3ht/xA5nF/5S3RTn+D/vfNpD74o9shEoskINXYmIm4LeklVLL l368O821KG/kl6deFAtWquPoBhZQqFysZqr5PVQ/NstqL3lc8oZGg07O7+ku8z8uPVBQ 3D7g== X-Gm-Message-State: ALQs6tCCH9UjGlexH7jjG0D/r3C6wXVDtmkMWss6udDnjYZ0OTJJJQ82 XivfxN1lW3PKKlRuPHGj0f5BN9XnyMk= X-Google-Smtp-Source: AB8JxZqGOQ2IkZjXF4ToUsAgLaXsR50ZDF7KqLY5DpDd3stcYjvdAoQDUW2QorvZf4b8mk94FiWThg== X-Received: by 2002:a19:e583:: with SMTP id i3-v6mr1973198lfk.135.1524845121776; Fri, 27 Apr 2018 09:05:21 -0700 (PDT) Received: from localhost.localdomain (user-94-254-173-44.play-internet.pl. [94.254.173.44]) by smtp.googlemail.com with ESMTPSA id j85-v6sm324083lfh.5.2018.04.27.09.05.20 (version=TLS1_2 cipher=ECDHE-RSA-AES128-SHA bits=128/128); Fri, 27 Apr 2018 09:05:20 -0700 (PDT) From: =?utf-8?q?Pawe=C5=82_Chmiel?= To: lgirdwood@gmail.com, broonie@kernel.org, sre@kernel.org, lee.jones@linaro.org, robh+dt@kernel.org, mark.rutland@arm.com Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org, devicetree@vger.kernel.org, =?utf-8?q?Pawe=C5=82_Chmiel?= Subject: [PATCH 0/4] mfd: max8998: Device Tree support fixes Date: Fri, 27 Apr 2018 18:02:58 +0200 Message-Id: <1524844982-4714-1-git-send-email-pawel.mikolaj.chmiel@gmail.com> X-Mailer: git-send-email 2.7.4 MIME-Version: 1.0 Sender: devicetree-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: devicetree@vger.kernel.org This patch series compose of 4 patches. First patch, fixes platform data retrieval issue in max8998 regulator driver, which could cause NULL pointer dereference. Second patch, fixes platform data retrieval issue in max8998 charger driver, which could cause NULL pointer dereference. Third patch, updates max8998 charger driver, so it's possible to parse devicetree for configuration. Fourth patch, updates max8998 documentation, so it includes new node and properties, needed for charger. All patches has been tested on (not yet mainlined), an S5PV210 based Samsung Galaxy S (i9000) phone. Paweł Chmiel (3): regulator: max8998: Fix platform data retrieval. power: supply: max8998-charger: Parse device tree for required data. dt-bindings: mfd: max8998: Add charger subnode binding Tomasz Figa (1): power: supply: max8998-charger: Fix platform data retrieval Documentation/devicetree/bindings/mfd/max8998.txt | 22 ++++++++++ drivers/power/supply/max8998_charger.c | 52 ++++++++++++++++++++++- drivers/regulator/max8998.c | 3 +- 3 files changed, 74 insertions(+), 3 deletions(-)