From: Johan Hovold <johan@kernel.org>
To: Loic Poulain <loic.poulain@linaro.org>
Cc: Johan Hovold <johan@kernel.org>, USB <linux-usb@vger.kernel.org>,
Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
Andy Shevchenko <andy.shevchenko@gmail.com>,
Ajay Gupta <ajaykuee@gmail.com>,
Daniel Thompson <daniel.thompson@linaro.org>
Subject: [v6] USB: serial: ftdi_sio: Add MTP NVM support
Date: Mon, 16 Jul 2018 14:25:58 +0200 [thread overview]
Message-ID: <20180716122558.GP10204@localhost> (raw)
On Sun, Jul 15, 2018 at 10:30:39PM +0200, Loic Poulain wrote:
> Hi Johan,
>
> Thanks for the review.
>
> On 10 July 2018 at 11:19, Johan Hovold <johan@kernel.org> wrote:
> > The CBUS configuration is stored in just a couple of words at a known
> > offset and could easily be retrieved without depending on the nvmem
> > subsystem when needed.
> >
> > As I assume fiddling with the EEPROM should be rare (e.g. done during
> > development or by hobbyists) and would still depend user-space tools
> > (e.g. for layouts, checksums and external EEPROMs), I think we should
> > just leave it all to user space to deal with.
>
> I'm fine with that, to be honest I'm interested in adding GPIO control
> but wanted to progress step by step, EEPROM access being the first one.
> I thought it could have been valuable to expose it via nvmem, but like you said,
> we can keep this internal for now.
>
> So, I'll come back with new patche(s) for CBUS GPIOs.
Sounds good!
Thanks,
Johan
---
To unsubscribe from this list: send the line "unsubscribe linux-usb" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next reply other threads:[~2018-07-16 12:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-16 12:25 Johan Hovold [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-07-15 20:30 [v6] USB: serial: ftdi_sio: Add MTP NVM support Loic Poulain
2018-07-10 9:19 Johan Hovold
2018-07-09 8:47 Loic Poulain
2018-06-29 19:52 Ajay Gupta
2018-06-26 12:54 Loic Poulain
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=20180716122558.GP10204@localhost \
--to=johan@kernel.org \
--cc=ajaykuee@gmail.com \
--cc=andy.shevchenko@gmail.com \
--cc=daniel.thompson@linaro.org \
--cc=linux-usb@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=srinivas.kandagatla@linaro.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 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.