public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Heikki Krogerus <heikki.krogerus@linux.intel.com>
To: Andi Shyti <andi.shyti@kernel.org>,
	Mika Westerberg <mika.westerberg@linux.intel.com>
Cc: Andy Shevchenko <andriy.shevchenko@linux.intel.com>,
	Jan Dabros <jsd@semihalf.com>, Raag Jadav <raag.jadav@intel.com>,
	linux-i2c@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH v2 6/6] i2c: designware: Remove an unnecessary condition
Date: Thu, 18 Dec 2025 16:15:05 +0100	[thread overview]
Message-ID: <20251218151509.361617-7-heikki.krogerus@linux.intel.com> (raw)
In-Reply-To: <20251218151509.361617-1-heikki.krogerus@linux.intel.com>

Writing also the high speed timing registers unconditionally.
The reset value for these registers is 0, so this should
always be safe.

Suggested-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Signed-off-by: Heikki Krogerus <heikki.krogerus@linux.intel.com>
---
 drivers/i2c/busses/i2c-designware-common.c | 8 +++-----
 1 file changed, 3 insertions(+), 5 deletions(-)

diff --git a/drivers/i2c/busses/i2c-designware-common.c b/drivers/i2c/busses/i2c-designware-common.c
index aac7b1f4710f..1981dbfa260f 100644
--- a/drivers/i2c/busses/i2c-designware-common.c
+++ b/drivers/i2c/busses/i2c-designware-common.c
@@ -391,11 +391,9 @@ static void i2c_dw_write_timings(struct dw_i2c_dev *dev)
 	regmap_write(dev->map, DW_IC_FS_SCL_HCNT, dev->fs_hcnt);
 	regmap_write(dev->map, DW_IC_FS_SCL_LCNT, dev->fs_lcnt);
 
-	/* Write high speed timing parameters if supported */
-	if (dev->hs_hcnt && dev->hs_lcnt) {
-		regmap_write(dev->map, DW_IC_HS_SCL_HCNT, dev->hs_hcnt);
-		regmap_write(dev->map, DW_IC_HS_SCL_LCNT, dev->hs_lcnt);
-	}
+	/* Write high speed timing parameters */
+	regmap_write(dev->map, DW_IC_HS_SCL_HCNT, dev->hs_hcnt);
+	regmap_write(dev->map, DW_IC_HS_SCL_LCNT, dev->hs_lcnt);
 }
 
 /**
-- 
2.50.1


  parent reply	other threads:[~2025-12-18 15:15 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-18 15:14 [PATCH v2 0/6] i2c: designware: Enable mode swapping Heikki Krogerus
2025-12-18 15:15 ` [PATCH v2 1/6] i2c: designware: Remove useless driver specific option for I2C target Heikki Krogerus
2025-12-18 15:15 ` [PATCH v2 2/6] i2c: designware: Remove unnecessary function exports Heikki Krogerus
2025-12-18 15:15 ` [PATCH v2 3/6] i2c: designware: Combine some of the common functions Heikki Krogerus
2025-12-27 15:52   ` Andy Shevchenko
2025-12-30 14:14     ` Heikki Krogerus
2026-01-19 13:18       ` Heikki Krogerus
2026-01-19 13:44         ` Andy Shevchenko
2026-01-19 13:49           ` Heikki Krogerus
2025-12-18 15:15 ` [PATCH v2 4/6] i2c: designware: Combine the init functions Heikki Krogerus
2025-12-27 15:53   ` Andy Shevchenko
2025-12-18 15:15 ` [PATCH v2 5/6] i2c: designware: Enable mode swapping Heikki Krogerus
2025-12-18 15:15 ` Heikki Krogerus [this message]
2025-12-27 15:32   ` [PATCH v2 6/6] i2c: designware: Remove an unnecessary condition Andy Shevchenko
2025-12-19  7:43 ` [PATCH v2 0/6] i2c: designware: Enable mode swapping Mika Westerberg
2025-12-27 20:17 ` Andi Shyti

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=20251218151509.361617-7-heikki.krogerus@linux.intel.com \
    --to=heikki.krogerus@linux.intel.com \
    --cc=andi.shyti@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=jsd@semihalf.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=raag.jadav@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