Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on aws-us-west-2-korg-lkml-1.web.codeaurora.org Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by smtp.lore.kernel.org (Postfix) with ESMTP id 37265C64EC4 for ; Wed, 8 Mar 2023 10:46:57 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S230207AbjCHKqz (ORCPT ); Wed, 8 Mar 2023 05:46:55 -0500 Received: from lindbergh.monkeyblade.net ([23.128.96.19]:41228 "EHLO lindbergh.monkeyblade.net" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S230148AbjCHKqx (ORCPT ); Wed, 8 Mar 2023 05:46:53 -0500 Received: from mail-ed1-x52e.google.com (mail-ed1-x52e.google.com [IPv6:2a00:1450:4864:20::52e]) by lindbergh.monkeyblade.net (Postfix) with ESMTPS id E96F7A42E4 for ; Wed, 8 Mar 2023 02:46:51 -0800 (PST) Received: by mail-ed1-x52e.google.com with SMTP id ec29so33060501edb.6 for ; Wed, 08 Mar 2023 02:46:51 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=linaro.org; s=google; t=1678272410; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :from:to:cc:subject:date:message-id:reply-to; bh=rdWkIz4I/mxvd/Alb9OvKLBH8sveQNRk7IcI1jXiuY8=; b=AXZ8uCMWCcREcyS94FpoZqMnKKe/WpjFlOMRO8KYKhs+YCTQodptdJuUyp8JVnGCl5 XQitDjfSuOEj9nopmoTe2oVQMWwNwt/bjknTKYlDjXhJAGB2iAfrWRRI037DROIeDhhZ grxln2NnNtjXp7yqkIKCwVKjzzbVb5S5/avPGiglZbc1ov/R5LyAqpOLrfMDU+zOaqhh aatvRB4nPXJDCqevA5UKOAE6bSOwDaYbPHrBzZP4tgVgqM/YFmhKkiWzKPLv4+3W0p0v CWN/kxlAHOXCljZgUm60bZZ3o+NtZ23chsVfAPiTvr5xgDiwjQNN0RByCYRs3WSENLJn ReaQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20210112; t=1678272410; h=content-transfer-encoding:in-reply-to:from:references:cc:to :content-language:subject:user-agent:mime-version:date:message-id :x-gm-message-state:from:to:cc:subject:date:message-id:reply-to; bh=rdWkIz4I/mxvd/Alb9OvKLBH8sveQNRk7IcI1jXiuY8=; b=x1koFH5K2AjgNt1PM0ZDmJ/gXYD6DlTzgpiINiuaCC12ZZ7UvR+d+Plz2jQAuGjlvF iqp2byM1I6qNtYIF5tpEiQduDvzt/YwxjKMz1RlgNznpkZu8aOgfSe7qnSBFuP6YEUTn qlEKWx1JOGvv+zTSECL/FRYYrmqgllCDcqGpVZSSHZnWPP0hRAJ3pBIHdLSenPePsqY9 gE1guxolYrR/G6nfnGWM4M5KHuWi2EaRV86s0mqfLz+14C107oH0yk7aLRs3MeuPzSWD pOOr/eguuA7R/01D1FLkSIMXdF9w0LKXG4N+mZX4gEFOuJftPiGS1O4EdKiXF+bmzcJr Jubw== X-Gm-Message-State: AO0yUKX+2xMe3MXlkVOCwjHyFodQJiF9G0FxMCeA9/28fCmtOHerpbYA EAsp1z1yxmzW+JDzFntxPjFbSg== X-Google-Smtp-Source: AK7set95jOe3tjacrO60yOKeB/hWtdyT8wql5anCCp+Jg47/qP+Fx45GFy11PcpWricimaeVl4I+zw== X-Received: by 2002:a05:6402:690:b0:4ad:7301:fe77 with SMTP id f16-20020a056402069000b004ad7301fe77mr15651638edy.9.1678272410334; Wed, 08 Mar 2023 02:46:50 -0800 (PST) Received: from ?IPV6:2a02:810d:15c0:828:ff33:9b14:bdd2:a3da? ([2a02:810d:15c0:828:ff33:9b14:bdd2:a3da]) by smtp.gmail.com with ESMTPSA id j23-20020a170906255700b008d9c518a318sm7432293ejb.142.2023.03.08.02.46.49 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 08 Mar 2023 02:46:49 -0800 (PST) Message-ID: Date: Wed, 8 Mar 2023 11:46:49 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:102.0) Gecko/20100101 Thunderbird/102.8.0 Subject: Re: [PATCH v1] max77663-rtc: pass rtc address from device tree node if exists Content-Language: en-US To: Svyatoslav Ryhel Cc: Chanwoo Choi , Alessandro Zummo , Alexandre Belloni , linux-kernel@vger.kernel.org, linux-rtc@vger.kernel.org References: <20230308083759.11692-1-clamor95@gmail.com> <190897d3-39b6-fb7c-dc18-dac580fadea6@linaro.org> From: Krzysztof Kozlowski In-Reply-To: Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Precedence: bulk List-ID: X-Mailing-List: linux-kernel@vger.kernel.org On 08/03/2023 10:29, Svyatoslav Ryhel wrote: > ср, 8 бер. 2023 р. о 11:11 Krzysztof Kozlowski > пише: >> >> On 08/03/2023 09:58, Svyatoslav Ryhel wrote: >>> I would love to, but max77663 uses max77686 rtc >>> https://github.com/torvalds/linux/blob/master/drivers/mfd/max77620.c#L123 >>> how to handle this? >> >> Don't top post. >> >> Hm, so it seems max7763 is already documented via max77620. I missed >> that. Add the new property to max77620, not to max77686 RTC. It does not >> look like RTC's property, but the PMIC's. > > There is no max77620 yaml, only txt. Add property to txt? If property was to accept, then unfortunately no, you need to convert first. Best regards, Krzysztof