From: "Shah, Nehal-bakulchandra" <nehal-bakulchandra.shah@amd.com>
To: Heikki Krogerus <heikki.krogerus@linux.intel.com>
Cc: "Shah, Nehal-bakulchandra" <nbshah@amd.com>,
ajayg@nvidia.com, linux-usb@vger.kernel.org
Subject: Re: UCSI:CCG: AMD Platform
Date: Sat, 29 Feb 2020 08:55:50 +0530 [thread overview]
Message-ID: <9fcf4549-e699-1a35-d87a-6bacf85fba29@amd.com> (raw)
In-Reply-To: <278ab9a6-497b-9cd5-8aa1-440fc78cb3db@amd.com>
Hi
On 2/27/2020 10:29 PM, Shah, Nehal-bakulchandra wrote:
> Hi
> On 2/27/2020 5:53 PM, Heikki Krogerus wrote:
>> On Mon, Feb 24, 2020 at 02:38:12PM +0530, Shah, Nehal-bakulchandra wrote:
>>> Hi
>>>
>>> On 2/14/2020 7:58 PM, Shah, Nehal-bakulchandra wrote:
>>>> Hi
>>>>
>>>> On 2/13/2020 5:35 PM, Heikki Krogerus wrote:
>>>>> On Thu, Feb 13, 2020 at 02:00:14PM +0200, Heikki Krogerus wrote:
>>>>>>> I am using CCG based UCSI driver without any
>>>>>>> modification.For I2C part i have written custom
>>>>>>> driver.
>>>>>>>
>>>>>>> I have attached the trace out and dmesg crash log.
>>>>>>>
>>>>>>> Please have a look
>>>>>> Thanks for the logs. Can you test the attached diff?
>>>>> Actually, don't try that one. Try this one instead.
>>>> Sure i will update on this on Monday.
>>>>
>>>>
>>>> thanks
>>>>
>>>> Nehal
>>> Patch is not solving the issue. I have attached both trace and dmesg output.
>> How about if you try this (the attached patch) together with that
>> previous diff?
>>
>> thanks,
> Sure, infact i suspected that in first place and tried same logic but it was failed but now i will check with both patch combine and shall update.
>
> Thanks
>
> Nehal Shah
This is still crashing .
Thanks
Nehal Shah
next prev parent reply other threads:[~2020-02-29 3:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-03 5:22 UCSI:CCG: AMD Platform Shah, Nehal-bakulchandra
2020-02-03 13:28 ` Heikki Krogerus
2020-02-03 13:32 ` Heikki Krogerus
2020-02-10 10:09 ` Shah, Nehal-bakulchandra
2020-02-13 12:00 ` Heikki Krogerus
2020-02-13 12:05 ` Heikki Krogerus
2020-02-14 14:28 ` Shah, Nehal-bakulchandra
2020-02-24 9:08 ` Shah, Nehal-bakulchandra
2020-02-27 12:23 ` Heikki Krogerus
2020-02-27 16:59 ` Shah, Nehal-bakulchandra
2020-02-29 3:25 ` Shah, Nehal-bakulchandra [this message]
2020-03-26 8:35 ` Heikki Krogerus
2020-03-26 13:41 ` Shah, Nehal-bakulchandra
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=9fcf4549-e699-1a35-d87a-6bacf85fba29@amd.com \
--to=nehal-bakulchandra.shah@amd.com \
--cc=ajayg@nvidia.com \
--cc=heikki.krogerus@linux.intel.com \
--cc=linux-usb@vger.kernel.org \
--cc=nbshah@amd.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;
as well as URLs for NNTP newsgroup(s).