linux-rtc.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Claudius Heine <ch@denx.de>
To: Alessandro Zummo <a.zummo@towertech.it>,
	Alexandre Belloni <alexandre.belloni@bootlin.com>,
	linux-rtc@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Henning Schild <henning.schild@siemens.com>,
	Johannes Hahn <johannes-hahn@siemens.com>,
	Claudius Heine <ch@denx.de>
Subject: [PATCH v2 0/3] Adding I2C support to RX6110 RTC
Date: Thu, 12 Nov 2020 14:07:31 +0100	[thread overview]
Message-ID: <20201112130734.331094-1-ch@denx.de> (raw)

Hi,

here is the 2nd version of the patchset that adds I2C support to the RX6110 RTC.

Changes from v1:
- moved common probing code into its own function `rx6110_probe`
- added a small patch to fix a type in the Kconfig


Claudius Heine (2):
  rtc: rx6110: add i2c support
  rtc: Kconfig: Fix typo in help message of rx 6110

Johannes Hahn (1):
  rtc: rx6110: add ACPI bindings to I2C

 drivers/rtc/Kconfig      |  20 +++--
 drivers/rtc/rtc-rx6110.c | 177 ++++++++++++++++++++++++++++++++++-----
 2 files changed, 166 insertions(+), 31 deletions(-)

-- 
2.20.1


             reply	other threads:[~2020-11-12 13:08 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-12 13:07 Claudius Heine [this message]
2020-11-12 13:07 ` [PATCH v2 1/3] rtc: rx6110: add i2c support Claudius Heine
2020-11-12 13:19   ` Claudius Heine
2020-11-16 14:43   ` Andy Shevchenko
2020-11-16 17:36     ` Alexandre Belloni
2020-11-16 17:58       ` Andy Shevchenko
2020-11-12 13:07 ` [PATCH v2 2/3] rtc: rx6110: add ACPI bindings to I2C Claudius Heine
2020-11-16 14:46   ` Andy Shevchenko
2020-11-16 15:30     ` Henning Schild
2020-11-16 16:05       ` Andy Shevchenko
2020-11-16 16:08         ` Andy Shevchenko
2020-11-17  7:37       ` AW: " johannes-hahn
2020-11-17 11:10         ` Andy Shevchenko
2020-11-17 11:17           ` Andy Shevchenko
2020-11-17  9:46       ` AW: " johannes-hahn
2020-11-17 11:33         ` Andy Shevchenko
2020-11-17 11:41           ` Andy Shevchenko
2020-11-18 10:04             ` Henning Schild
2020-11-18 10:58               ` AW: " werner.zeh
2021-03-16 10:08                 ` [PATCH v3 0/1] add ACPI binding to RX6110 driver Claudius Heine
2021-03-16 14:48                   ` [PATCH v4] rtc: rx6110: add ACPI bindings to I2C Claudius Heine
2021-03-16 16:55                     ` Andy Shevchenko
2021-03-17  7:53                       ` Claudius Heine
2021-03-16 19:04                     ` kernel test robot
2021-03-16 20:44                       ` Andy Shevchenko
2021-03-16 10:08                 ` [PATCH v3 1/1] " Claudius Heine
2021-03-16 11:30                   ` Andy Shevchenko
2021-03-16 11:33                     ` Andy Shevchenko
2021-03-16 11:52                     ` Henning Schild
2021-03-16 13:46                       ` Andy Shevchenko
2020-11-12 13:07 ` [PATCH v2 3/3] rtc: Kconfig: Fix typo in help message of rx 6110 Claudius Heine

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20201112130734.331094-1-ch@denx.de \
    --to=ch@denx.de \
    --cc=a.zummo@towertech.it \
    --cc=alexandre.belloni@bootlin.com \
    --cc=henning.schild@siemens.com \
    --cc=johannes-hahn@siemens.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-rtc@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).