lists.openwall.net   lists  /  announce  owl-users  owl-dev  john-users  john-dev  passwdqc-users  yescrypt  popa3d-users  /  oss-security  kernel-hardening  musl  sabotage  tlsify  passwords  /  crypt-dev  xvendor  /  Bugtraq  Full-Disclosure  linux-kernel  linux-netdev  linux-ext4  linux-hardening  linux-cve-announce  PHC 
Open Source and information security mailing list archives
 
Hash Suite: Windows password security audit tool. GUI, reports in PDF.
[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <CAPDyKFoHwg3MvyNTTTnZLhsEA0Zhj6ZU+fZkhf8rGeoTsnTDJA@mail.gmail.com>
Date:   Fri, 11 Aug 2023 10:42:20 +0200
From:   Ulf Hansson <ulf.hansson@...aro.org>
To:     Wenchao Chen <wenchao.chen666@...il.com>
Cc:     Wenchao Chen <wenchao.chen@...soc.com>, adrian.hunter@...el.com,
        linux-mmc@...r.kernel.org, linux-kernel@...r.kernel.org,
        zhenxiong.lai@...soc.com, chunyan.zhang@...soc.com,
        yuelin.tang@...soc.com
Subject: Re: [PATCH] mmc: core: Add host specific tuning support for SD HS mode

On Fri, 11 Aug 2023 at 09:23, Wenchao Chen <wenchao.chen666@...il.com> wrote:
>
> On Wed, Aug 9, 2023 at 6:09 PM Ulf Hansson <ulf.hansson@...aro.org> wrote:
> >
> > On Wed, 9 Aug 2023 at 07:30, Wenchao Chen <wenchao.chen@...soc.com> wrote:
> > >
> > > Added .prepare_hs_tuning and .execute_hs_tuning host
> > > callbacks to support host-specific tuning for SD high
> > > speed mode.
> >
> > This certainly needs to be clarified more. Especially why it's needed
> > for the sdhci-sprd variant.
> >
>
> First of all, Unisoc's IC provides cmd delay and read delay to ensure
> that the host can
> get the correct data. However, according to SD Spec, there is no need
> to do tuning in
> high speed mode, but with the development of chip processes, it is
> more and more difficult
> to find a suitable delay to cover all the chips.
> Therefore, we need SD high speed mode online tuning.

Thanks for sharing this information - and please add some of this in
the commit message next time.

[...]

> > > +static int mmc_send_tuning_data(struct mmc_card *card)
> > > +{
> > > +       u8 status[64];
> >
> > We use kmalloc-ed data for data transfers.
> >
>
> Why is it better to use kmalloc-ed data?

If you use DMA for example. From the core point of view, all data
should be kmalloc-ed, if it's a data transfer and possibility that
that DMA is used. Hence, it seems reasonable to conform to this
behaviour when using this helper function from the core.

[...]

Kind regards
Uffe

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ