From: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
To: Jason Gunthorpe <jgunthorpe@obsidianresearch.com>
Cc: peterhuewe@gmx.de, tpmdd-devel@lists.sourceforge.net,
linux-kernel@vger.kernel.org,
Marcel Selhorst <tpmdd@selhorst.net>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Tejun Heo <tj@kernel.org>, Al Viro <viro@zeniv.linux.org.uk>,
Andrew Morton <akpm@linux-foundation.org>,
Jianyu Zhan <nasa4836@gmail.com>,
"Eric W. Biederman" <ebiederm@xmission.com>,
Rasmus Villemoes <linux@rasmusvillemoes.dk>,
Andrzej Hajda <a.hajda@samsung.com>, NeilBrown <neilb@suse.de>,
Guenter Roeck <linux@roeck-us.net>,
Simon Wunderlich <sw@simonwunderlich.de>
Subject: Re: [PATCH v2] tpm: enable PPI for TPM 2.0
Date: Wed, 22 Apr 2015 08:57:55 +0300 [thread overview]
Message-ID: <20150422055755.GC6764@intel.com> (raw)
In-Reply-To: <20150421193338.GA31179@obsidianresearch.com>
On Tue, Apr 21, 2015 at 01:33:38PM -0600, Jason Gunthorpe wrote:
> On Tue, Apr 21, 2015 at 09:30:55PM +0300, Jarkko Sakkinen wrote:
> > Enabled PPI interface to the character device sysfs directory accessible
> > both for 1.x and 2.0 devices.
> >
> > The ppi group is moved from the platform device directory to the
> > character device directory. In order to retain backwards compatibility
> > with the 1.x devices, a symlink is created to the platform device
> > directory.
> >
> > Signed-off-by: Jarkko Sakkinen <jarkko.sakkinen@linux.intel.com>
>
> > Reviewed-by: Jason Gunthorpe <jason.gunthorpe@obsidianresearch.com>
>
> Jumping the gun a bit, there :)
> But yes, the TPM bits still look OK to me.
> Ah, don't forget to update Documentation/ABI/testing/sysfs-driver-ppi
Right. Is there a rigid naming convention for these files? I don't see
any obvious pattern and there's no documentation for file names in here:
https://www.kernel.org/doc/Documentation/ABI/README
The legacy TPM 1.x sysfs attributes are in a file named as sysfs-class-tpm.
Maybe we could:
* Rename existing sysfs-class-tpm as sysfs-class-tpm1
* Rename sysfs-driver-ppi as sysfs-class-tpm
What do you think? I don't know exactly what to do here. That is the
reason I haven't updated the documentation yet.
> > diff --git a/fs/kernfs/dir.c b/fs/kernfs/dir.c
> > index 6acc964..749cea3 100644
> > +++ b/fs/kernfs/dir.c
> > @@ -1225,6 +1225,7 @@ int kernfs_remove_by_name_ns(struct kernfs_node *parent, const char *name,
> > else
> > return -ENOENT;
> > }
> > +EXPORT_SYMBOL_GPL(kernfs_remove_by_name_ns);
>
> ??
> I don't see this being called
My bad, it is clutter in the patch file. I'll remove it.
> > +/**
> > + * sysfs_link_group_to_kobj - add a symlink to a kobject pointing to a group
> > + * @kobj: The kobject containing the group.
> > + * @target_kobj: The target kobject.
> > + * @target_name: Name of the target group.
> > + */
> > +int sysfs_link_group_to_kobj(struct kobject *kobj, struct kobject *target_kobj,
> > + const char *target_name)
>
> Agree with Guenter, separate patch.
>
> I liked the signature I suggested earlier:
>
> sysfs_link_group_to_kobj(struct kobject *from_kobj,
> const char *from_name,
> struct kobject *target_kobj,
> const char *target_name)
>
> 'link_group' may be too specific a name, I think this would work to
> establish a link to any file in a sysfs directory? Which is good,
> we'll need that for future TPM patches that relocate the other sysfs
> files..
I think it should.
> Jason.
/Jarkko
next prev parent reply other threads:[~2015-04-22 5:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-21 18:30 Jarkko Sakkinen
2015-04-21 18:58 ` Guenter Roeck
2015-04-22 5:44 ` Jarkko Sakkinen
2015-04-21 19:33 ` Jason Gunthorpe
2015-04-22 5:57 ` Jarkko Sakkinen [this message]
2015-04-22 16:38 ` [tpmdd-devel] " Jarkko Sakkinen
2015-04-22 17:22 ` Jason Gunthorpe
2015-04-22 18:10 ` Greg Kroah-Hartman
2015-04-23 4:55 ` Jarkko Sakkinen
2015-04-21 19:52 ` Greg Kroah-Hartman
2015-04-22 5:39 ` Jarkko Sakkinen
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=20150422055755.GC6764@intel.com \
--to=jarkko.sakkinen@linux.intel.com \
--cc=a.hajda@samsung.com \
--cc=akpm@linux-foundation.org \
--cc=ebiederm@xmission.com \
--cc=gregkh@linuxfoundation.org \
--cc=jgunthorpe@obsidianresearch.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@rasmusvillemoes.dk \
--cc=linux@roeck-us.net \
--cc=nasa4836@gmail.com \
--cc=neilb@suse.de \
--cc=peterhuewe@gmx.de \
--cc=sw@simonwunderlich.de \
--cc=tj@kernel.org \
--cc=tpmdd-devel@lists.sourceforge.net \
--cc=tpmdd@selhorst.net \
--cc=viro@zeniv.linux.org.uk \
/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
Powered by JetHome