From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org X-Spam-Level: X-Spam-Status: No, score=-7.0 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS, INCLUDES_PATCH,MAILING_LIST_MULTI,SIGNED_OFF_BY,SPF_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.0 Received: from mail.kernel.org (mail.kernel.org [198.145.29.99]) by smtp.lore.kernel.org (Postfix) with ESMTP id E87E9C282C2 for ; Thu, 7 Feb 2019 10:41:52 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C01EF2147C for ; Thu, 7 Feb 2019 10:41:52 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1726967AbfBGKlv (ORCPT ); Thu, 7 Feb 2019 05:41:51 -0500 Received: from metis.ext.pengutronix.de ([85.220.165.71]:47301 "EHLO metis.ext.pengutronix.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1726876AbfBGKls (ORCPT ); Thu, 7 Feb 2019 05:41:48 -0500 Received: from lupine.hi.pengutronix.de ([2001:67c:670:100:3ad5:47ff:feaf:1a17] helo=lupine) by metis.ext.pengutronix.de with esmtp (Exim 4.89) (envelope-from ) id 1grh7n-00089p-2H; Thu, 07 Feb 2019 11:41:43 +0100 Message-ID: <1549536102.4557.10.camel@pengutronix.de> Subject: Re: [PATCH 3/3] reset: hisilicon: Add HiSilicon HI3670 reset support From: Philipp Zabel To: Manivannan Sadhasivam , xuwei5@hisilicon.com, robh+dt@kernel.org Cc: linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org, linux-kernel@vger.kernel.org, guodong.xu@linaro.org Date: Thu, 07 Feb 2019 11:41:42 +0100 In-Reply-To: <20190201153841.21903-4-manivannan.sadhasivam@linaro.org> References: <20190201153841.21903-1-manivannan.sadhasivam@linaro.org> <20190201153841.21903-4-manivannan.sadhasivam@linaro.org> Content-Type: text/plain; charset="UTF-8" X-Mailer: Evolution 3.22.6-1+deb9u1 Mime-Version: 1.0 Content-Transfer-Encoding: 7bit X-SA-Exim-Connect-IP: 2001:67c:670:100:3ad5:47ff:feaf:1a17 X-SA-Exim-Mail-From: p.zabel@pengutronix.de X-SA-Exim-Scanned: No (on metis.ext.pengutronix.de); SAEximRunCond expanded to false X-PTX-Original-Recipient: linux-kernel@vger.kernel.org Sender: linux-kernel-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On Fri, 2019-02-01 at 21:08 +0530, Manivannan Sadhasivam wrote: > HI3670 SoC is architecturally same as the HI3660 SoC. Hence, add the > HI3670 compatible to HI3660 reset driver in order to reuse it. > > Signed-off-by: Manivannan Sadhasivam > --- > drivers/reset/hisilicon/reset-hi3660.c | 1 + > 1 file changed, 1 insertion(+) > > diff --git a/drivers/reset/hisilicon/reset-hi3660.c b/drivers/reset/hisilicon/reset-hi3660.c > index 17d8bb128e6e..1c22f3457ba7 100644 > --- a/drivers/reset/hisilicon/reset-hi3660.c > +++ b/drivers/reset/hisilicon/reset-hi3660.c > @@ -103,6 +103,7 @@ static int hi3660_reset_probe(struct platform_device *pdev) > > static const struct of_device_id hi3660_reset_match[] = { > { .compatible = "hisilicon,hi3660-reset", }, > + { .compatible = "hisilicon,hi3670-reset", }, > {}, > }; > MODULE_DEVICE_TABLE(of, hi3660_reset_match); If the HI3670 device tree contained the hisilicon,hi3660-reset compatible as well, this change would not be necessary. regards Philipp