From: Andrew Lunn <andrew@lunn.ch>
To: Sven Van Asbroeck <thesven73@gmail.com>
Cc: Heiner Kallweit <hkallweit1@gmail.com>,
Jakub Kicinski <kuba@kernel.org>,
Russell King <linux@armlinux.org.uk>,
"David S. Miller" <davem@davemloft.net>,
netdev <netdev@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH net-next v1] net: phy: spi_ks8995: Do not overwrite SPI mode flags
Date: Mon, 9 Nov 2020 21:25:59 +0100 [thread overview]
Message-ID: <20201109202559.GF1456319@lunn.ch> (raw)
In-Reply-To: <CAGngYiVV1_65tZRgnzSxDV5mQGAkur8HwTOer9eDMXhBLvBCXw@mail.gmail.com>
On Mon, Nov 09, 2020 at 02:56:38PM -0500, Sven Van Asbroeck wrote:
> On Mon, Nov 9, 2020 at 2:49 PM Andrew Lunn <andrew@lunn.ch> wrote:
> >
> > Did you check to see if there is a help to set just the mode without
> > changing any of the other bits?
>
> Absolutely, but it doesn't exist, AFAIK.
> It would be great if client spi drivers would use a helper function like
> that.
Then you should consider adding it, and cross post the SPI list.
Andrew
next prev parent reply other threads:[~2020-11-09 20:26 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-09 19:31 [PATCH net-next v1] net: phy: spi_ks8995: Do not overwrite SPI mode flags Sven Van Asbroeck
2020-11-09 19:49 ` Andrew Lunn
2020-11-09 19:56 ` Sven Van Asbroeck
2020-11-09 20:25 ` Andrew Lunn [this message]
2020-11-09 20:34 ` Sven Van Asbroeck
2020-11-09 21:09 ` Jakub Kicinski
2020-11-09 21:20 ` Sven Van Asbroeck
2020-11-09 21:24 ` Jakub Kicinski
2020-11-09 21:29 ` Sven Van Asbroeck
2020-11-09 22:04 ` Jakub Kicinski
2020-11-09 22:19 ` Sven Van Asbroeck
2020-11-09 22:23 ` Jakub Kicinski
2020-11-09 22:27 ` Sven Van Asbroeck
2020-11-09 22:36 ` Jakub Kicinski
2020-11-09 22:39 ` Sven Van Asbroeck
2020-11-09 22:50 ` Jakub Kicinski
2020-11-09 22:57 ` Sven Van Asbroeck
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=20201109202559.GF1456319@lunn.ch \
--to=andrew@lunn.ch \
--cc=davem@davemloft.net \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=netdev@vger.kernel.org \
--cc=thesven73@gmail.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).