All of lore.kernel.org
 help / color / mirror / Atom feed
From: <Tudor.Ambarus@microchip.com>
To: <p.yadav@ti.com>, <daniel@0x0f.com>
Cc: <linux-mtd@lists.infradead.org>, <michael@walle.cc>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mtd: spi-nor: Add support for ZB25VQ128
Date: Wed, 29 Sep 2021 05:16:52 +0000	[thread overview]
Message-ID: <4a57745e-dd0e-7890-0767-e6eaabeecd63@microchip.com> (raw)
In-Reply-To: <20210928163403.iufy6rgn7imiebpz@ti.com>

On 9/28/21 7:34 PM, Pratyush Yadav wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On 28/09/21 10:15PM, Daniel Palmer wrote:
>> Hi Pratyush,
>>
>> On Mon, 20 Sept 2021 at 20:26, Pratyush Yadav <p.yadav@ti.com> wrote:
>>>
>>> Zbit should be in bank 10, so it should be preceeded by 9 0x7f bytes,
>>> correct? I don't see any logic to handle that in SPI NOR currently so I
>>> assume this manufacturer does not implement the continuation codes.
>>>
>>> In that case, it should go to the manufacturer collisions driver
>>> proposed here [0].
>>>
>>> [0] https://patchwork.ozlabs.org/project/linux-mtd/patch/20210727045222.905056-6-tudor.ambarus@microchip.com/
>>
>> Sorry, I'm not sure what I should do with this information. I didn't
>> even know about the continuation codes thing until now.
>> Is there something I need to do here or do I just need to wait for the
>> collision handling code to get merged?
> 
> I think that should be what you need to do. Tudor, any plans on
> re-rolling that patch series in the near future?
> 
Hi, all,

Yes, I was out of office for a month, today I got back. I'll handle it.

Cheers,
ta
______________________________________________________
Linux MTD discussion mailing list
http://lists.infradead.org/mailman/listinfo/linux-mtd/

WARNING: multiple messages have this Message-ID (diff)
From: <Tudor.Ambarus@microchip.com>
To: <p.yadav@ti.com>, <daniel@0x0f.com>
Cc: <linux-mtd@lists.infradead.org>, <michael@walle.cc>,
	<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] mtd: spi-nor: Add support for ZB25VQ128
Date: Wed, 29 Sep 2021 05:16:52 +0000	[thread overview]
Message-ID: <4a57745e-dd0e-7890-0767-e6eaabeecd63@microchip.com> (raw)
In-Reply-To: <20210928163403.iufy6rgn7imiebpz@ti.com>

On 9/28/21 7:34 PM, Pratyush Yadav wrote:
> EXTERNAL EMAIL: Do not click links or open attachments unless you know the content is safe
> 
> On 28/09/21 10:15PM, Daniel Palmer wrote:
>> Hi Pratyush,
>>
>> On Mon, 20 Sept 2021 at 20:26, Pratyush Yadav <p.yadav@ti.com> wrote:
>>>
>>> Zbit should be in bank 10, so it should be preceeded by 9 0x7f bytes,
>>> correct? I don't see any logic to handle that in SPI NOR currently so I
>>> assume this manufacturer does not implement the continuation codes.
>>>
>>> In that case, it should go to the manufacturer collisions driver
>>> proposed here [0].
>>>
>>> [0] https://patchwork.ozlabs.org/project/linux-mtd/patch/20210727045222.905056-6-tudor.ambarus@microchip.com/
>>
>> Sorry, I'm not sure what I should do with this information. I didn't
>> even know about the continuation codes thing until now.
>> Is there something I need to do here or do I just need to wait for the
>> collision handling code to get merged?
> 
> I think that should be what you need to do. Tudor, any plans on
> re-rolling that patch series in the near future?
> 
Hi, all,

Yes, I was out of office for a month, today I got back. I'll handle it.

Cheers,
ta

  reply	other threads:[~2021-09-29  5:17 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-09-18  7:22 [PATCH] mtd: spi-nor: Add support for ZB25VQ128 Daniel Palmer
2021-09-18  7:22 ` Daniel Palmer
2021-09-20 11:26 ` Pratyush Yadav
2021-09-20 11:26   ` Pratyush Yadav
2021-09-28 13:15   ` Daniel Palmer
2021-09-28 13:15     ` Daniel Palmer
2021-09-28 16:34     ` Pratyush Yadav
2021-09-28 16:34       ` Pratyush Yadav
2021-09-29  5:16       ` Tudor.Ambarus [this message]
2021-09-29  5:16         ` Tudor.Ambarus

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=4a57745e-dd0e-7890-0767-e6eaabeecd63@microchip.com \
    --to=tudor.ambarus@microchip.com \
    --cc=daniel@0x0f.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-mtd@lists.infradead.org \
    --cc=michael@walle.cc \
    --cc=p.yadav@ti.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.