From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: Andi Shyti <andi.shyti@kernel.org>,
Mika Westerberg <mika.westerberg@linux.intel.com>,
Jan Dabros <jsd@semihalf.com>
Subject: [PATCH v1 0/2] i2c: designware: Clean up MODEL_* definitions
Date: Wed, 14 Jan 2026 09:17:49 +0100 [thread overview]
Message-ID: <20260114081954.252160-1-andriy.shevchenko@linux.intel.com> (raw)
The current way of recognizing models is not scalable and in most of the cases
just a replacement of well established device_is_compatible() approach.
For now take the low-hanging fruits and partially clean up those MODEL_*
definitions.
Andy Shevchenko (2):
i2c: designware: Remove not-going-to-be-supported code for Baikal SoC
i2c: designware: Use device_is_compatible() instead of custom approach
drivers/i2c/busses/Kconfig | 1 -
drivers/i2c/busses/i2c-designware-common.c | 6 +-
drivers/i2c/busses/i2c-designware-core.h | 2 -
drivers/i2c/busses/i2c-designware-platdrv.c | 70 +--------------------
4 files changed, 2 insertions(+), 77 deletions(-)
--
2.50.1
next reply other threads:[~2026-01-14 8:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-14 8:17 Andy Shevchenko [this message]
2026-01-14 8:17 ` [PATCH v1 1/2] i2c: designware: Remove not-going-to-be-supported code for Baikal SoC Andy Shevchenko
2026-01-14 11:50 ` Mika Westerberg
2026-01-15 15:23 ` Andi Shyti
2026-01-14 8:17 ` [PATCH v1 2/2] i2c: designware: Use device_is_compatible() instead of custom approach Andy Shevchenko
2026-01-14 11:53 ` Mika Westerberg
2026-01-14 16:09 ` Andy Shevchenko
2026-01-15 5:39 ` Mika Westerberg
2026-01-15 7:41 ` Andy Shevchenko
2026-01-15 10:06 ` Mika Westerberg
2026-01-22 11:10 ` Andi Shyti
2026-01-22 11:49 ` Andy Shevchenko
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=20260114081954.252160-1-andriy.shevchenko@linux.intel.com \
--to=andriy.shevchenko@linux.intel.com \
--cc=andi.shyti@kernel.org \
--cc=jsd@semihalf.com \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mika.westerberg@linux.intel.com \
/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