LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Sowjanya Komatineni <firstname.lastname@example.org>
To: Mark Brown <email@example.com>
Cc: Jonathan Hunter <firstname.lastname@example.org>,
Laxman Dewangan <email@example.com>,
"Krishna Yarlagadda" <firstname.lastname@example.org>,
Subject: Re: [PATCH V5 1/4] spi: tegra114: add support for gpio based CS
Date: Wed, 15 May 2019 11:24:22 +0000 [thread overview]
Message-ID: <BYAPR12MB3398ED52051F5BFA08D7B3A6C2090@BYAPR12MB3398.namprd12.prod.outlook.com> (raw)
> > Tegra SPI doesn’t support inter byte delay directly to meet some SPI slave requirements.
> > So we use GPIO control CS in parallel with a dummy HW CS and use inactive cycles delay of SPI controller to mimic inter byte delay.
> Please fix your mail client to word wrap within paragraphs at something
substantially less than 80 columns. Doing this makes your messages much
easier to read and reply to.
I did changed but looks like it didn't made diff. Will try with different email client.
> Please don't ignore review comments, people are generally making them
for a reason and are likely to have the same concerns if issues remain
unaddressed. Having to repeat the same comments can get repetitive and
make people question the value of time spent reviewing. If you disagree
with the review comments that's fine but you need to reply and discuss
your concerns so that the reviewer can understand your decisions.
If you are referring to comment from Jon on updating commit, I didn't ignored. I am just waiting if any more comments from you or others before posting updated patch.
But I see you applied patch now. So how should I post with updated commit?
next prev parent reply other threads:[~2019-05-15 11:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-14 5:03 [PATCH V5 0/4] additional features to Tegra SPI Sowjanya Komatineni
2019-05-14 5:03 ` [PATCH V5 1/4] spi: tegra114: add support for gpio based CS Sowjanya Komatineni
2019-05-14 9:33 ` Jon Hunter
2019-05-14 17:18 ` Sowjanya Komatineni
2019-05-14 17:31 ` Jon Hunter
2019-05-15 9:35 ` Mark Brown
2019-05-15 11:24 ` Sowjanya Komatineni [this message]
2019-05-15 11:29 ` Mark Brown
[not found] ` <BYAPR12MB3398528B86D3DE9CC3AA6D85C2090@BYAPR12MB3398.namprd12.prod.outlook.com>
2019-05-15 11:42 ` Mark Brown
2019-05-15 11:18 ` Applied "spi: tegra114: add support for gpio based CS" to the spi tree Mark Brown
2019-05-14 5:03 ` [PATCH V5 2/4] spi: tegra114: add support for hw based cs Sowjanya Komatineni
2019-05-15 11:18 ` Applied "spi: tegra114: add support for hw based cs" to the spi tree Mark Brown
2019-05-14 5:03 ` [PATCH V5 3/4] spi: tegra114: add support for HW CS timing Sowjanya Komatineni
2019-05-15 11:18 ` Applied "spi: tegra114: add support for HW CS timing" to the spi tree Mark Brown
2019-05-14 5:03 ` [PATCH V5 4/4] spi: tegra114: add support for TX and RX trimmers Sowjanya Komatineni
2019-05-15 11:18 ` Applied "spi: tegra114: add support for TX and RX trimmers" to the spi tree Mark Brown
2019-05-23 1:02 ` [PATCH V5 4/4] spi: tegra114: add support for TX and RX trimmers Nathan Chancellor
2019-05-23 1:10 ` Sowjanya Komatineni
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--subject='Re: [PATCH V5 1/4] spi: tegra114: add support for gpio based CS' \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
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).