linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marek Vasut <marex@denx.de>
To: Raviteja Narayanam <rna@xilinx.com>,
	"linux-i2c@vger.kernel.org" <linux-i2c@vger.kernel.org>
Cc: Michal Simek <michals@xilinx.com>,
	Shubhrajyoti Datta <shubhraj@xilinx.com>,
	Wolfram Sang <wsa@kernel.org>, Srinivas Goud <sgoud@xilinx.com>
Subject: Re: [PATCH 2/5] i2c: xiic: Drop broken interrupt handler
Date: Tue, 8 Sep 2020 16:04:33 +0200	[thread overview]
Message-ID: <488a2682-b15a-0463-b8be-b681c6d87b94@denx.de> (raw)
In-Reply-To: <SN4PR0201MB348634B4F722A224E071D049CA280@SN4PR0201MB3486.namprd02.prod.outlook.com>

On 9/7/20 10:51 AM, Raviteja Narayanam wrote:

[...]

>> Is this dynamic/standard mode switching what is already in the downstream
>> xilinx kernel tree ?
>>
>> I think we should fix what is already upstream first, and only then add more
>> complexity.
> 
> Yes, agreed. But, that would be a hardware fix in the future IP release. Since we have
> to support existing IP versions, we are planning to upstream the standard mode
> and based on the DT property (IP version), we will switch.

Is the dynamic mode addition be backported to stable as well ?
It is a lot of code, so I have a feeling that would be difficult.

Maybe it would be better to mark the xiic driver as broken until the
hardware is fixed ?

  reply	other threads:[~2020-09-08 16:40 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-13 15:07 [PATCH 1/5] i2c: xiic: Fix broken locking on tx_msg Marek Vasut
2020-06-13 15:07 ` [PATCH 2/5] i2c: xiic: Drop broken interrupt handler Marek Vasut
2020-06-17 12:25   ` Shubhrajyoti Datta
2020-06-17 12:31     ` Marek Vasut
2020-06-26 12:13   ` Raviteja Narayanam
2020-06-28 23:41     ` Marek Vasut
2020-06-29 12:52       ` Raviteja Narayanam
2020-06-29 21:50         ` Marek Vasut
2020-07-08 15:23           ` Raviteja Narayanam
2020-08-19 17:42             ` Marek Vasut
2020-08-24  8:27               ` Raviteja Narayanam
2020-08-24 11:58                 ` Marek Vasut
2020-08-25  9:44                   ` Raviteja Narayanam
2020-08-25 20:50                     ` Marek Vasut
2020-09-07  8:51                       ` Raviteja Narayanam
2020-09-08 14:04                         ` Marek Vasut [this message]
2020-09-11 10:28                           ` Michal Simek
2020-06-13 15:07 ` [PATCH 3/5] i2c: xiic: Defer xiic_wakeup() and __xiic_start_xfer() in xiic_process() Marek Vasut
2020-06-26 12:13   ` Raviteja Narayanam
2020-07-08 15:23     ` Raviteja Narayanam
2020-06-13 15:07 ` [PATCH 4/5] i2c: xiic: Switch from waitqueue to completion Marek Vasut
2020-06-26 12:13   ` Raviteja Narayanam
2020-06-28 23:41     ` Marek Vasut
2020-06-29 12:53       ` Raviteja Narayanam
2020-06-29 21:52         ` Marek Vasut
2020-06-13 15:07 ` [PATCH 5/5] i2c: xiic: Only ever transfer single message Marek Vasut
2020-06-13 19:33   ` Wolfram Sang
2020-06-13 19:37     ` Marek Vasut
2020-06-13 19:42       ` Wolfram Sang
2020-07-13  8:37         ` Michal Simek
2020-06-26 12:14   ` Raviteja Narayanam
2020-06-26 12:11 ` [PATCH 1/5] i2c: xiic: Fix broken locking on tx_msg Raviteja Narayanam
2020-06-28 23:18   ` Marek Vasut
2020-06-29 12:52     ` Raviteja Narayanam
2020-07-08 15:23       ` Raviteja Narayanam

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=488a2682-b15a-0463-b8be-b681c6d87b94@denx.de \
    --to=marex@denx.de \
    --cc=linux-i2c@vger.kernel.org \
    --cc=michals@xilinx.com \
    --cc=rna@xilinx.com \
    --cc=sgoud@xilinx.com \
    --cc=shubhraj@xilinx.com \
    --cc=wsa@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).