linux-usb.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johan Hovold <johan@kernel.org>
To: Loic Poulain <loic.poulain@linaro.org>
Cc: Andy Shevchenko <andy.shevchenko@gmail.com>,
	Johan Hovold <johan@kernel.org>, USB <linux-usb@vger.kernel.org>,
	Srinivas Kandagatla <srinivas.kandagatla@linaro.org>,
	Ajay Gupta <ajaykuee@gmail.com>
Subject: [v3] USB: serial: ftdi_sio: Add MTP NVM support
Date: Mon, 25 Jun 2018 10:40:00 +0200	[thread overview]
Message-ID: <20180625084000.GG26803@localhost> (raw)

On Mon, Jun 25, 2018 at 10:35:31AM +0200, Loic Poulain wrote:
> Hi Andy,
> 
> On 25 June 2018 at 09:36, Andy Shevchenko <andy.shevchenko@gmail.com> wrote:
> > On Fri, Jun 22, 2018 at 5:22 PM, Loic Poulain <loic.poulain@linaro.org> wrote:

> >> +#define EEPROM_SZ_FTX 2048 /* cf FTDI AN_201 */
> >> +#define EEPROM_SZ_FT232RL 128  /* cf FTDI AN_121 */
> >
> > These defines looks too particular, shouldn't be this a part of driver
> > data / platform data / device properties?
> 
> I'm not sure where to move this since it depends on chip type which is
> detected at runtime. I don't think ftdi_sio_quirk is the right place.
> So maybe I could just skip the defines for now and come back to:
> 
> switch (priv->chip_type) {
>     case FTX:
>         nvmconf.size = SZ_2K;
>         break;
> ...

Yes, please do that. The EEPROM_SZ_ defines you added in this (?)
revision add no value.

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

             reply	other threads:[~2018-06-25  8:40 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-25  8:40 Johan Hovold [this message]
  -- strict thread matches above, loose matches on Subject: below --
2018-06-25  8:35 [v3] USB: serial: ftdi_sio: Add MTP NVM support Loic Poulain
2018-06-25  7:36 Andy Shevchenko
2018-06-22 14:22 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=20180625084000.GG26803@localhost \
    --to=johan@kernel.org \
    --cc=ajaykuee@gmail.com \
    --cc=andy.shevchenko@gmail.com \
    --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 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).